skysight-inc/HackerNews huggingface dataset:
It's really not all that good, because you aren't thinking in terms of careers. A (real) engineer goes to school to be an engineer, gets his license to practice engineering, and from then on is largely assured to receive increasing salaries from that point onward. Sure, the tools may change, but real world experience on actual engineering problems is seen as irreplaceable by employers.

A developer by contrast is judged by the tools he uses just as much as his tenure, and his tenure becomes a net negative after a period of time. Because wages rise faster and stagnate faster, corporate types see them as replaceable sooner. This might not mean much to people who hop from job to job every year or two, but for a lot of people, they just want a place to work and feel secure.

I know a hell of a lot more 80 year old lawyers, accountants, doctors, and engineers than I do 50 year old developers.
Java circa 2005 had a whole lot of problems, but if you ask me, the biggest problem of it all was that many of the 'solutions' to the problems were worse than the disease.

Back in the day, a friend of mine brought me in to write business software in Java for a small retail company. They didn't have much money, but they also didn't have any management that cared about our technical decisions, so we had a freedom that helped our careers tremendously: Nobody is making any less than 3x what they did then. But along with that freedom came the responsibility of getting the decisions right.

Hibernate was a great improvement over the awfulness that was naked JDBC, but the risks to bad performance were so terrible that we ended up just writing some decorators to make JDBC usable instead. Years later, I went to a big enterprise place, and saw what happens when developers stop learning SQL, and use hibernate to run complex queries.... and then I learned how big of a bullet we dodged.

Hibernate wasn't the only bullet though: One that Java is still suffering from is Spring. We decided that exchanging boilerplate you compile for XML was not a good tradeoff. Later they added annotations, but still, handing all of that wiring to the runtime is just not a good idea. Spring also taught people that it's easy to just have objects that can be constructed in ways that are broken (zero param constructors were easier to use), made application startup slower than even EJB, produce error messages that make the Clojure compiler seem friendly, and added all kinds of insane nonsense that made Rod Johnson quite rich, but didn't help Java itself move forward. Java 1.4 and java 5, out of the box, are like a person with a broken femur. Instead of fixing the bone, most of the ecosystem was just feeding the patient oxycodone: The result was that the patient still had a broken bone that was setting incorrectly, and the patient was now addicted to opiates. And yet, the people that wrote the bad tools that caused this have nice houses in Nob Hill and get to try to build new startups, now selling us their magical solution to the microservice problem.

The Java ecosystem only started to move forward when Ruby on Rails came to town, and, despite all of it's own problems, made it clear that the whole thing had to move forward. Now the JVM has far better languages than Java, and Java itself has actually improved in important ways, but that was due to competition, not bad solutions to problems.

I think we are back in the same boat with NoSQL databases: The companies selling tooling that did well didn't do so on good engineering, while the companies that did the best engineering struggle. But is the whole movement a good idea, or are we just going to see something like Spanner come in and the technologies that people got so excited about were just low quality solutions to problems that most of the time we didn't even have?

I think there's more to learn from the pattern of how developer tools succeed (and fail to deliver), than from just the lesson of Hibernate's tremendous shortcomings for anything complicated.
For a real life Scala.js app see https://github.com/jducoeur/Querki
Maybe this is out of inexperience, but having worked with Rails' and Django's respective ORMs, some of the things, about Hibernate, from this article like, lacking migration support seem a bit strange. And never having used it, feel like I am not seeing the complete picture.

Anyone with having worked with both, care commenting ?
After a long writeup about the treachery of ambiguous problem statements, the article ends with ... a misleading ambiguous statement:

> the ukulele-playing and dancing ambitions would affect the probabilities about the sex of his sibling.

I suspect that this whole article would have been much better if was written by one of the interviewees instead of the jouralist. Sigh.
SQL needs marketing. Become obsolete unless you understand this durable persistence and functional, high-leverage reporting service!
I feel like the there is something similar at play in long distance running. By repeating the same motion a lot, your nervous system probably works out the most efficient pathways to activate and can work without your conscious mind getting too involved.
At one point in my (non-military) career, I spent a ton of time onboard a LHA/LHD (the types of carriers mentioned above). They are impressively huge. You had no way of knowing if the ship was at sea or not. Even at the time - more then a decade ago - I remember thinking that with anything more competent then a harrier - they could do damage.

