skysight-inc/HackerNews huggingface dataset:
> I'm confused. Is there something else in another language with better solutions for IDE, dependency management, dependency injection, etc.?

Other languages are less dependent on a heavy IDE; I can write Python or even Scala in vim (+ repl in another tab) reasonably comfortably, and while vim has its warts it's a lot less fragile than eclipse.

Spring is IMO not worth the complexity compared to explicitly constructing things, but if you really want to do that there are ways to do it in Scala (e.g. just using implicits, reader monad) that don't require annotations or XML and don't have anything like the number of quirks (e.g. autoproxying, about 10 magic lifecycle methods, configuration-dependent behaviour on duplicate beans) that Spring does.

Likewise Hibernate is nice but it has some irritating misbehaviour (e.g. passing empty lists can cause it to make SQL syntax errors) that isn't present in ActiveRecord or even modern JVM alternatives.

I didn't expect my comment to be so negative when I started writing it, but as I started to try and explain the basics I realized how many arbitrary workarounds a very basic Java app needs. A lot of this is 10 years of accumulated cruft rather than fundamental problems, but at the sharp end new users still have to deal with it.
I misread the title, I thought they hired some farmer who builds a rocket in his barn, similar to the movie The Astronaut Farmer.

Turns out it's a regular farmer... growing rocket fuel?

Actually... if the new rocket is using methane could they be growing crops that decompose into lots of methane? Are they experimenting with alcohol/LOX? Are they growing biofuel to refine to RP-1?
TIPS open up a can of worms that most people probably don't want to deal with, unless the bonds are held in a tax-advantaged account (such as an IRA). Here's the skinny straight from the horse's mouth:[1]

Form 1099-OID shows the amount by which
the principal of your TIPS increased due
to inflation or decreased due to deflation.
Increases in principal are taxable for the
year in which they occur, even if your
TIPS hasn't matured, so you haven't yet
received a payment of principal.

I.e., you must pay annual taxes on an increase in principal for your TIPS bonds, even though you don't get your cash back from the govt until the bond matures.

No thanks! Count me out of that one!

As a possible alternative (which has its own problems) there are Series I savings bonds (which also attempt to compensate for inflation). Those have the advantage of:[2]

Tax reporting of interest can be deferred
until redemption, final maturity, or other
taxable disposition, whichever occurs first.

[1] http://www.treasurydirect.gov/indiv/research/indepth/tips/re...
[2] http://www.treasurydirect.gov/indiv/products/prod_tipsvsibon...
You are. Sure you call libraries that aren't written in Python, but that seems just as irrelevant as the fact that the JVM is written in C.
Based on some other comments in this thread, it looks much more mundane- a simple tax dodge.
Bayesian Statistics – A Beginner's Guide
I'm incredibly quick with Vim and I rarely use `q:`, `q/`, `:normal`, etc.

In fact, I think I only type `q:` as a typo when I'm trying to `:q[uit]` :p
That's my opinion too. I love 3D. I've made lots of 3D images, classic LR pairs, and SIS, but I'm not enamored of RSIS. One thing about the random stereograms commonly produced, including the demos here, is that having too many horizontal repeats makes the image harder to fuse at usual viewing range.

I'd suggest limiting vertical panels to 7 or so, which would make it easier to see in 3D on a small screen. That goes for any SIS, whether random or bitmap slice "surface". To my sensibilities, the random dot type, as opposed to a normal bitmap image slice used as the vertical panel, is much less visually interesting and gives the viewing eyes much less to grab onto.

IMO a carefully chosen bitmap thematically or visually coordinated with an elegant carefully drawn depth map creates a work of art that can be appreciated for its interesting shape and color even by viewers who can't grok the 3D effect.

Besides, looking at something beautiful can motivate people to keep trying to see the 3D part come into focus, and eventually some do succeed. When that happens it really is like "magic".
I got to agree with the Reddit posts quoted in the blog post.

