skysight-inc/HackerNews huggingface dataset:
I agree with you, however our model of the solar system gives us pretty good confidence about macro level events even into the distant future.

To the specific example of the sun rising - for the sun to stop rising, the earth has to either become tidally locked about the sun, or the earth or sun must be destroyed.

One article[0] says:

Scientists have reliable data on the Earth's rotational speed, based on observations of the sun's position in the sky during solar eclipses, going back some 2,500 years. Although the rotational rate hasn't declined smoothly, over that period the average day has grown longer by between 15 millionths and 25 millionths of a second every year. Even at the faster rate, it will take 140 million years before the Earth's rotation slows enough to necessitate a 25-hour day.

The real crux of this matter is predictive power. We can get a rough understanding of the predictive power of a model by asking the question "at what point does the expected error in our prediction make that prediction meaningless?" For example, how accurate does a population model need to be for us to be willing to use it to predict population distribution in 50 years? It's fair enough to say that our models are not capable of predicting the population distribution in 1 million years, but no model could and it's unlikely we would be able to utilise such a prediction even if it were made.

As I said before, the existence of a profitable life insurance industry is evidence that we are good at making lifespan predictions at the individual level, in aggregate. Every time a policy is written, it's like a wager is being made between the insured and the insurer. Yes the insurers lose some bets, and some years they may even lose a lot of them, but it's clear that the odds are stacked in their favour, for otherwise they would be unable to offer insurance at all.

If you were to bet on what the climate of this planet will look like next year, how would you make your prediction? If you were to offer odds, how would you structure the book to make sure you win?

Yes, the absolute accuracy of climate models is going to diminish over the next 1, 5, 10 years, so the error associated with a specific global average temperature prediction (for example) will increase. That doesn't mean the actual temperature is just going to fluctuate wildly! Next year the global average temperature may decrease. It is extremely unlikely that in 10 years time the average temperature will have decreased, even if there is drastic intervention. Any bookmaker looking to make a profit would be offering odds on how much the temperate increases, not merely on if it increased or not.

Yes, predictive power is going to decrease as time goes on. No, that doesn't mean models are useless, nor that we can't have predictions that become more likely as time goes on.

[0] http://www.popsci.com/jessica-cheng/article/2008-09/ive-hear...
Culture is completely a Moral Agent of Society, and to argue otherwise is ridiculous. Nearly all Art is in close proximity to or a direct result of an internal belief system font of inspiration. How that comes to be expressed by default entails a Message, thus enter twining Morality and Art in ways that can not be separated from Individuals as members of Society.

That's why arguments about separating Great Art from Shithead Artists is a constant conversation of "Is it okay..." among adults who care about such things.
Regardless. The broader point is, Git is a screwdriver and what is needed at this point is a hammer. Sure, we can keep trying to pound nails with a screwdriver but that's harder work and is far less productive.

We. Need. A. New. Tool.

p.s. But there are how many CSS pre-processors? And how many JS frameworks? Etc. Things we don't need. Go figure.
Yes, you compared them, or rather, compared the reactions of people to them. If you aren't implying by extension that SaaS and awsless are comparable then your argument makes no sense.
Coding CSS for Context
Chevrolet’s Bolt makes its ride-sharing debut in Los Angeles with Maven
Test Pilot Tracking Protection Graduation Report
There are good ways and bad ways to use functions, just like any design pattern.
I'm currently doing research with students from South Korea, this surprised no one. They actually have a saying about "Keeping in touch with a cousin's cousin if they work at Samsung." In SK you're considered well off/rich if you or any family works there because it's the main tech business. After Choi Soon-sil the government is seen as corrupt through and through, in glad they're doing something about it, as most of the population (95%) disapprove.
Don't worry too much about making your customer happy - worry about keeping their customer happy.

Or to generalize: make your customer successful and help them look good in their market.
Of course, if you give them the IMEI it facilitates them listening to your phone calls and tracking your location. The 'checking for stolen phones' thing seems totally implausible to me.
This doesn't look like it was a problem with Hibenrate, more of a "wrong tool for the job"-scenario. Reposting what I recently wrote on Reddit on a similar Hibernate discussion thread:

In my experience, ORMs and specifically SpringData-JPA-Hibernate occupy this weird niche in the enterprise spectrum. They are an overkill for small projects and they become a hinderance for large projects, so they sort of sit there for medium projects. If you start with an ORM on a medium size project and it becomes a big project you can sometimes find yourself in an awkward spot where you are writing a lot of SQL (and not of the JPQL kind). With Hibernate/JPA specifically there are so many things that are broken that they just start getting in the way if your schemas become large enough. To me this is really just a manifestation of Behavioral Problem (Martin Fowler, Enterprise Patterns), where relational databases don't really map to objects at all when you get down to it.

