skysight-inc/HackerNews huggingface dataset:
Nobody's happy with keeping things how they are anymore, unfortunately. Got to keep moving fast and keep breaking things, no matter how well they worked. Not introducing new features feels like stagnation to investors and shareholders.
This looks like it: http://www.becbapatla.ac.in/cse/naveenv/docs/LL1.pdf
How has Bucklescript-TEA been in your experience? When would you recommend it and how about JS interop?

For those who don't know, TEA stands for The Elm Architecture, so it's like Elm for Bucklescript or Reason. The library's author is also very active in the Elixir community.
you are right. I'm sure Bender has always on internet connection, so he doesn't need a phone to make phone calls:)
70 Percent of the World’s Web Traffic Flows Through Loudoun County, Virginia
You know I already have a spare phone at home. Cost me nothing technically since when I upgraded I just kept it instead of throwing it out.

Reduce, reuse, recycle.

Y'all bitch it's ridiculous (and I ain't saying it's right or that I agree with the premise of having to do it in the first place), I'm just saying thats what people will do faced with the situation.
The system is still based on central bank currency in the background. What is being lost is direct consumer access to central bank currency: they must rely on private-sector intermediaries.
I've wanted a language like this. Java's checked exceptions with some way to offload the bookkeeping to the compiler.

What about other run-time exceptions, like divide by zero? Are they checked?

What about Hoare's billion-dollar mistake (null pointer exceptions)? Does Zig have non-nullable references?
Counterpoint, the best place to spend counterfeit money is a music festival....and then it gets passed down to you. I've picked up a half dozen counterfeits at music festivals. Sucks if you're not really paying attention.
Most of life beyond the hunter/gatherer stage is ridiculous.

It's ridiculous all the way down.
Basically it uses dead reckoning then. Cool stuff! There are other velocimeters, accelerometers, etc. that do that as well, the important part is the amount of error that builds over time. I wonder what this "quantum compass" has for error?
> Commond [sic] Clause is like the Patriot Act, a purposeful misnomer by its authors to attempt to gain unearned goodwill & respect.