But it's not just JavaScript, it's Frontend and WebDev in general. The whole landscape is too big and moving too fast for anyone to move along and most importantly: it is very, very frustrating. Go to angel.co and just look at three or four job openings and you will end up with 50 different Frameworks, Libs and Stacks. Half of them might be dead or deprecated in 12 months. It is insane.
Forget CSS Specificity, Always Use BEM
Amazon already charge VAT on items at 20% in the UK.
It's a blessing that most of roman ruins still stand relatively intact even after applying two thousand years of human stupidity to them. For example, they could definitely ruin a lot with an early subway.

And yes, it was kind of strange that Milan outran Rome in terms of subways.

On the other hand, Saint Petersburg is built on the swamp, and metro had to be 50+ meters deep and featured underground river flooding one of its tunnel for 10+ years. At least you're happy to have this place genuinely diggable.
The average Joe on the street never directly interacted with nor was directly affected by Dennis Ritchie's work. Since the greater population had never heard of him, they weren't going to be as emotionally affected by his passing. Popular media knew which way the wind was blowing and decided to devote more time and energy to mourning Jobs, because they need their pageviews.

That's not to say the Ritchie wasn't mourned by the people he most closely associated with. My university's CS department held a one minute silence before morning lectures the day after he died. I'm sure other CS people around the world did something similar too. But Ritchie was simply not a global celebrity the way Jobs was, so you can't expect them to be remembered the same way.
One of the key elements of the new rules is that merchants must collect two pieces of non-conflicting evidence. And the onus of proof is on the merchants' shoulders. They must keep searching until they have two pieces of evidence that do not conflict. If IP address, for example, conflicts with cc billing address then more evidence will be required from the customer.
Google Cloud has found a creative (stupid IMO) solution to this. They no longer allow non-business in the EU to use their services as of recently.

https://support.google.com/cloudbilling/answer/6090602?hl=en
Why you shouldn’t use Git merge --rebase
Could you elaborate about the fr/us move causing shorter days? Most u.s. software companies seem obsessed with long hours.
Very few UK politicians want to leave the EU.
For highly skilled people you generally have lots of options, it's very difficult for a company to require 50 hour weeks without paying a salary higher than a company that requires 40 hour weeks.
As Wiki confirms, it's usual nowadays to reserve the term for freeholders (or tenant-farmers, which WP oddly doesn't mention at all).
Or rather: a friendly reminder that tests should be passing in intermediate commits too after git rebase.
My previous reply was critical of TIPS. But I didn't offer an alternative. This is a very complicated issue to deal with; there are so many pluses and minuses to all investments.

But here's an alternative to TIPS: Roth IRA or Roth 401(k). You put your after-tax money in there and then you NEVER have to pay taxes on interest or capital gains. No taxes ever again. Of course that's at the whim of Congress. They can always bend you over 20 years from now by changing the law. TANSTAAFL.
not on VAT, there is "no lower" rate on VAT for sellers since it's collected directly for the state. They are having a discount on the profits tax.
Java is not the problem.

Oracle ignoring the mobile OS eco-sytems and not providing either JVM or AOT compilers is the problem.
New way of search by location on Flickr and Instagram
All the more reasons not to make things more difficult than necessary by building those things in space.
Surely Kip Thorne himself has to realize that he's grasping at straws. A lot of the things he mentions are of the type "in this precise, extremely rare situation it is possible, if we ignore all the other side effects". For example, I'm sure his calculations will be correct regarding the planet orbiting a black hole close enough for relativistic effects. What it also means is that the planet would pass through the extremely hot accretion disk twice every orbit, killing everything and evaporating all the water. And considering the speed that a stable orbit would require, that would be a very common occurrence.

The point is: don't claim that you're scientifically accurate. Usually, a good sci-fi movie will set up rules for itself, and follow those rules appropriately. If you make your ruleset "real world physics", you have to be extremely accurate if you still want to make it believable. The rules set up expectations, and breaking your own rules is an instant turn-off for science fiction fans.

