skysight-inc/HackerNews huggingface dataset:
I can read a hopeful, personal story without screaming survivorship bias.

OTOH, I can't read a generalization about the fate of others supported only by a a hopeful, personal story without screaming...“unwarranted
generalization from personal experience”. To even rise to the level of survivorship bias, it’d have to be based on others experiences, but distorted by the relative visibility of the successful examples.

None of this has anything to do with self-victimhood, as I'm not in the graduating-into-the-current-situation group at whom the unwarranted generalization is directed.
We had a pretty similar experience with elm around cookies. The elm-lang/cookie repo README starts with "Cookies are an ancient mistake of web browsers. They make a bunch of security problems quite easy, so consider this an expert library." However, they never address reading cookies, so if you're using a framework that does CSRF protection with cookies, you have to use ports, which adds quite a bit of complexity for something as simple as making an API request.

Elm looks great on the surface, but once you start digging in you really start to realize it's "there" way or else. It's too bad, the ideas have a lot of promise, but we pivoted away quickly after running into the "core arrogance" a couple of times and went with Typescript/React/Redux.
The Future of the United States Depends on the Immediate Adoption of UBI
Exactly, pretty much any parallel algorithm is embarrassingly parallel (gather or calculate a bunch of data, process it and merge it together) so I question the need for continuously needing in-process parallelism instead of solving it trivially.
I wrote a short meta blog about this thread. I analyzed all of the personal blogs in the comment section using Wappalyzer.

https://news.ycombinator.com/item?id=22822401 + https://www.dannysalzman.com/2020/04/08/analyzing-hn-readers...
Oh hey, that's my post.

I first wrote it back in 2018, and just updated it yesterday with some additional links and comparisons.

(Actually was considering retitling it after getting some feedback last night, but given that the link just got submitted here, I'll leave it as-is for now.)

A few quick notes:

- If you haven't looked at Redux in a while, please try out our official Redux Toolkit package [0], which is now our recommended approach for writing Redux logic, and the React-Redux hooks API [1]. We're going to be teaching both of those as the default approach for using Redux going forward.

- We have a new "Style Guide" docs page that gives our official guidance on suggested usage patterns [2]

- On that note, I'm working on an ongoing major rewrite of the Redux core docs [3]. My current task is creating a new "Quick Start" tutorial, which will be a "top-down" intro to using Redux to stand alongside the existing "bottom-up" tutorial sequence. The goal of the Quick Start section is to quickly introduce Redux concepts, and show RTK and hooks as the "right way to write Redux code", without going into the details of how it works under the hood, so that folks can get started now and learn the underlying aspects later. I've an early partial WIP draft PR up [4], and hope to finish the first draft in the next few days. Once the Quick Start page is done, I'll be turning my attention to rewriting the main tutorial sequence in order to remove outdated terms, clarify explanations, and teach simpler patterns (like using "ducks" files instead of splitting code across multiple files).

If anyone's got questions on anything I wrote in the article or otherwise Redux-related, ask away!

[0] https://redux-toolkit.js.org

[1] https://react-redux.js.org/api/hooks

[2] https://redux.js.org/style-guide/style-guide

[3] https://github.com/reduxjs/redux/issues/3592

[4] https://github.com/reduxjs/redux/pull/3740
Please add a license file. Without one people can't legally use the code you posted.
Frequency of change and rate of change are very different. C++ (now) changes at about the same rate but in larger, less frequenct increments.
The tech industry is a class-, gender-, and race-biased inter-generational wealth transfer scheme masquerading as an industry. Past a post of base-level competency, and excluding strategy-level technical roles, employment and compensation is based on identity and not proficiency.

It's the same as with industry labor in the last half of the 20th century. Every person who retired with a pension was not an unequivocal value-add to their employer; there was a need to support and enable the consumptive lifestyles of the public (but only the "right people"), lest the entire system implode.

No one wants to admit that they're mere cogs, compensated for not gumming up the money machine. They want to believe that they have value. And they do, but it's implicit in their identity, not necessarily their productivity. If you don't believe it, ask how much your colleagues in India make.
> In particular the switch to .await syntax happened just couple weeks before it was finally stabilized

The syntax was introduced in May, while the feature was stabilized in November.
Indeed look for the layout and grid components in your ui library. Semantic-ui-react has direct implementations as react components as well with code samples so no need to write any css yourself unless you want to do super custom stuff :)
You can't sue a company just because they made bad investments.
Agree. So I assume that most of the unemployment is in the travel/hospitality/restaurants/retail (etc).