The author (not plural) describes in depth the differences between recognized open source licenses v. the commons clause (https://commonsclause.com/) and also describes her intent behind developing the license. Specific emphasis appears to have been devoted toward distinguishing this license as being distinctly non-open in the FAQ printed on the root of the domain.

(To be clear: I have no affiliation with the author or with this license and any known implementations of it.)
You’re describing feudalism. Your station in life depends on your family’s ownership of the right hereditary lands. In 50 years, “were you born with access to a productive city or not” will dominate race, gender, etc. in determining life outcomes.
> you go to the bank and get more cash.

Not sure which country you are talking about but the vast majority of people go to an ATM not the bank to get cash. You still need a debit card to get cash from an ATM.
Except that Downtown is the only place in SD where being car-free is generally possible. SD has terrible public transportation especially now that Amtrak won't run later Coaster routes.
Even assuming we'd want XML as the message/schema format back (with all the security, performance and readability issues it entails), SOAP/WSDL/WS-* was any better than rest in standardization back in the day.

For instance, there were multiple different ways you could format your message (RPC/encoded, RPC/literal, Document/encoded, Document/literal, Document/literal wrapped) and different implementations supported different formats. There were all kinds of extra features that were never supported across board like multi-part messages etc.

Before WS-I there was practically zero guarantee that two SOAP implementations would ever be able to interoperate (and please remember, while REST has no standard in practice, it's dead simple to implement REST by hand - the same couldn't be say about SOAP!). WS-I only came out in 2004 or so, and by then it was already too late. I'd say the SOAP ecosystem is the definitive case study for trainwrecks.

If you really want a standard method for RPC then you're much better off with a modern implementation like gRPC or Thrift or Cap'n proto. Please don't go back to the nightmare called SOAP.
The Netherlands, just as most other countries within the EU do not rely much on the AmEx/Visa/Mastercard payment network, but on V-Pay (VISA) or Maestro (Mastercard).

Those are direct debit transactions which cannot be reversed unlike CC transactions. The advantage for shops is, that the costs are lower than for CCs. In general, Europe isn't used to paying ordinary everyday items with a credit card, which is why grocery shops simply don't accept them.
A lot of people were confused by the paper's probabilistic claim, and tried to correct each other. At the time I'm writing this comment, only one of them has done so accurately and germanely, as far as I can tell.
Australia Is the Testbed for the World's Most Extreme Copyright Blocks
But let's not throw away the baby with the bath water...

A huge value of HSL is being able to verify that you're keeping hue constant. Or, to change hue everywhere slightly (when you decide you want a 214 blue instead of 217).

The second value of HSL is that it's easy to look at a code and understand its brightness and saturation semantically.

But I agree that you absolutely need to manually pick appropriate lightness and saturation values to match what you want perceptually, and that changing lightness often requires changing saturation as well.
How universities should teach blockchain
The problem is when the payment companys are so big and so few, that 1 or 2 companies can basically shutdown an entire business themself (by removing their ability to be paid).

The solution is to use anti monopoly laws to break them up.

I don't think that companies should be forced to do something. What I instead want is for there to be enough competition in the market, such that no matter how terrible your views, there exists at least 1 one who will work with you.

And if there isn't enough competition in a market, then that's a problem.
V-Pay should be accepted by any shop in NL. I am not sure where the issue comes from, as there is no card, specific to the region.

In NL maestro/v-pay cards are accepted 100% of the time, because those cards are issued by all banks there.
The conversation here is interesting to contrast with https://news.ycombinator.com/item?id=18403497.
Really though, what's up with the windows 10 start menu...
Sure. I have a Profile. Let's say I load it from the database and make a change. I want to know if I need to save the profile. This is particularly important when using optimistic locking, a.k.a. resource versioning. My profile has a version number, like an ETag. I only want to update if there is a real change, and updating increases that revision number with every persist.

Here's a scenario. A woman gets married. Her last name changes. She updates the profile from Smith to Jones. The last name is now dirty. The code that save the object can say, "Are you dirty?" The struct says, "Yup". Saving code says, "Right! In you go." On the other side, the bit gets flipped back to false (it's cleaned). At the end, the revision updates by one and goes back to the client.

Another scenario. A user opens the edit profile box, doesn't change anything, but hits save. Without a dirty check, the object, which hasn't fundamentally change, gets saved with a new revision number.

Now what is all this about the revision number? I don't want to allow changes to a profile whose revision number is greater than the revision number my client passes. Let's say the Profile has revision 5. The client, which has been disconnected for a bit, says, "Update the profile, at revision 2, with all this new great data." The system needs to reject that update. The client needs to tell the user, "Sorry. That didn't work. Here's all this new data." If the client is especially Canadian, it will also say, "Oh, by the way we've saved your data, would you like us to copy it over the new data". I've never seen Canadian code, and mine is especially Floridian, but it could happen like that.

All of this is fairly easy in OO languages, which Go is not. It's actually easy in Go too if you use -ters and Setters (Go doesn't like GetFirstName(), but is okay with FirstName()). If I use functions attached to structs, easy. Just curious how other feel about this.
Not being snarky, but there are homeless people in Sweden? In the US we're regaled with tales of the Scandanavian social safety nets. We're told everyone is taken care of. That's not the case?
In over 6 years working in this industry, in projects with anywhere from dozens of users to millions of users, not a single bug I have encountered was caused by a "hidden allocation" causing the process to go OOM. Not one instance.

One of the two examples he cited in his introduction, the Android one, wasn't even caused by an unhandled OOM error. Android by design will kill unused processes if they're occupying memory that the foreground process needs.

If we want software without bugs, removing hidden allocations in languages is far down in the priority list.
What utopia?
It's been a nightmare in making.
Total lack of privacy and financial fascism by fiat.
I agree it's confusing. If you consider a random variable X whose value is the rank of a randomly chosen elliptic curve. Then I believe this article is saying X converges in probability [1] to 50%/50%.