The movie shows other cases where it doesn't follow its own rules: they have spaceplanes that can get to orbit from a planet with 1.8 times earth gravity, but not from earth without huge boosters?

For the record: I like Interstellar a lot. It was a great film, and I'll definitely be buying it when it comes out on DVD. I just have my gripes with the lofty claims of accuracy that Hollywood films so love to make.
This is why I prefer to have objects in the DB if they are not too large or numerous for that to be practical, that way the transactional integrity of the DB and its backup handles this. Unfortunately it is not always practical or under your control.

From a developers PoV you can increase the consistency of your users backups by being careful how you order operations. If you make sure the DB is updated after the file is in place and tell the app administrators to backup the database first, and your blobs are insert-and-soft-delete only (you can do updates in an insert & soft delete only way with versioning instead of in-place updates). That way you are never in a position where you have a missing blob, though you might end up with orphans where inserts happen during the time the backup took to run.

Other than that, as you say, you have to stop the app or the app has to have built in support for consistent backups (or integration into your chosen solution).

To minimise the downtime associated with this you can use tricks like LVM snapshots or your OS's equivalent. That way the downtime is only as long as it takes to stop the app, take the snapshot, and restart the app, instead of the full length of time it takes to make the backup (which could be a fairly long time if it involves a full backup of a large DB), and it means you can coordinate the backups of apps that are integrated (or just used in sync) but not in a transactionally safe way, without having to stop them all for the full backup run.

That is the best you can do without explicit support in the app - there is only so much a backup solution can be in control of.
This discussion is exactly why I'm drawn to Meteor. As someone who turns out prototypes and doesn't do full time web development, the overhead of researching all these options every time I try to do something is too much. The cost is that I might not always be using exactly the right thing, and that I'm stuck with Meteor's quirks. The pay off is that it always just waiting to go.

As an aside, I think it's notable what a barrier to entry all this is. If you want to try your hand at web app development the thicket of libraries is not a welcoming prospect...
Type safety is valuable, but you can have equivalent or better type safety in a much less verbose language than Java. e.g. I use Scala - it's not quite as concise as Python, but it's pretty close, and the language is powerful enough that I can express more possible effects directly in the type system (Does this method make an async call? Does it access the database? Does it log audit events?) without the code becoming unreadably verbose.
Thanks! Your first sentence says it (almost) all.
This is the correct response to this article. He makes a big deal out of saying he doesn't need to "choose the right tool" anymore. But then later, he feels compelled to qualify that Java is the right tool for him, which sort of invalidates his former point.