Hence, even after the economy is open, it would be hard to get those people back to work until the "enhanced" benefits run out.

I.e. I expect to see a lot of restaurants/hotels open but with no employees. Or, they will be employees, but their wages will have to be increased by 50%, which would cause runaway inflation.

If this happens, this might lead to spike in automation (AI).
Man, this is infuriating. What does Google say when the hotels call to correct the information?
I'll second this. I've read many "why I'm leaving <x>" posts and regardless of the degree someone might agree/disagree with the contents, it's a very fair article. That's difficult to pull off, I'd say.
Duly bookmarked - nice reference!
Data-driven study of N95 filtering facepiece respirator decontamination
I've been working in Elm for a few years, and I feel like I can answer some of the questions.

0.19 introduced a new restriction on Native code (javascript), previously you could compile kernel code in your own projects, now you can't. You've never been able to publish a package using native code to the package site (only packages under the elm or elm-explorations github namespace can).

If you feel strongly about it there are ways around it, forking the compiler, or giving your project a fake "elm/whatever" name so that the compiler will build it, there is also a set of shell scripts on github that allows you to get around the restrictions. I've used it before to make some tooling to track virtual-dom performance.

The biggest miss in the post in my view is not looking more at using Custom Elements for the internationalization needs. Having a custom element where you pass in a posix time and have it formatted using the Intl APIs is very possible, and it also allows you to wrap up the interface between Elm and JS in a nice, type-safe way.

The 0.19 upgrade was fairly large, but manageable. Our app was around 70k LOC when we upgraded from 0.18 to 0.19, the upgrade was fairly smooth, and it hugely improved our build times. I had actually forked the 0.18 compiler to improve build times, full builds took around 2 minutes, and incremental builds around 45 seconds. In 0.19 full builds take 4 seconds and incremental builds less than a second.

I share in some of his experiences as well, I have had posts deleted on the Elm Discourse page for mentioning a way for someone to run a fork of a core package to get a fix. I stopped working on a private package manager for Elm after someone described an existing solution as a hostile attack on Elm.

Overall the benefits of Elm still outweigh the downsides for me, no other language I have used has made development a joy like Elm has, refactoring is honestly fun, change whatever you want, follow the compiler errors, and at the end everything works again. Packages are generally high quality and work, an Elm package that hasn't received any updates in a year probably isn't abandoned, it's finished. Coming back to code I haven't worked on in a while is easy, the type system has my back, and most Elm code looks similar due to using the elm architecture and elm-format.
Cool! How do you transfer documents to your main computer?
Honestly, I put more faith in a random internet person sharing their opinion on HN using a bit of logic, reason and current reality than I would someone who actually considered themselves to be an "economist" (which btw fully deserves air quotes whenever saying outloud).
I haven't used Elm, so I have no horse in this race. But I feel like I've been hearing these stories for a while, that it started out as an interesting and useful language but kept having features removed in new versions. Since it's open-source, and apparently there are existing projects in older versions of Elm that would effectively be held hostage by these feature removals, I'm amazed there hasn't been a (well-known) fork yet.

