skysight-inc/HackerNews huggingface dataset:
> The only negatives I have heard about Scala are the binary compatibility issues with dependencies and Scala versions.

You might have heard people complaining, but it's kind of complaining at a very high level.

Scala's compatibility story is better than most other languages, it's just that a significant part of Scala developers come from Java, where people expect that _nothing_ _ever_ changes.

Scala is not like that, it has a deprecation policy which includes actually removing stuff.

> I had shied away from Scala before since I didn't see any clear dependency injection support (can't live without it) but seems like that has been solved with the Spring Scala module.

Not sure I'd call that idiomatic Scala. There are a few DI libraries in Scala, but I'd say that the language reduces the need for DI a lot.
You can of course use everything from legacy Java stuff like Spring, Guice, CDI to Scala libraries like SubCut, MacWire or Scaldi.
http://www.cssilize.com/ ($35) and https://sudopay.com/ ($29) were discussed here before.
The question is if you have haven't validated your product yet do you develop for iOS, Android or use a cross platform toolkit like PhoneGap. I think the answer will depend on what you have experience with, who your target market is and whether you want to target tablets (which still leans towards iOS in my view).

Validate on one platform and then expand to another if it works is my current approach but it definitely isn't the only one.
The first social network for developers and the tech community
This is stunning. I think this type of practice is illegal in the UK.
Can anyone out there explain this in pseudocode? I tried my best to understand the paper but was thoroughly defeated by it.
Do they keep the leadership? I'd love to see fresh blood there.
There are two issues here. One is the ability to obtain, given sufficient local resources, a file descriptor to /dev/urandom. I think defining away this problem is fine: running a program in an environment without a valid /dev is simply user error. In such an environment, operations that might require entropy should simply fail.

The second issue is resource limits: low level components of LibreSSL cannot cope with entropy-generating functions failing. On OpenBSD, these functions cannot fail, but on Linux, they can. That's not a problem with Linux, but with LibreSSL's architecture. It's LibreSSL's responsibility to ensure that it allocates. Every call to LibreSSL's internal RNG is preceded by some kind of resource-allocating call that can fail. It's in this call that LibreSSL should obtain the resources needed to do its work. That it doesn't is simply a bug in LibreSSL, not a deficiency in Linux.
Mongodb: aggregation framework vs. mapreduce
It's called the "Chilling Effect":

http://en.wikipedia.org/wiki/Chilling_effect
Finnish SaaS e-commerce recommendation engine raises 5.5M Series A round
Nor do they have people depending on them to put food on their table. When you have to provide, you don't have too much freedom in where you work. It's rare to move your entire family across country, for example. So maybe you're stuck in some backwater city, because your kid goes to school there and you don't want to ruin their social life by uprooting them just because you're facing some crunch time. Is it impossible for you to be a master programmer in that situation? Certainly not.

The point is, it's not a good idea to take our freedom for granted. We're kind of spoiled right now, because the job market is literally figuratively on fire. Once the job market saturates within a decade, people will hopefully realize how rare it was for us to have such freedom of choice in where we were able to choose to work.
Fails Compilation Best Fails Year 2014
First of all, I was not talking about patents at all.

And my first assumption was that they do something more than cropping, in other words that the implementation is not trivial. But I learned that might not be the case.
Packet handling != application logic

But yes, there is some interesting work being done on building network applications directly against the hardware.
To anyone wishing to use this, there is a missing opening " on line 5 just before facebook_token.

Edit: I realise this should really be posted on the Github page but I don't have an account and can't be bothered to register a new one.
You're completely wrong. According to the OpenBSD devs, on modern BSDs and Linux, /dev/urandom is as good a source of entropy as anything. It's commonly implemented by a good cryptographically secure pseudo-random generator. This code only gets called in cases where /dev/urandom is not available (for example in a chroot jail or when the file descriptor limit is reached).
I've tried mdb, but had some crashes in the initial testing (windows7, 64bit).
dup https://news.ycombinator.com/item?id=8028704
> Even if you have opened it, you have no guarantee that the file descriptor has not been closed since.