In other words, I viewed this article as a large waste of time. Nothing has been added to what is already conventional wisdom.
We are working hard on making RoboVM as mature as possible. There's already plenty of applications on the App Store using RoboVM. Happy to talk if you need more info for decision making. Ping us at hello@robovm.com.
The top EU folk get a massive monthly budget for assistants and consultants = expert help (for EU MPs, this "extra staff budget" is to the tune of 30k USD per month [1], though often abused to fund family members/friends, just as you'd expect).

So indeed you should be surprised (and enraged) if you think they're not doing a good enough job.

The fact they're not experts has been factored in and provided for by the system.

[1] http://en.euabc.com/word/814
I need only 2 reasons to use this instead of others. Which do you think should be those?
I can second this recommendation. I've used mutt-kz for about two years now as my primary email interface and it's been rock solid.

I came from regular mutt so there was no learning curve, but that shouldn't be too bad either once you get used to those keybindings.
Great trick! Didn't know about this. This may be handy for debugging C macros, as an alternative to run the preprocessor by hand over the whole source just to see the expansion of a single macro.
Too Many 'a's (A poem, with apologies to Dr. Seuss)
Nicely done. I just wonder where to embed these...
As the position requires ten years of experience in Central Texas agriculture specifically, it's probably moot in this case.
Sploria – Travel advice direct from the locals
I notice that you have switched from "poor people" to "poor person with no degree", and from "richer [than poor]" to "rich".

My example was of someone who did not work at all, and has $50 million in inherited money. By definition, anyone who works will be able to outwork someone who never works. How does a poor person "outwork" that multimillionaire?

Classically speaking, I structured this as a worker against an owner of capital. You have responded, it seems, by arguing that capital is irrelevant, and then reclassified "work" to "access to better paying jobs".

I believe you also imply that going to an elite university is an independent factor from poverty. It may be that someone poor cannot take the 4 years off for such studies, and must instead help support the family and take care of an ailing parent. Therefore, these are correlated, with the implication that being rich helps make your children rich.

Your original premise was that working hard is the primary factor, and ignore other systemic biases.
24 Pull Requests is back again for a 3rd year, encouraging people to give back to open source projects that they've been benefiting from all year.

The site itself is also open source: https://github.com/24pullrequests/24pullrequests
SOAP certainly sucks, but regarding your comment on using lisp as the transfer protocol is a bad idea. Data transfer protocols must be verifiable - you should basically be able to write a piece of code that parses the data input and verifies that it will not do something bad if deserialized. Given that as far as I know, Lisp is turing-complete, this task is impossible. Therefore, Lisp, while being a nice programming language, is a very bad wire protocol.
> It's because they make their money from the hundreds of billions of dollars they skim off the top of their customer funds.

The movie Trading Places nailed this, albeit in the context of commodities rather than stocks. But the principle is the same:

Mortimer Duke: Tell him the good part.

Randolph Duke: The good part, William, is that,
no matter whether our clients make money or
lose money, Duke & Duke get the commissions.

Mortimer Duke: Well? What do you think,
Valentine?

Billy Ray: Sounds to me like you guys a
couple of bookies.

Randolph Duke: [chuckling, patting Billy Ray
on the back] I told you he'd understand.
The resume's being sent in for this will be worth a read. I hope someone hacks SpaceX and leaks them. ;)
These Cool Robots Are Processing Your Amazon Orders
That's what we should do, but there is no common economic policy in Europe, and this is collected for the national budgets, not for the European budget. We are talking about shitload of money, half of the French State tax revenue for example.

We are also talking about shitload of fraud.
When ever I use Skype or Lync (things that I need to use at work), I really miss IRC. By default modern IM clients are constant source or distraction. Someone said something? Make sure to ring some bells and blink some notifications. Someone wrote an emoticon? Of course everyone wants to see slightly taller than line height image representing the emoticon. With animations, because why not?

I also really miss how in IRC channels are kinda the default way of communicating. I feel like Skype and others start from one-to-one communication and channels/rooms/... are more like a secondary feature.

If at work I need to ask some question, I do not care who answers to that and in many cases I do not know who has the answer. I do know what team or interest group might know the answer. With channel first kind of IM (IRC) I just join #folks-who-develop-the-server-im-sending-data-to and throw the question in the air. Eventually someone answers me.

With Skype, there is no such channel, because the mindset is different. So I need to browser the corporate intranet to figure out who might be the tech lead of the server I'm sending data to and contact that person. I chose the tech lead because he's the person who most probably knows the answer. Too bad that he is also the busiest one and I'm just making the situation worse.

Also, I really miss news groups. Why each web forum must reinvent the wheel and fail at it? :( I'm not that old, only 31. But boy where things better when I was younger. :D
I just do Android and WP as hobby.

SDL was ok for games, but now with a real app, I tried the Qt way, only to discover there are still lots of issues.

So I figured out, better use JNI and C++/CX directly and save the pain of figuring out bugs in Qt.

In the end, the JNI pain is bigger than figuring out Qt bugs and helping those guys.

For small devshops there is a lot of time to be saved by letting third parties like Digia and Xamarin have to go through the pain of writing platform specific wrappers.

If I was doing mobile OSs for work, I would gladly pay for them.
I'm so sorry to hear that. A very sad and sobering read.

I'm sure a lot of your coworkers and team are contributing, like you said, but it'd be nice to think (if they haven't already) that your actual company would make a reasonable contribution to Nicola and their future child, since it sounds like Steven gave so much to the company (albeit under compensation). I know I would for one of my key and valued employee's, if I were in a position to do so.
Agreed, the java books I listed still provide more value to my core Java than more recent books. I do the majority of my Java work now in the Play framework, when I use a new framework or library blogs and stackoverflow are my go to resources, for a deeper understanding of the library then those books are the way forward.
"Oh but you're working with cool stuff! And you have a foosball table and free lunch"
I'm not sure anything interesting happened in the PL world since 2004 besides PEGs. Please feel free to correct me if I'm wrong, I always prefer to be among the first to jump on a new bandwagon in the language design trends.
I appreciate this effort and will give it a try.

One of my main problem with javascript frameworks is having to drift away from the original server HTML. Not everybody wants to go the whole way down the Single Page Abbit hole. It's not only a question of speed or SEO.

I think many devs are both backend & front-end craftsmen, and as so build the backend first and then wish to 'grow' their frontend part on that foundation. Or ideally wish they could. Instead they have to fork the project into 1). the Good Ol' server HTML part 2). the API SPA part.

No matter how close angular or react (with jsx) stays to HTML, you still need to rewrite the whole view to comply with it's templating needs. There's no incremental evolution there, and worse : having to duplicate and sync maintenance on both ends, breaks the DRY principle which is fundamentally bad - since you end up with 2 sources of truth.

Pre-rendering the view with react on node (even if your on rails or whatever) may be a solution I don't know yet. Another take I guess would be to render your server html files with a template which complies with their JS counterpart. Yet another take would be to use HTML as the API instead of JSON - which is proven to work quiet well.

Anyways, just to conclude I think devs would feel more confident if they could rely a little more on the servers end while the frontend finds its ways and stabilizes a little.
Very cool, now the last step, automate the picker. So no humans are required to do this work. Saves a lot of money. And Amazon can be cheaper still.

This is what IT is all about. Automate the humans away.
Now what are we going to do with all those humans that are not capable of doing work that cannot be automated away?
The movie shows other cases where it doesn't follow its own rules: they have spaceplanes that can get to orbit from a planet with 1.8 times earth gravity, but not from earth without huge boosters?

Normal fuel is just less expensive.
Critical denial of service security vulnerability in OpenVPN
I completely agree with this. Make sure you know the ins and outs of what's out there, but don't just follow trend blindly. Especially with a large team, or internal eco system.

I make a habit out of using smaller frameworks that gets the job done, and only that. Anything else or beyond, we code ourselves, or re-use from a different project. Or we just stick with older technology because we know it works. Sure, our productivity might initially be lower, but at least we save ourselves the pain of "the next big thi—oh wait, something new arrived let's switch".
You wrote "this will impact GDP and thus the state's ability to ...", as if that were a bad thing, or at least something to be avoided.

If so, then your logic says that this "outside of the norm" case is also a bad thing for the country, or at least something to be avoided.

Most would disagree with you. For that matter, my own g'grandmother worked as a maid for a man, who she later married. I don't see why you get to call my family history "outside of the norm" simply because it disagrees with your view of economics.
I came to say the same. If you multiply the number of dependencies, owned by different people, having different interest, you multiply the chances of having to catch up with a problematic update.

On a more general pov, the debate between "integrated design" and "modularized" design has been going on for decades. We know the advantage of both. The problem right now is that angular made a desition to break compatibility in a major way while their framework was barely becoming mainstream. Let's not make it a bigger problem.

People that invested in the .net framework, or in the unity framework, did not make a blunder. All we need is an equivalent in the front end js world.
Upstart startups: Lessons for small fry taking on big fish