That said, a carrier force is also a networked force. They have planes and ships all aligned in a sensor network to project power over the horizon. I don't see them doing that with LHDs.
It just dawned on me that the president of South Korea is female. Its even more surprising when you realize that most korean families think very conservatively when it comes to the female role in a family household.
Office Hours with Kat Manalac
This was using the latest toml and serde releases, which I think does use that new attribute stuff (which is fucking cool btw). But no warning from cargo until it was compiling the dependencies.
Google Pixel: How Google designed its first real phone
Let's say you get 50 writes / sec per node. You need what, 1000 nodes to get to the playing fields of Postgres, with a simpler and cheaper setup ? Right now it's really not competitive, unless they improve the performance 1000 times. It makes no sense to buy and administrate many more machines to get the power you can have with one machine on another, proven tech.
Blogspam of

http://magazine.ar.fchampalimaud.org/more-serotonin-less-mot...

The original has more links and references; the original author credit (Ana Gerschenfeld) was stripped out of this.
For some reason that page has the title "Macros - The Rust Programming Language"
Seeking feedback on Lean UX research tool
Customer Feedback, Fast and Slow
When I click on the play button, it opens a new tab that says "You must log in first." with the login prompt below.
my take on hibernate, or ORMs in general, is really to abstract the _differences_ between vendors' sql implementation (including creation, and upgrading of schema). If you have to ship a product that have to work under all database vendors, an ORM like hibernate is the only choice - otherwise, you'd have to write separate scripts for each vendor, and that just makes the job at least 5x harder (or more, assuming you go for more vendors).

Not kwowing how to write proper SQL is a problem, and ORM won't solve that for you.
Questions like “Which paradigm is better
for modeling the real world” are virtually meaningless. The choice depends upon how the world is
conceptualized, and what additional properties are expected of the model.
How to build animated microinteractions in React
I live in Washington and go to Whistler quite often to mountain bike. I've probably crossed the border 25 times in the last few years, and the only thing that the Canadian border patrol seems to care about is that I'm not bringing weapons into Canada. I wonder if they have knowledge that I have a CCW in WA. But in general they are always quite polite about things, which I can't say about crossing the border on the return trip.
On Vision
Yes, it's a small but real risk foreigners should consider every time they chose to cross the US border.
At a given point in time yes, but to get this data set, you need to write it into the DB. Big datasets implies either you have been receiving data for very long of you did it quickly on a shorter period of time. It's usually the later. Which mean you need fast writes. 50 writes / sec is terrible, even more if to improve that you need to buy more servers while you 30 euros / months postgres instance can deal much more than that.
But the problem is that AI can fail in unexpected ways.

Humans are much worse than AI when it comes to self-driving tasks like image/pattern recognition, sure. But they are inefficient in expected ways where measures can be taken like having larger and brighter signs, stronger rules, etc. But what happens when you don't know for sure when it can fail and when it won't?

It's been a few years since people are seeing the magic of machine learning but something like this was just discovered. Are you sure if someone goes in front of a Tesla with a picture like the parent comment quoted, it wouldn't crash and cause harm to the people inside?
There are quite a few CEOs who have gone to prison in the US[1]. The Tyco scandal was a big one.

[1]http://www.huffingtonpost.com/2012/05/18/top-10-ceos-sent-to...
ReactOS 0.4.4 Released
The SaaS Video and Phone advisory solution for business
Selling to an existing public company makes the shares liquid just as well, without incurring (much) more Sarbox waste. Look at AppDynamics, Oculus, Supercell, Dollar Shave, and many others.
I sort of sympathize though because there is overwhelming pressure to use the latest fad in software engineering. At one point Hibernate was the cool new thing, so cool that even non technical managers heard of it. And you really don't want to have to explain to ever busybody non programmer why you aren't using the cool new thing they are reading about. Even if you do explain yourself well, there is a chance they won't understand and will just assume you are incompetent or behind the times for not using Hibernate. Much easier to just use the damned thing and hope for the best.

If you doubt me on this, I challenge you to go to a typical enterprise and develop a web page with vanilla js or HTML forms today. Or build a data project without using something like Spark, even if you only have a few hundred MBs of data.
Why haven't you done it already?
Doesn't seem like that common of a problem to have to ship code that has to work with different databases. But if I ever had to do such a thing I would just stick with ANSI SQL.
Here's the books he has written: https://www.cs.utah.edu/~shirley/books/index.html
Yeah, that makes sense, they would totally be using it.

Still, upgrading to those releases _should_ have taken manual intervention; how were you depending on them in your Cargo.toml? And I guess you had no Cargo.lock for some reason?
I used to think I needed to learn an ORM to be able to write maintainable software.

However time taught me writing maintainable SQL with good migration story is way better. ORMs make porting queries to another project that needs to use the same database difficult.
It's less obvious what is really happening and the performance usually isn't as good as hand written SQL.
Hand written SQL also means fine grained control over prepared queries, access to vendor specific features (advisory locks, LISTEN/NOTIFY, triggers), materialised views etc.