Similarly related is the concept of "Almost Surely" [2]. Wikipedia includes a great example with throwing a dart.

[1] : https://en.wikipedia.org/wiki/Convergence_of_random_variable...

[2] : https://en.wikipedia.org/wiki/Almost_surely#Throwing_a_dart
Performance on the plot is higher than FP32 peak, but there's no error - because FBGEMM does not compute in FP32, it computes in 8-bit fixed point. On a Broadwell CPU, you can do 16 FP32 multiply-adds (2x 8-wide FMA instructions via VFMAxxxPS instructions), but 32 8-bit multiply adds (1x 32-wide multiplication with accumulation of adjacent results via VPMADDUSBW instruction).
Data from Smartphones Proves Cyclists Faster in Cities Than Cars and Motorbikes
There are a lot of contenders. My own unsorted list is Nim, Rust, C++20xx, D, Objective C, Pony, Zig, Crystal, Red, and maybe a form of Lisp (why not Common Lisp). Even more unlikely a maybe and only for the C/C++ trenches of embedded systems, some form of Forth. If Jai ever ships I might consider adding it (at least as a contender to the C/C++ trenches of games and game engines), but it's absurd to think it will have any impact when it can't even be used by anyone other than jblow yet. Even if it ships, I would bet its highest anywhere-realistic impact (which is still damn high) would be to become the PHP of game programming. The mythical C/C++ replacement that everyone will choose when they previously would have chosen C or C++, causing C/C++ to die like COBOL? Much less likely.
> Nuclear energy is currently not a massive part of our energy production.

depends where you are talking about, there's a lot of reactors in the world, plenty enough to do statistics.
It’s also no longer necessary for satellite offices to duplicate headquarters functions. The work done at HQ is infinitely reusable. HQ has near-perfect visibility into the goings-on at each office, so they no longer need independent decision making capability. And the economics have changed to favor quality over quantity: 100 top engineers are better than 1,000 cheap ones. Where are you find the highest concentrations of top talent?
I think it's more likely that access will always be available, however 'immigrants' quality of life will be far lower.

That's already the way it plays out here as far as I can tell.

Young people with regular jobs live in single rooms in flatshares or their parents' homes (if they have that access).

In middle age I expect them to live in small flats whilst their parents lived in large homes.

Over longer time periods, quality of life will decrease across the board and most will be in worse accommodation than the previous generation.

The issue we're facing I think is more that this sort of centralization of productive work is unsustainable. You can't* just stuff the entire population of the UK into London, or the entire population of the US into SF, NY, etc. They'd be bloody awful places to live.

* well, you can. I don't think we should.
You are talking about price, I talk about efficiency. The savings you gain with industrialisation aren't going to last forever. And I stand by my point, I'm unlikely to see a 30% gain in efficiency from wind in my lifetime, there's 200 years of incremental progress on turbines, I doubt we'll improve it by much.
you are not debating. you use this as an opportunity to spread your belief on political correctness. please keep that rubbish to yourself.
Oh cool, I use Sublime also. I actually made a slightly customized fork of this to help out:
https://github.com/unqueued/sublime-notelink

Most people would probably want the more powerful extension[1] which also has wiki link navigation, but it also has some incompatibilities with my setup.

I use a wiki-ish repo. A Journal.md that is my primary work log, but I also make little subpages when I want to expand into something specific or reference something previous.

So, I might do [[2018-10-11_issue_cron-aws-replication-issue]]. If the issue is more complicated, I would just roll it into a more general [[issue_cron-aws-replication-issue]]. I usually don't need to do this, and I try to not let it grow to be too complicated. But having it be somewhat structured has been really helpful. The links can act as tags, and I occasionally use symlinks as redirects. My Git.md page has lots of things I've learned at this job in it.

I keep it synced with my private git repo[2], where the Markdown wiki syntax works seamlessly with the Gollum wiki[3]. This also works if you want to access your wiki hosted on a private github repo.

[1]: https://github.com/SublimeText-Markdown/MarkdownEditing