Has anyone considered making a compatible fork of Elm?
You're missing the point of the example. Substitute tomatoes with something with a long shelf life, like Spam. It doesn't matter. The point is that the people utilize leverage (loans) in order to fund investments that will yield a return greater than the interest rate paid on the loan. People don't use leverage to buy milk, cigarettes, and gasoline, which are the types of goods tracked in the Consumer Price Index (CPI). They use leverage to buy assets. So when people say that inflation has been low despite the unprecedented amount of money printed over the last 10 years, they're only looking consumer goods and not assets.
> The thing about 50lb sacks is that you can't store the flour in the sack after you open it

You could make it into ship's biscuit. It'll keep for years, and you can always use it in soup or something.

https://www.youtube.com/watch?v=FyjcJUGuFVg
Here it's mostly "partial layoffs". Basically you're still employed and can be asked to work at any time (e.g. 40% on Monday, 0 until Friday and 10% on Friday). When not working, 80% of the salary is paid by then unemployment office.

As far as I know, it means you cannot do another job instead, you're still on payroll. Though individual employer might show goodwill.

As a result, "real" unemployment has barely increased, but about 1/3 of the workforce is on some kind of reduced hours (or their company has signed up for the scheme, though not necessarily reduced hours yet, it's not clear to me).
Are there examples of how humans are/were able to outrun an animal until it collapses? I find it difficult to imagine unless you corner the animal and have enough manpower to not be run over.
One advantage of an economy like this is that in another year or two, companies will have been humbled a bit and will not be looking so far up the corporate equivalent of Maslow's hierarchy, and will either be more focused on things that actually matter, or will be dead.

Unfortunately, we have to get through this bit first....
Sure: great -it can be used with other sorts of models as well, but it's really not that big a deal, and can be implemented in a lazy afternoon. I'm pretty sure lack of this as a first class language feature is holding back exactly no DL frameworks or programming languages, and glueing it onto Swift isn't going to make DL people use it. I've never used Swift's repl; I suppose that might actually be something that gets people on board.
There isn't a good option in the UI to view the next or previous entries in this five-part series, so here are the rest if anyone is interested:

[Part 1]: https://voxeu.org/content/long-view-globalisation-short-part...

[Part 2]: https://voxeu.org/content/long-view-globalisation-short-huma...

[Part 4]: https://voxeu.org/content/long-view-globalisation-short-grea...

[Part 5]: https://voxeu.org/content/long-view-globalisation-short-new-...
Education Without Truth in Postmodern Perspectivism
Show HN: A Vehicle Routing Problem solver written on Rust
Fascinating story, it is unbelievable what humans can survive
it’d be quite stupid to give up your job in this “economy” for a benefit limited to 4 months.

Beyond that, it just shows that minimum wage is nowhere close to covering basic necessities, especially for families.

Even if the mechanism you fear does start happening, the result would be that employers would (finally) have to raise wages. Win-Win!
Securing WebViews with Chrome custom tabs
I too graduated with a CS degree from a highly ranked technical University.

It was probably the worst time for recent graduate with a CS degree. You hear news of all jobs going to India. Nobody in the US was hiring developers. In fact, they were getting all laid off.

I had to scrape by taking odd jobs here and there. I worked as a short-order cook, made jewelry in a factory, worked at a UPS warehouse, etc. It felt hopeless and felt like I wasted money and time getting a CS degree.

Eventually I joined a tiny web-shop for super low pay. I was underpaid for many years afterwards. In 2006, I joined a "real company" but still was underpaid. I quickly left that company and started making more money elsewhere. I got nervous in 2008 since that recession came right when my career started to get good and stable. But I was safe, and it was smooth sailing.

My story has survivor bias. But it took a lot of hustling, grit, depression, etc. from 2001 to 2007. It can take a long time to get back on your feet, at least in my case.
And don't expect it to support normal transactions or participate in distributed ones
So sad but true.
https://www.anandtech.com/show/15708/amds-mobile-revival-red...

The battery life alone just seems so appealing! Coupled with the CPU grunt, this is an ideal machine for someone like me that plays CPU-intensive games, and spends the rest of his time compiling code and running lots of programs. I wouldn't mind a dedicated Ethernet port, so I am eagerly awaiting reviews of the beefier Zephyrus G15.
I played for hours and hours, and at times was utterly confused — but enjoyed just exploring the worlds. I think I finally beat it by copying with pencil on the school bus a map a friend made of the pattern needed for something in the library.
It does, actually. What matters is that there is a king, not who is the king.

The saying works because, as you say, it suggests a successor, but the successor has to use the same title, because what people want is a new king, so that nothing changes and they can live as they did before the king was dead, not a revolution with a civil war tainted in blood.

If you do volontarily change the title, it's because you think the new one will be better, which is pretentious.
It baffles me that you can even write "academia isn't a real job" while the entire planet is desperately hoping for biomedical breakthroughs. Almost all of the people working on COVID have advanced degrees; many of them work in academic labs.

As for teaching, if you want to be intubated by someone who once a post about it on Medium, well...best of luck.
Information Extraction from Receipts with Graph Convolutional Networks
Thank you very much! The base template is from here: https://github.com/luizdepra/hugo-coder/

Over time, I made small changes, added side menus and re-designed the landing page.
This is a satirical piece, for the unfamiliar.
States need devs who know 50y/o computer language to process unemployment claims
I feel like error handling in Node hit a nadir in 10.0 due to async function stack traces being so truncated. I started in the industry when Java was young and while I appreciated stack traces plenty, I hardly ever had to deal again without them, and you really do come to depend quite a lot on this behavior.

Officially we are upgrading to 12 for perf, but I was the first (and will probably be the primary) contributor to that work because I want everyone to have decent stack traces again. Our code has too many layers of abstraction, and working without full traces is adding insult to injury.
Type I and Type II Errors: The Inevitable Errors in Optimization Experiments
It was fine on consoles, but on PC it'd lead to some weird behavior, like the monitor switching modes as it returned to the desktop and then went back into 3D mode as the newly-launched EXE ran its init code.
A/B Testing Doesn’t Impact SEO. At All. If You Do It Right
Will differential programming be able to solve the halting problem?
This is super cool. I wonder if there's anything like this as a vscode plugin
> Is it really that hard to distinguish reassuring rhetoric from a scientific claim?

Nope.

For instance, if you can differentiate survivorship bias (which this fails to even reach up to) from a valid statement supported by objective evidence, you have, in fact, literally distinguished mere reassuring rhetoric from a scientific claim.
"I am afraid the big hit will come in the second wave" Quite possible, yes, but do not live in fear, friend. This is a great time to eradicate fear and embrace the chaos :)
Also, I wonder, could there be any effect of a population decrease from an exodus from NYC?
Did ATP ever have a guest on the show before?
Ask HN: What is your relationship with open source software?
Hello!