You can absolutely rely on internal file descriptors not being closed. A program that closes file descriptors it does not own is as buggy as a program that calls free on regions of memory it does not own. A library cannot possibly be robust against this form of sabotage. The correct response to EBADF on a read of an internal file descriptor is to call abort.

The "close all file descriptors" operation is most common before exec. After exec, the process is a new program that can open /dev/urandom on its own (since, as I've mentioned previously, it's a broken environment in which /dev/urandom does not exist).
Stress affects short term memory in old age
- Good fullscreen support. Normal terminal can only go into "Lion fullscreen" which means it will be on a separate workspace and you can't have other windows besides it.
- Configurable keyboard shortcuts

That's reason enough for me...
Netflix works fine on my ARM Linux phone. It's not about OS or processor, it's about middleware.
QUIZ: Which of the Top e-Commerce Platforms is Right for Your Business?
How about the free tools of the trade, 2014?
Interresting... wondering if I can easily map the kv part to say lua's table dictionary
Show HN: Project Enferno
Sounds like the Master Programmer has never worked
at a company that crunched you for 80 hour weeks, for weeks.

No, that's just a separate problem:

Why are programmers non-productive? Because their time is wasted in meetings.
Why are programmers rebellious? Because the management interferes too much.
Why are the programmers resigning one by one? Because they are burnt out.
Having worked for poor management, they no longer value their jobs.
Alcohol affects students' memory
Similarly, http://thecodelesscode.com/contents

It's a bit more contemporary and is still being added to. I can't figure out who the author is though. All I know is they go by the name of Qi https://github.com/QilessQi

Also, all the koans are on Github and translations can be submitted via PRs https://github.com/alessandro1997/the-codeless-code
OpenXava 5.0.1 released: Rapid Development for Java
Show HN: Cod – Rethinking Documentation Generators
Looking at [1], the following can be found listed under sources:

^ <![CDATA[Scribn. & Merr.]]>, 1901 In: Bull. Div. Agrostol. U.S.D.A. 24: 26

Maybe he should have done more testing before spamming Wikipedia with mess like that.

[1] https://sv.wikipedia.org/wiki/Eutriana_repens
> I think we can get away with the fully-automated approach for most of the maps

Even though it might look nice to outsiders, I firmly believe you can never get representations of cultural and human data really right if you're doing them automatically.

Such data will always be full of quirks, and representing it will always need some tweaking if you want to get it perfect. Say, moving a label a bit further left so it doesn't hide a monument, displaying a street wider than its actual designation because it's an important way, not showing at all another path because it's disconnected from the rest of the network and really not that important (or displaying the more minor path that connects this one to the rest even though its designation means it should be hidden).

I really think a lot of people who make maps do not acknowledge the fact that human data is not something that is completely normalized, not normalizable, and sometimes might not be able to be processed with a set of rules, however fine.
Maybe there's a much less sinister reason for companies shying away from relocation. We had a few applicants that we were willing to offer relocation and all of them flipped at the last moment. They all said their significant others had a change of heart. I suspect the changes a relocation will bring, hits home really late.
Once bitten twice shy; I am not considering people who are not in my geographical area anymore.
Likewise, sorry if I was too emphatic about what's a matter of taste.
This script also has an unintended consequence: it can roughly measure how attractive you are to the population. Assuming that everyone you auto-swipe will also respond (and truthfully, not using this script) this could give you some very sobering results if you're not the most attractive. Imagine the guy who runs this and gets 10-15 likes. It's like automating going to a bar and getting stuffed all night long, only quicker! It could also of course end up boosting your ego a lot, but I suspect for many it will not. Stay thirsty, my friends.
If LibreSSL was the origin of the API, I might agree with you. But LibreSSL is trying to largely conform to an API they have inherited. If that isn't feasible to do safely on Linux, then while it may be arguable whether or not it is a deficiency in Linux, it is a problem for Linux users.