[2]: https://gitea.io/en-us/

[3]: https://github.com/gollum/gollum
It starts in the center and emanates out. I've seen changes in the county center ripple out for decades, but the pace of that in the last 5 years has dramatically quickened.

Honestly it just takes a different outlook, and the more progressive ideas need to start somewhere. I'm so glad I got to see this first hand and am very impressed. Like I said elsewhere, I'm very grateful for this time Downtown. It has changed my outlook and expectations for wherever I live for the rest of my life.

I've invited my family with a large group of kids to come live here in light of that, and they evolved because of living here too!

In the true sense of the word "awesome" ... it really is. So I am excited to see the entire county evolve by what we do here in its core.
2007: SOAP has won and it won't change

2012: REST has won and it won't change

2018: GraphQL has won and it won't change

2023: ...
Your 2015 MBP had similar processor and ram as your 2012 Air, that seems a bit odd.
Notably, from that site: "Vitess has been serving all YouTube database traffic since 2011, and has now been adopted by many enterprises for their production needs."

(I work at Google, but not on Vitess or YouTube)
> That's not what most people want.

How exactly do you know this?

I would imagine lot of people want their own device repaired.
We're using Argo as a replacement for our GoCD based continuous delivery system and it's been fantastic. We were about to move onto Concourse and realized we would need to set up the and manage the equivalent of a Kubernetes cluster just to support it. We took a few extra weeks to prototype Argo first and were glad we did.

In our use case, the primary deployment model is blue/green deploys of VM based microservices on AWS with a bunch of Terraform managed infrastructure gluing them together. The newer class of service we're developing right now is container based and has even more infrastructure complexity. Teams manage their own service releases and each group has slight variations in their deploy steps. We need a deploy system that can support the old and new style and remain flexible while providing a migration path.

Teams love the flexibility and expressiveness of the workflow definitions. They've begun to move cron jobs onto it as well. Argo is much more lightweight and easy to operate than any other system we had worked with because it leans so heavily on Kubernetes primitives that we already needed to understand. The codebase is also relatively easy to understand, so we've been able to contribute things back to the project while working through the migration.

We've taken a cue from the project and begun to consolidate our control plane on CRDs so they can seamlessly integrate with Argo. CRD Operators + Argo are allowing us to consolidate all of the custom deploy/config tooling we built over the years onto a common system that is testable and well integrated.

It's a little early in the project to measure the full effect, but the internal project has a lot of momentum.
How is this not big news? It sounds like it’s going to unseat GPS as the de facto navigation system.
The first time I experienced a cashless store was Amsterdam in 2013. It was a fast food restaurant. Of course at first I was a little upset but it did get me thinking what are the advantages to the store

The store no longer has to go to the bank to get heaps of change

The store no longer has to take money to the bank

The store will have no money on premises so less of a target for robbery

The store will have no money on premises so no having to trust employees not to take some.

Nothing to account. Just read the total.

In almost every way, as long as there are enough customers it's a win for the store. Many customers love it too. Most of my western friends visiting Japan get annoyed they can't go cashless in Japan because they're used to being cashless where they are from.

I did run into my first no-cash accepted store here recently. It will be interesting to see how it goes in Japan as they are more privacy oriented.

I agree with all the issues of going cashless. It scares the crap out of me, especially when traveling. But, I can't see it not happening relatively quickly.
Except as fish oil supplements relate to heart attacks (headline is misleading IMHO):

> While the overall results were disappointing, there appeared to be a beneficial effect when it came to one aspect of heart disease and fish oil: heart attacks.

> Taking fish oil lowered the risk of heart attack by about 28 percent, which is a "statistically significant" finding, says Dr. JoAnn Manson, who is chief of the division of preventive medicine at the Brigham and Women's Hospital in Boston. She led the research.

> Those who appeared to benefit the most were people who didn't ordinarily eat much fish in their day-to-day diet, as well as African Americans, Manson says.