A friend and I are in the process of exploring ideas on how we can give back to the open source community in novel ways. While we are very excited these ideas, we wanted to reach out to the open source community and see what their thoughts were on the subject. If you are able, please take a few minutes to fill out the linked survey. It is 100% anonymous and your input will go a long way towards helping us drive our vision to help the open source community flourish even more than it already has.

Survey - https://forms.gle/NGxpZcuM2UpJBx6e8

Thank you for your time!
App Stores have a lot of problems that push developers away from them:

1. Apple have a history of convoluted review processes and arbitrary rejections. It has a terrible reputation amongst devs.

2. Thanks to unpredictable reviews you can't time when a new upgrade becomes available to coincide with e.g. website changes, emails.

3. The App Store can't upgrade apps whilst they're running.

4. App Store 30% standard cut is far too high when a developer could sell direct from their website and pay 2% or less to a card processor.

5. The App Store UX is itself pretty bad. There's no flexibility or ability to customise how your app appears.

6. Devs are forced to allow app reviews and ratings although they may not wish to have that e.g. because users use reviews as a way to request support instead of an actual support system, but you can't reply.

7. App Stores often create problems for corporate or managed desktop deployments.

8. For software that is billed, despite exhorbitant fees their billing engines can be primitive. For instance even years after launch the Windows app store had no ability to do bulk discounts or other kinds of completely normal retail strategies. I don't know if it does these days, but I do know of an app developer who shipped via the WAS and whose business was badly hurt by Microsoft's lackadaisical attitude towards basic features like that. They could have sold big into education but couldn't get much traction because there was no way to offer reduced rates to schools.