For my part, I believe strongly that it is a deficiency if we have to go through all these kinds of hoops in order to safely obtain entropy, when the solution is so simple on the kernel end: Ensure we retain a syscall.
Does anybody really like scrolling animations? They make page navigation a nightmare. I hope it's a trend that will die soon.
It's likely the biggest power drain because of processor consumption because many people spend a lot of time on a laptop on the internet.

Further, if you read the article, you'd know that this problem does not affect macs.
apparently I started this? woah.
Exactly what part of LibreSSL's API prohibits the maintenance of an internal file descriptor and early checks that this file descriptor can be filled with a handle to /dev/urandom?

Resource management is not a "hoop". It is a fact of life.
The comments in the code makes it exceedingly clear that a part of the reason for this code to exist is to make a point, and it seems they've succeeded very well at that.
The "htm" extension was a lot more common back when some consumer systems still had the three character limit. The web server limitations don't matter that much on something like a web hotel where users typically FTP their files over from whatever OS they are using themselves.
6 Reasons – Why you should switch to Adsuit
It becomes the application's problem. LibreSSL on its own can't really go out and obtain resources whenever it wants, nor can it ensure the application won't take these away. The application using LibreSSL would have to make LibreSSL do these things, at the right time and right place. You're pushing responsibility to users and applications and while at it admitting that it is impossible for a library to abstract it all away and provide a guaranteed safe API that cannot ever fail. It definitely sounds very Linuxy.
Self-censorship is also called "self-censorship". http://en.wikipedia.org/wiki/Self-sensorship
I don't think that's what grizzles is saying, I think the idea was to patch the wiki software to generate these article stubs on the fly from the actual source instead of batch importing them once.

Sounds like a good idea to me, but I don't know the Wikipedia culture so they might have reasons against that.
but the scroll wheel finally works
zUID: Unique ID generator service
> 536931d80decb18c33db9612bdd004d4 susi

Poor women called Susi.
This is awesome! But I can't see it surviving on donations. Commercialize it please so that it survives. Tasteful ads aren't so bad like what Reddit does or Carbon[something]... I'm just concerned you won't survive on donations.
Life-long endurance running slows down ageing
I thought that, when nesting tmux instances, you just press the prefix key a number of times depending on how deep you need you need your next keystroke to propagate?

For me personally, I use ctrl-a instead of ctrl-b so I have this line in my ~/.tmux.conf:

#send prefix to nested sessions with C-a
bind-key C-a send-prefix

Lastly, iterm2 uses it's own keystrokes for it's tmux integration. (i.e.: cmd-D to split vertically)
Yup. I would have never thought about using Google drive to share PDF publicly. Now that I know, still not sure I would. You're damn right, interface does matter.
LibreSSL can pre-allocate resources it needs in places where applications expect it to fail, then go on to use those resources in places where applications do not expect it to fail. Complaining about having to manage a file descriptor is strange, since LibreSSL already manages another resource, heap memory. Nobody expects LibreSSL to be able to do everything it promises if the system runs out of memory, so why should people expect LibreSSL to do everything it promises if the systems is misconfigured or out of file descriptors? Fundamentally, applications need to cope with resource constraints, and it's the job of libraries to tell applications when resource constraints have been exceeded. raise(SIGKILL) is an exceptionally poor way of informing an application that its resource demand has outstripped supply.
Nothing. But nothing also prevents the client from intentionally or accidentally closing that file descriptor. As I've pointed out elsewhere, looping over all file descriptors and closing them on fork() is a common pattern for applications where you want to ensure you don't have resource leaks (whether for capacity or security).

Which is fine if you have a safe way of returning errors in all code paths, but as the comments points out, they believe they don't. Maybe they're wrong, but they seem to have spent some time thinking about it. They've also provided an easy define to change the behaviour to failing hard for people building it on systems where their caveats against failing hard does not apply (e.g. systems with secure core files)