Basically, if you are going to do quite a bit of SQL, any ORM will just in the way. Should be plainly obvious to anyone with experience.
This page will serve as a very useful "Who not to hire" page.
We’re a tech company that makes suits so of course we published a hardcover book
"Given the importance of getting the core ABI and the related fundamentals correct, we are going to defer the declaration of ABI stability out of Swift 4 while still focusing the majority of effort to get to the point where the ABI can be declared stable."

Do I read that correctly? Swift 4 will have a ABI under the hood but they aren't going to come out and formally lock it down until after Swift 4?
The idea of "use Hibernate so you don't have to write SQL" while being objectively wrong, also hits on an antipattern I've noticed over and over again. The "- so you don't have to -" anti pattern. Such as "we will configire this in xml so you don't have to write more code". Or "put some code in the database so you don't have to do a deployment process to make changes."

You always end up having to do the thing you were trying to avoid plus deal with the middleman abstraction you introduced trying to avoid it. Anytime I hear someone say "- so you don't have to -" I wince and anticipate upcoming technical debt.
I read your first chapter and loved it!
Cheese is best after the expiration date, if it's 2+ of blue, unpasteurised and soft. I only buy cheese from the reduced shelves, when it's less than half price because its use by date is today - this gets me tasty cheese, and helps limit my consumption (since on the average visit, there's no reduced cheese available).

Not recommended: buying your cheddar this way. That tends to go a bit hard and crispy. Always found that unappealing.

Also not recommended: using this purchasing strategy with raw oysters.
Pfff. I'm working on my second billion!

I gave up on my first...
The Front-End Developer Spectrum
Cycles of War and Empire
I suggest a better title for that article: "How I blame technology X of almost ruining my career when I am the only one to blame because I did not understand what I was doing"
What would I do? I'd take ALL those incidents on GitHub and I'd run them thru some sort of AI pattern recognition algorithm. That would become my identification "engine" (?).

It might not catch everything all the time - since humans are pretty creative when it comes to fucking things up - but I bet it would be pretty effective. Certainly more effective than what we have now. Then if it can keep learning going forward, all the better, eh.
I'd be surprised if the real number was even a net subsidy rather than a net tax. We impose all sorts of extra taxes and costs on the telecommunications that we do not impose on other industries. For example, state and local cable TV franchise fees alone (typically 5% of gross revenue) amount to $5-6 billion per year in the U.S. In comparison, the American Recovery and Reinvestment Act had $7 billion in telecommunications subsidies, and that was a one-time shot.

Then there is the economic deadweight loss created by implicit and explicit cross-subsidies. There is a 17-18% tax on telecommunications services.[1] That is not a net tax, because the money is redistributed within the industry, but it increases prices, which decreases demand, which causes a net deadweight loss. Then there is implicit cross-subsidies in the form of build-out requirements. In nearly every city, you are not permitted to only build out in the neighborhoods where you can count on having enough subscribers to recoup the cost of that part of the build. You have to build out everywhere. The end result is that prices go up in neighborhoods with more potential subscribers in order to subsidize the deployment to neighborhoods with fewer potential subscribers. Again, making the product more expensive decreases demand and imposes a deadweight loss.

The ideas behind these policies are mostly well-intentioned. We want as a society to provide connectivity to rural areas and poor neighborhoods. But the implementations are driven by politics rather than any attempt to achieve the desired end result in the most economically efficient way. We don't pay for SNAP benefits with a tax on supermarkets. We impose a general tax on everybody, to avoid distorting the economy in favor or against any particular industry.

[1] That tax pays for almost all the "subsidies" you hear telecom companies getting. It's like imposing an 17-18% tax on all smartphones, and giving the money to companies building cheap smart phones for poor people. Nobody would call that a "subsidy" to the smart phone industry (it's a cross-subsidy within the industry).
(Ozgun from Citus Data)

I think the answer to your question depends on the workload you're planning to use Citus for. We find that users rely on Postgres for different use cases and Citus' benefits (and worst parts :)) vary across them.

Common use cases, ordered by popularity & benefits, include:

1. Multi-tenant database: Most B2B applications already have the notion of a tenant / customer built into their data model. Citus allows you to scale your transactional relational database to 100K+ tenants with minimal changes to your application -- and with all the benefits of Postgres.

2. Operational analytics: Citus enables ingesting large volumes of data and running analytical queries on that data in human real-time. Example applications include analytic dashboards with sub-second response times.

3. NoSQL++: As we increased Citus' feature set, we found that users started relying on it for workloads that have high read / write throughputs. We have a few "hidden" features in v6.1 that make Citus even more powerful here. That said, sometimes the open source community is way ahead of us on this. :)

4. Other: These include anything from distributed transactions to real-time notifications. Since we extend Postgres, if you're a power user and understand Citus' underlying primitives, sky's the limit. (We debated adding a section to our documentation for other workloads. We just couldn't agree if we wanted to name it Top Gun or Highway to the Danger Zone.)