9. App Stores enforce random policies unrelated to the core mission of app distribution. For instance the Mac App Store is extremely vague about to what extent plugin mechanisms are allowed. Good luck implementing an IDE or browser in the MAS; you'll always be living in a grey zone. It also forbids any kind of custom licensing mechanism or copy protection, so when Apple's is insufficient you're SOL and requires all languages to be in the same bundle yielding huge downloads (=lower conversion rate due to failed downloads). Those are just implementation limitations but you aren't allowed to do better.

Basically, Apple don't have a good track record of creating an excellent developer experience with their app stores. On mobile they forced devs into it against their will. On desktop where backwards compatibility prevents it, devs have nearly universally rejected app stores ... even when an app is in it, it's common for websites to direct users to their own distribution points.
Hopes for a Coronavirus Drug
I didn't look deep enough to be confident, but I don't understand Rust's issue with do notation.

It already has monads, and uses them in a lot of places. Do notation is just syntax sugar.
Simple and secure transfer of funds abroad
Follow up:
eevBLAB #73 - Medtronics Open Ventilator + Others UPDATE - YouTube
https://www.youtube.com/watch?v=TltM74rNasM
Deep dive into the Central Bank Digital Currencies and how fintech can benefit
Your link, interesting as it is, doesn't point to any particular criticism of the idea, and given its age might not be much relevant today anyway, had it done so.
In 'fairness' to the poster, if they're relying on CNBC for their perspective, they're idiots unless they're really young and haven't been burned before by the mainstream media's reporting.
For work we’re in the process of switching from one to the other and the join meeting links on invites are now half functional on both. I wonder if this is the culprit
Mostly what happened at that large company is customers would call their sales guy, their sales guy would call me or someone who knows and we'd tell them ;)

A few customers could call me directly too, I didn't mind that, they were good folks.

It's not a good process, but it is what naturally happens.
This criticism is spot on; it is exactly what I observed in late 2018, early 2019 as well. It's an awesome language, but there is basically a big case of 'vendor lock-in'. Certain compiler features are only available to the maintainers, nor is there any way to use alternative package sites.

I don't want to know what would ever happen if the Elm developers decide to take https://package.elm-lang.org offline. That will leave so many projects out there in an unbuildable state. Even if you saved source tarballs of the core packages, there is no way to tie it into the build yourself. The Elm compiler must load it through the official package site.

I would thus personally strongly advise against using something like Elm to build any piece of software that needs to be maintained over time. It's too much of a risk.
> My company currently uses the LGPL version of Qt, and would gladly pay for the commercial one. In the Trolltech and Nokia days they actually did pay for it, but the prices are no longer affordable us. So we are stuck with the LGPL version for now.

Huh, price isn't even a THAT big problem. Software developed with LGPL version can't use the commercial one.

> 2.13. If I have started development of a project using the open source version (LGPL), can I later purchase a commercial version of Qt and move my code under that license?

> This is not permitted without written consent from The Qt Company. If you have already started the development with an open-source version of Qt, please contact The Qt Company to resolve the issue. If you are unsure of which license or version to use when you start development, we recommend you contact The Qt Company to advise you on the best choice based on your development needs.

https://www.qt.io/faq/

IIRC they aren't really willing to give the permission to switch
We’ve had high res astrophotography long enough that I expect we should be producing time-lapse video of lightyear-scale events.