If they can't fail early in a safe manner without potentially creating a security leak (as they potentially would if an unprivileged user could induce an unsafe core dump), and can't even be guaranteed that they're able to safely log the error (there's no guarantee they'd be able to write it anywhere), it's hard to see alternatives but to try to do something that is "good enough" as the alternative could be much worse.

Neither is a good solution.
Australian Gov refuses to release source code to software used to count votes
Thank you so much. I lost this feature with my new machine and I was sure it used to work.
Comcast Rep won't let a customer leave
Then abort if it's not available? A lot of software (most?) doesn't work with an empty /dev. At least null is othen required, so why not throw urandom in there as well?
Room-Sized and Stadium-Sized 3D Printers
نتيجة الثانوية العامة من موقع اليوم السابع 2014 برقم الجلوس
"FTDI USB Drivers", if it's the VCP ones the very latest ones have been reasonably stable for me. I've not had a system crash for quite a while now, whereas I was having them weekly with an older version.
why scribd?
All asymptotically fast algorithms for integer multiplication basically reduce the problem to one or several polynomial multiplications.

Polynomial multiplication can be done in subquadratic time using an evaluation-interpolation strategy: namely, to multiply two polynomials of degree less than n, we evaluate both polynomials at 2n points, compute 2n pointwise products, and recover the polynomial product by interpolation.

When one chooses roots of unity as the evaluation points, the evaluation and interpolation steps reduce to discrete Fourier transforms (forward and inverse, respectively), which can be done in O(n log n) arithmetic operations by means of the fast Fourier transform (the pointwise products require O(n) arithmetic operations).

Now, there are a couple of difficulties. How do you decompose the integers into polynomials? Is it better to use short polynomials with large coefficients, or long polynomials with small coefficients? Since the coefficients asymptotically grow with the length, you have to account for the bit complexity of the arithmetic operations in the FFTs and pointwise products (here you get recursive integer multiplications).

Which FFT algorithm should you use (there are many to choose from)?

Also, the ring of integers does not have enough roots of unity to do FFTs, so you have to lift the computation to a larger ring, such as the field of complex numbers (with numerical approximations), an appropriate finite field, or (as in the Schönhage-Strassen algorithm) a polynomial extension ring. Which choice gives the best complexity?

The improvements to integer multiplication published in the last few decades have basically been tightened analyses of such tradeoffs. I have not read this paper in detail yet, but it seems to provide a clear description in the introduction. Quote:

The idea of the new algorithm is remarkably simple. Given two n-bit integers, we split them into chunks of exponentially smaller size, say around log n bits, and thus reduce to the problem of multiplying integer polynomials of degree O(n/log n) with coeffcients of bit size O(log n). We multiply the polynomials using discrete Fourier transforms (DFTs) over C, with a working precision of O(log n) bits. To compute the DFTs, we decompose them into "short transforms" of exponentially smaller length, say length around log n, using the Cooley-Tukey method. We then use Bluestein's chirp transform to convert each short transform into a polynomial multiplication problem over C, and finally convert back to integer multiplication via Kronecker substitution. These much smaller integer multiplications are handled recursively.
Why setup the device when you should be able to open it way prior to chrooting (if you don't - that's a proper time to abort() on my book) and keep the descriptor open for later use?
Daily routine of lazy hacker
Why would you want to reseed the PRNG?

If the PRNG is good enough (no visible correlation in the statistics tests you can imagine thrown at it), and it's properly seeded with true randomness, then isn't everything peachy?

I am much more afraid of the seeding part of it than the actual algorithm. The algorithms are well studied by smart people, the actual implementation and seeding aren't always.

There mere fact that one could reseed the PRNG makes me nervous. That could be used in devious ways. But I am not a cryptographer, not even a mathematician, so don't take my word for it!