Our goal in each release is to add new features that makes Citus stronger in use cases where it's already strong, as well as to listen in to our users & customers and look to expand into areas where we already see good adoption.
I love that mindset. By your logic we should all be coding in assembly.
Test Pilot No More 404s Graduation Report
> Software Architect

I found the problem.
Proposition 5 proves that the composition of surjective maps are _necessarily_ surjective only when the second map is monotone continuous. Based on the definition of surjectivity given, you can have a composition of surjective maps that isn't surjective.
Would you want to be able to change your brain so that you can productively work 70 hours per week? I wouldn't - it'd quickly become the standard against which you're measured, while the rewards for passing the test stay about the same.

There's a similar argument to be made for being able to share your life on facebook - it displaces alternative interpersonal interactions, so you have the same amount of human connection except with your social graph sold to marketers.
The AI can be trained to become robust to Adversarial examples.
Not only that, there is work going on right now that aims to recognize all Adversarial examples. Early results are promising.

I fear for the future if the fascists control the neural networks.
Are you able to provide sources for the position you put forth about similar US harassment of political dissidents decades ago?

Obama prosecuted more journalists and whistle blowers than any president in history.

And we're not talking about turning into Nazi Germany. We're talking about why government crimes against their own people, especially for political speech, should never be allowed to happen because they can result in worse outcomes than you would expect.
Wonder if they accept Pastafarians?
> 0.01%

The same could be said about the proportion of innocent people who would be jailed without the presumption of innocence. Yet I still support the presumption of innocence, even though I personally have never needed it. It makes me feel safer and allows me to trust and cooperate with the authorities.
This is why insurance exists. Usually you'll find the big complainers didn't buy it. Evidenced here by the request for more funds on patreon. It doesn't even seem like the loss is irreplaceable, unlike something handmade.

Time and effort cannot be replaced, but the monetary loss at least should be insured against.

Unfortunately byuu made a poor decision about risk. If anything this makes me question byuu's ability to assess risk which is a pretty important skill in someone looking to be an archivist. Throw in lack of accountability and this is someone I will definitely not be supporting.
Who would have thought that buying horses for president's best friend's daughter[1] would be Samsung's ruler's undoing...