> African-Americans in the study experienced a 77 percent lower risk of heart attack when compared to placebo, which is a "dramatic reduction," Manson says. Further research is needed to confirm these findings, she adds, but, "in the meantime it would be reasonable for African Americans to talk with their health care providers about whether they may be candidates for taking fish oil supplements."
> All Android based phones have their firmware locked and root access disabled

Xaiomi A1 and A2 come with stock android and official bootloader unlock on the website, takes 10 mins to unlock and install LineageOS. LineageOS root access is an option in the settings.
Those that want help can get it — you can’t force help on everyone, and you need to be a legal citizen. Some are visiting from other EU countries.
Hahahahahaha.

Perfect.

Maybe 2023: gRPC has won and it won't change
That blog post was a good read.

I also wanted to say that I certainly believe that you've done real math and got interesting results from the sort of model we were discussing above. It does seem like, as you say, a rich and natural theory.

That said I wanted to make another counter argument here. Particularly based on the meaning of the phrase "pick a random real number". To pick a number at random is a necessarily randomized process, however it should give a classical output. After picking the number I should be able to make two copies of it, put them on ships flying away from eachother at the speed of light, and both ships should be able to perform the same computation (without entangling particle pairs beforehand).

Moreover any reasonable representation of a real number should admit operations like "what is its n^th digit".

Under these two constraints, you would have to flip an infinite number of coins, and it would take infinite time and space to pick a real number. Or in other words, you can't really.
https://www.nejm.org/doi/full/10.1056/NEJMoa1809944

Abstract:
'It is unclear whether supplementation with vitamin D reduces the risk of cancer or cardiovascular disease, and data from randomized trials are limited.
Methods

We conducted a nationwide, randomized, placebo-controlled trial, with a two-by-two factorial design, of vitamin D3 (cholecalciferol) at a dose of 2000 IU per day and marine n−3 (also called omega-3) fatty acids at a dose of 1 g per day for the prevention of cancer and cardiovascular disease among men 50 years of age or older and women 55 years of age or older in the United States. Primary end points were invasive cancer of any type and major cardiovascular events (a composite of myocardial infarction, stroke, or death from cardiovascular causes). Secondary end points included site-specific cancers, death from cancer, and additional cardiovascular events. This article reports the results of the comparison of vitamin D with placebo.
Results

A total of 25,871 participants, including 5106 black participants, underwent randomization. Supplementation with vitamin D was not associated with a lower risk of either of the primary end points. During a median follow-up of 5.3 years, cancer was diagnosed in 1617 participants (793 in the vitamin D group and 824 in the placebo group; hazard ratio, 0.96; 95% confidence interval [CI], 0.88 to 1.06; P=0.47). A major cardiovascular event occurred in 805 participants (396 in the vitamin D group and 409 in the placebo group; hazard ratio, 0.97; 95% CI, 0.85 to 1.12; P=0.69). In the analyses of secondary end points, the hazard ratios were as follows: for death from cancer (341 deaths), 0.83 (95% CI, 0.67 to 1.02); for breast cancer, 1.02 (95% CI, 0.79 to 1.31); for prostate cancer, 0.88 (95% CI, 0.72 to 1.07); for colorectal cancer, 1.09 (95% CI, 0.73 to 1.62); for the expanded composite end point of major cardiovascular events plus coronary revascularization, 0.96 (95% CI, 0.86 to 1.08); for myocardial infarction, 0.96 (95% CI, 0.78 to 1.19); for stroke, 0.95 (95% CI, 0.76 to 1.20); and for death from cardiovascular causes, 1.11 (95% CI, 0.88 to 1.40). In the analysis of death from any cause (978 deaths), the hazard ratio was 0.99 (95% CI, 0.87 to 1.12). No excess risks of hypercalcemia or other adverse events were identified.
Conclusions

Supplementation with vitamin D did not result in a lower incidence of invasive cancer or cardiovascular events than placebo. (Funded by the National Institutes of Health and others; VITAL ClinicalTrials.gov number, NCT01169259.)'
An Alternate Viewpoint on Global Warming: Dr. Patrick Michaels