You could argue these should be domain of DBA but in my opinion all devs should atleast know SQL at this level.
Help Find Planet 9
Sounds like the sort of thinking that leads to apps that depend on a slew of "cloud" vendor services and 5 different saas api's (plus their collective cloud requirements) because the developer doesn't know how to hash a password or resize an image.
Weird, I'll file a bug, thanks.
I think JIRA uses it. I vaguely remember the query format for it being a form of JPQL.
Silicon Valley’s Startup Machine (2013)
I love this. Ha lisp doesn't have a good OO system. Lisp 5 minutes later: Implemented a powerful one out of macros...and u were saying?
I much prefer:

var query = from c in db.MyTable
where lessThan == null ? true : c.MyColumn < lessThan
where greaterThan == null ? true : c.MyColumn > greaterThan
where name == null ? true : c.Name == name
select c;

Although IQueryable supports your approach also:

var query = db.MyTable;

if (lessThan != null)
query = query.Where(c => c.MyColumn < lessThan);

if (greaterThan != null)
query = query.Where(c => c.MyColumn > greaterThan);

if (!String.IsNullOrEmpty(name))
query = query.Where(c => c.Name == name);

var results = query.ToList();
Hibernate didn't ruin his career, SQL did. If he'd actually worked with Hibernate, rather than abandoning it for SQL at the first opportunity, he would have got a system that performed well for less effort, was database-independent (which makes it easier to e.g. have a better test suite, because you have a wealth of in-memory options for testing so you can afford to run more tests on each build) and was more maintainable. All too often I've seen it play out like this:

1. Hibernate system working great

2. Idiot notices that one of their queries is slow, blames Hibernate