(Wow, that's a lot of "'s"'s...)

[1] For those who don't follow South Korean news closely: https://en.wikipedia.org/wiki/Chung_Yoo-ra

She's currently in a jail in Denmark, fighting extradition requested by Korean prosecutors. In addition to tripping Lee, she also got multiple professors in Ewha Womans University arrested for corruption. (Yay?)
As an enterprise IT admin who has handled Windows update deployment for over six years... you missed the point.

The updates should all ship on Patch Tuesday for the reasons above. The problem is that "an issue" has interfered with "all updates" because "all updates" is now "one update".

For instance, one of the things that most articles did not cover about this issue is that Adobe released a new version of Flash Player on Tuesday to coincide with Patch Tuesday, when Microsoft would've released theirs as well. IE and Edge get their Flash Player updates from Microsoft through Windows Update now.

However, that didn't happen this month, because the cumulative broke. And so now people can look at the Chrome and Firefox Flash Player updates and exploit the remote code execution vulnerabilities in IE and Edge, which are now at risk.

In other examples, Microsoft has released updates which broke things like network printing on Windows 10. Enterprises had to make the choice to either not be able to print, or not get security updates until Microsoft finally fixed it two months later. Without the ability to pick and choose updates, when an update has a problem or compatibility issue, companies are going to end up just stopping updates, which is bad for everyone. In the past, we'd just hold the problematic update, but with cumulatives, it's not possible.
How bout you NOT collect this information. It's just creepy that this is turned on by default.
Every compiler supporting separate compilation has an ABI -- the question is whether the ABI changes between releases or not.
I feel like a salesman because I always am bringing up azure but... You might take a look at the azure active directory b2c service. You can use stand alone azure ad or integrate with other various providers (Google, Facebook,etc). Their posted child is the real Madrid website which uses it.
How would using more confusing terms help?
A.I. Duet
You have a lot less to prove to CBP than someone coming from a broken country. Your incentives to stay in the US are drastically less than someone from, say Mexico. Other countries do the same thing. A US citizen gets a warm welcome into Mexico. A Guatemalan gets hassled.

There's still random bad luck - as a Canadian I've been theatened deportation for not cancelling my green card despite not using it or living in the US. I've been detained because a CBP agent decided a trade show was work and I wasn't eligible for a B1. (His first words were "you're going miss your flight, I'll make sure of it".) But most of the time they wave me right by.
There's a word for people who can't refrain from sharing their political opinions with their friends: they're called prats.

Unfortunately facebook in its current implementation seems hellbent on encouraging people to be prats.
The main value of the design patterns is that they have given names to things that were already common and fairly intuitive to a half decent programmer.

But I've come across many people trying to use them as a guide for how to write code - and misunderstanding them. Factory in particular is often misunderstood. It is mainly useful when you have parallel class hierarchies not as some odd wrapper around all the constructors in the software.
Yes we are! There's someone working on Vietnamese [1]. It's a bit blocked on mdbook support [2], but the translation part could start before that's done. Chapters 2, 3, 4, and 6 are effectively "frozen" for print at this point [3] so they'd be the place I'd recommend starting first!

[1] - https://github.com/rust-lang/book/issues/375

[2] - https://github.com/azerupi/mdBook/pull/200

[3] - https://github.com/rust-lang/book/projects/1
You can always mirror the display to a TV so they can see what you're doing.
Quitting Facebook doesn't effectively prevent it from affecting you and your social network.
Hidden Figures Is a Groundbreaking Book. But the Film? Not So Much
> When you write an SQL statement, you are defining what you want and how the tables are related in your context. You are NOT telling the RDBMS what the actual execution plan should look like.

Which is the exact same thing you do when you write a LINQ query against a database context...

Both are just languages that describe what you want to achieve, not how to achieve it.
Well I'm in my thirties, and I'll happily use stuff way past the date.

I also go by my nose, though for some products like milk, I don't mind if it has a smell or some separation. I do make sure to boil it before I use it.

Edit: I also don't use pre-packaged food, I prefer cooking from scratch.
I too have a couch from West Elm (not the Peggy). Don't know the name, because we fortunately got it gratis from my mother in law -- she has a matching twin but their recently downsized abode couldn't accommodate both.

The couch itself looks nice but is a terrible failure for comfort. The rear pillows are above half as tall as a normal persons back requires, making lounging in it a chore unless you have enough pillows to prop you up. My mother in law suffers from the same button plight as the article suggests: they seem to pop off like overripe fruit.

The worst part though is the flimsy legs. Every time I rise from my seat it makes a cracking sound like a wet twig. I know it will give out eventually, because the same couch at my in-laws' place is already propped up by a paint can in one legless corner.

I can appreciate this article like not many I've read before. West Elm truly does suck.
So does excel VBA.

But man, are arrays a pain in VBA.
Sadly, many people will skim the article, including the incorrect first half, and come away from the article with increased misunderstanding.
I'm intrigued that you think that requires an IMEI.
"SQL seems hard" "Here's a tool that makes it so you don't have to use SQL" "Great! Let's use that" - without having done the work to determine if that tool is actually any simpler (hint: it's not)
I'm not sure "so you don't have to" is the problem; it's that do X so you don't have to do Y is only helpful if X costs less than Y.

So use an ORM so you don't have to write and maintain SQL is bad, because writing and maintaining SQL is not expensive, but using an ORM is (at least in my experience: I've run into many cases where the ORM generates pathological queries that aren't fixable without throwing away all the code that was calling into the ORM; where a bad query in plain SQL is usually readily accessible).

On the other hand, use Erlang's hot code loading so you don't have to restart nodes to update code is not bad: hot code loading isn't super expensive (you have to do a little bit of planning for some types of changes), but restarting nodes is (first you have to move all the traffic, then you have to actually restart it, then you have to move the traffic back).
Yes. My college roommate (from Korea) once told me that Samsung is "above the government", when I asked him whether Samsung influences the government.

But naturally they must have enemies within the system. And as a country modernizes, it becomes harder and harder to maintain that tight control. So perhaps the enemies are striking as hard as they can to dethrone Samsung. One consideration is whether the enemies are also Cheabols though.
> People who have an accident may become temporarily disabled, i.e., not able-bodied.

Temporarily -> no need to start over.

> And correctly-designed programs don't have “accidents”.

That's dangerously naive. Many mission critical software has bugs. That's why airplanes for example from Airbus use 'diversity' in both hardware and software. The same functionality is implemented with different sets of hardware and implemented by different teams using different programming languages. The systems are additionally designed for graceful degradation, dynamic reconfiguration, switching to alternative control software, ...

Still: Lufthansa Flight 2904 -> 'Computer logic prevented the activation of both ground spoilers and thrust reversers until a minimum compression load of at least 6.3 tons was sensed on each main landing gear strut, thus preventing the crew from achieving any braking action by the two systems before this condition was met.'

The software was surely not written in Lisp and I also would doubt they would allow Racket 'principled' macros anywhere near Flight Control Software.
This is a very niche use case. The vast majority of projects have neither the user base to arrive to such numbers, no are they I/O challenged. Most companies are not facebook or google.

Plus if you manage to do 50 write sec on this DB, I don't see how you plan to scale anything with it. You are back to use good old sharding with load balancers.
If you're a software dev, don't move to Canada.