Am I wrong here? Why?
Jeu-à-télécharger : une aventure fun avec des jeux PC
Découvrez les jeux PC fun et fous que vous propose le site de téléchargement Jeu-à-télécharger ! Une grande aventure vous y attend tous les jours.
Vertical and horizontal splitting. This gives me several side by side terminals in one window.
Also: Buffy the vampire slayer (season 4).
It's a bit strange people make biblic references for such projects when the "don't you play God" theme (itself a variation on the myth of the golem) is, volens nolens, part of popular culture.
Or maybe the team deliberately did it, as a kind of memo?
Indeed! I got dragged to the police station once by a guy cause I took a picture of his front door. He even tried to force me in to his car. Instead I walked to the cops with the guy driving next to me. He explained the problem and the cops told him to leave me alone.
Which brings an interesting improvement to the game: Testing pictures.

So far I've had the most success with a simple picture of me stretching when I was tired one morning and sister had my phone and was bored. I think the main feature is that you can see my forearms are veiny. But most of my face is obscured by sunglasses, may hair is covered by a wool hat, and I'm generally being tired, sleepy, and uninteresting.

Pic in question: http://instagram.com/p/lm5FNjkxp1/?modal=true
Zinc doesn't rust though.

ED: Read the correction below.
.. which you need to do anyway. The SSL library, and the program linked against it, can fail in a thousand more ways that generate them.
This Package Could Help Amazon Use 200 Times Fewer Boxes
> Nobody expects LibreSSL to be able to do everything it promises if the system runs out of memory, so why should people expect LibreSSL to do everything it promises if the systems is misconfigured or out of file descriptors?

The issue is not that anyone expects it to do everything it promises if the system is misconfigured, but that if it should fail, it should take care to try to avoid failing in ways that could open massive security holes.

This is the issue here: The developers believe that as the existence of systems with unsafe core files is well established, their options are limited, as there is a risk of exposing enough state to less privileged users with a core dump to leave the system vulnerable. Someone building for a system they know has properly secured core files, can disable the homegrown entropy code, and the code will fail hard if /dev/urandom and sysctl() are both unavailable, and the problem goes away.

But what do you suggest they do for the case where they do not know whether failing will expose sensitive data? They've chosen the option they see as the lesser of two evils: Do as best they can - only as a fallback, mind you - and include a large comment documenting the issues.

If they had full freedom to design their own API this would not be an issue. They could e.g. have put in place a callback that should return entropy or fail in an application defined safe way, or many other options. But as long as part of the point is to be able to support the OpenSSL API, their hands are fairly tied.
WHY?????????????? :(
I tried the automated-liker approach a few months ago. While post-processing makes more sense in theory, Tinder's algorithms will penalize you for having a poor match/message ratio.

What I found to be a lot more fun is to run your hits through Google's reverse image search to see who they are in real life before striking up a conversation.
Taking a photo yes, of a liquid gas storage tank. The feds wouldn't have showed up if he was taking pictures of a traffic light.
I currently spend about a dollar a cup to two dollars a cup for black coffee. Mostly because seems like it would take a few hundred dollars worth of experimental purchases and a reasonable number of hours to match the quality I get form local cafe.

If I move to another city or If I decide I have time/money for the hobby I will do.
If I'm not driven to find a better source, then presumably I was satisfied with the information on Wikipedia. Quick reference for the most relevant information is what Wikipedia is good at.
How D-Wave Built Quantum Computing Hardware for the Next Generation
> tracking the landing leg attachment points at liftoff

I suspect its more to do with that being where the giant spacex logo is painted on.
I have tmux set up so that pressing the prefix key twice switches to the previously selected window. I don't remember whether it was like that out of the box, or whether I had to configure that when I switched from gnu screen.

I take it with nested tmux sessions, cmd-D would split the outer tmux window? How would you split the inner tmux window?
post it somewhere else
I think the stereotype is that men are not as discerning as women when dating. That is, if a straight man is presented with 100 random women, he'd be more likely to consider a larger number of them to be dateable, than if a straight woman were presented with 100 random men.
These would make amazing wall art, sign me up.
Has anyone felt in limbo since leaving high school