3. Idiot writes their query in raw SQL because hurr durr SQL is faster than Hibernate. (Bonus points for never benchmarking anything. Extra bonus points for switching to SQL and adding an index at the same time, observing this makes it faster, and deciding it's probably the switch to SQL that made the difference)

4. Idiot notices their query is getting results that are inconsistent with recent changes that went via Hibernate.

5. Rather than making any effort to fix this properly, idiot disables all caching in Hibernate. There, I fixed it.

6. Idiot notices that Hibernate queries are now slow (gee, ya think?) and uses this as a reason to migrate all other queries to raw SQL.

Hibernate doesn't save you from having to design a good data model, nor from having to tune it for performance. You can't turn off your brain when using Hibernate, you do still have to figure out which entities own which side of their relationships, and when you get to a scale where performance becomes an issue you do have to spend a bit of time doing performance tuning, just as you do when using SQL. It does genuinely simplify a lot of things and save you from writing a lot of boilerplate. But if you spend a week tuning your SQL query and no time tuning your Hibernate query and use that as your benchmark, no shit the SQL will be faster, and if your first resort whenever you hit a slow query is going to be to bypass Hibernate rather than working with it then yeah you probably shouldn't be using Hibernate in the first place.
You're going to see fewer and fewer comparisons to GPUs, since Intel has finally figured out that users don't want to cram all their data into a PCIe lane. The current generation of KNL is not really a coprocessor -- it's self-hosted, so instead of a crapload of dual-socket Xeon processors with MIC cards hanging off them, you have a crapload of single-socket KNL processors, on which users can run x86 code directly. nVIDIA is still superior, in my eyes, but they're going to need to get nvlink figured out and deployed, because Intel has basically started deploying accelerator cards with no CPU layer needed -- and no recompile, either.
Gotcha, thanks for clarifying! That's not what I see; I'll try to figure out why that happens.
In this story, Monica was able to actually get to year 4. What's to say that if she went with raw SQL, the team never would have been productive enough to match their run rate. For every story there is of a successful team who rues using an ORM, how many teams are out there who are lost to the obscurity of failure thanks to not choosing a fast over correct solution.

Now, this is not a judgment for or against SQL, given there are plenty of users of Hibernate, it has clearly worked for some teams. Equally, given people still write SQL, I am sure it has worked for many people.

Fundamentally there are two questions to my post:

1 - how much could have been saved in this scenario by a better team

2 - how often is it that the right solution now becomes the wrong solution later?
Java developers?
I'm using scala Slick for huula, should I have this concern too since the development there seems really like just a one company effort.
So writing C "so you don't have to" write assembler is an anti-pattern?

I think the real anti-pattern that leads to ORMs is the fact that languages have no way of natively dealing relationally with data. This is the real origin of the impedance mismatch problem. Languages still deal with data using hierarchical and linear models.
It wasn't showcasing the humanity of the victims that provided the commentary, it was the commentary on how the anti-semitism rose to a level within the general population that reenforced for me the humanity or "normalness" of the perpetrators.
In the long run it could hopefully be a good thing, if better corporate governance results in Samsung improving its operations and becoming even more innovative.
I agree based off of what I've read so far. It's not bad, just not great.
Extrapolating your argument to the extreme: why write ruby when you can write C? Why write C when you can write assembly? Why write assembly when you can write binary?
It is sort of a promise the drug will still work. Short expiries don't cost them sales and limit bad publicity and other hassles.
There's no such thing as ANSI SQL for real world applications on real world databases. Even something as simple as limiting the number of rows returned varies widely (TOP vs LIMIT vs rownum).

The correct answer is to forget about database independence and double down on just one[1] so you can use it to its full potential.

[1]: And obviously it should be Postgres...
- Facebook's mission is "Make the world more open and transparent."

That was not their original founding mission. It was

"Thefacebook is an online directory that connects people through social networks at colleges [Harvard only][2004]"

In 2006 that mission was changed to include other universities and colleges.

Which is a long way from their current stated mission.
In other words, mission statements evolve - and the founding mission is seldom the final mission for many companies.
It's simply a guarantee of full potency of the drug. A while ago, a study (currently looking for it...) found ~90% of OTC drugs were perfectly fine 10+ years after the expiry date, IIRC. And most antibiotics should be just as stable as aspirin.
My First npm Publish
This article: http://blogs.tedneward.com/post/the-vietnam-of-computer-scie... is 10 yrs old. It is clear and to the point.
ORM is a bad choice. Take a little time to Learn SQL basics, it is easier than any programming language.
There's always a little chance of getting infected even with the vaccine.

Herd immunity makes that chance orders of magnitude smaller.

It's not about forcing people to protect themselves. It is about forcing people to not increase the chances of my kids dying of a completely avoidable issue, just because these other people believe in fairies.

Your freedom extends as far as where mine starts.
Look, if you write clear sql anyone will be able to read it. ANSI sql can be read by people even from other languages. You need to wrap it layers of bizarre abstraction and tape on language specific orms. How else will you keep your job?
Chaining and failing on first error is only useful for the most trivial of error situations. Non toy programs handle errors with retry strategies, alternate algorithms and fallbacks which may all be contextual.
> If we could go back and rename Windows Hitler would anyone be using it???

That didn't take long. https://en.wikipedia.org/wiki/Godwin%27s_law
> We’re always struggling with lazy/eager fetching problems. At one point, we decided to do everything eagerly, but it seems suboptimal, and besides, sometimes it’s not possible to access some fields because there is no session, or something like that. Is that normal?

WTF. No concept of the N+1 problem.

> We’re still struggling with which database engine to use for the final deployment. I thought Hibernate was portable, but we have some native queries that use some MS SQL magic, and we’d actually like to go with MySQL in the production

WTF. Why are you developing against MS-SQL then?

> Sometimes we spend days looking for errors. It seems like we have to analyze Hibernate-generated SQL because we have no idea why it’s not working as expected and it’s producing unexpected results.

WTF. If you don't understand your ORM you won't understand the queries it generates.

> Can you help me understand how Hibernate cache works? I just don’t get it. There are some first/second level caches. What is this all about?

WTF. No concept of using transactions.

I've used ORMs longer than the term ORM existed. I've never once thought it as a replacement for SQL. It's a supplemental tool.
There's a lot of external influence on the Korean government. A significant amount of Samsung shares are foreign held. The larger foreign investors are concerned about the structure of these Korean giants based on familial ties and want Samsung to break apart ownership.

The Koreans are a weaker country heavily reliant on the presence of the US' external peace keeping force to deter aggression from their neighbors. There's a significant amount of pressure even by US firms for Samsung to abandon their primitive tribal familial structures within their corporations.
Ive seen this in the UK Aus and NZ but never in the US. I wonder if it is because US stores stick to a perhaps rational strategy where discounted items cannibalize profits?
I would rather expect the same laws that keep you from defacing or removing a stop sign would apply to modifying one with noise to make it invisible to self-driving cars.
Ask HN: Why 'new' instead of 'newest'?
Why the most recent posts here at HN is under the tab called 'new' instead of 'newest' ? At first glance, it looks like it's meant for a new submission.
The charges against Samsung and Enron CEOs are completely different.

Former, it's bribery. Latter, some insane level of securities fraud / book cooking.

Judges would come down harder on the latter.

But it's an interesting question.

Basically this is equivalent a major U.S. company like Boeing or Disney indirectly bribing close friends of Trump to gain political favor.
Background: https://news.ycombinator.com/item?id=13007234