skysight-inc/HackerNews huggingface dataset:
I was taking a Game Engines class at my uni last semester and we had to add scripting to our C++ engines using Duktape (or it's C++ counterpart, Dukglue.) It was surprisingly easy to use Duktape once you figured out the initial boilerplate, and it was especially exciting and fun to be able to write a demo game using the engine in two languages (especially with one which didn't require recompilation!)
>We will see an economic depression, also caused by energy problems. The current quantitative easing is actually the first sign of the problems with energy:

One of the only realistic takes in this thread. The current, generationally low price of oil is built entirely upon the output of North American fracking. Fracking is the most capital intensive business on earth at the moment and most players are actually losing money. They are bouyed by the current, generationally low interest rates which are built upon politicized central banking policy. When interest rates rise, fracking grinds to a halt. When fracking stops, the price of oil shoots to 2008 or greater levels and the global economy grinds to a halt. The century scale economic depression that will result entirely invalidates each and every prediction made by the author of the article we're discussing.
I'm partial to killerFS.
Or 7 (is it now?), based on a thread above, organic civilizations become machine civilizations, which can colonize much more efficiently because long journey times don't bother them, and more stealthily because they can make do with comets and moons and such that won't support organic life.
Fasttracker II clone in C using SDL2
It's also funny he compares it to caviar which today is almost all farmed and is as cheap as it's ever been in living memory.
On the other hand, life is extremely frugal with energy. The foundations of biological systems are ridiculously efficient, and all the complex life forms are pretty good too. Despite being designed by a biased random process, they have at least this going on for them: the fitness function favors energy-efficient systems. Unlike our markets.
Do you mind sharing your iphone app or website?
I remember 5-6 yrs ago I tried to create an app using Pascal to remove cache/temporary files, fix registry errors and a few optimizations like popular "optimization/speedup" apps. I wanted to show the progress on progress bar but see what: the process just took 0.3-0.5 seconds and the progress bar is not required anymore. But I wanted to show it anyway and put random amount of wait time (sleep) between steeps. I didn't realize why the popular apps needs 3-5 minutes for the task that my simple app just needs 0.5-1 second.
On the central conceit about people underestimating how much happens in a decade... how much has happened in the last decade?

I feel like very little has changed in the last decade. Technologically, socially, politically, it feels like we’ve lived through a decade of very little noticeable change, especially compared to other periods such as 1990-2000 or 1980-1990.
>No, professionally minded teachers do no such thing. The pay at private and charter schools is roughly 50% to 70% of publics' pay.

Is that the average or median figure for pay? Because I can tell you right now that in LA and San Diego the most common starting place for teachers earning or who have just earned their credentials will either be juvie or low income neighborhoods albeit this is from a highschool perspective so maybe I'm simply wrong with respect to the article. Maybe if you account for public schools in higher income neighborhoods then teaching publically remains competitive and I failed to acknowledge that in my earlier post but the overall picture for a starting teacher is none the less that they will work to either escape public school or ascend out of bad/high-turnover schools.
Forced labor of any sort just seems tricky especially when there is a racial disparity among those so penalized. Prison work programs also seem like a good idea ("teach a trade" etc.) but then they are couched as essentially slave labor and they sound less good.
While I completely agree with most of this article. I think some of it is untrue. A lot of the new functionality is needed for a increasing amount of apps.

For example, I work on an app which wouldn't be possible on the web 5-10 years ago. It's a single page app because it needs to be. It uses a lot of javascript making many requests because we have to and the customers requires it. We could probably make it a lot faster, the issue is that the amount of functionality that we are trying to include in a short amount of time leaves us no other choice than to include yet another library etc.

I know this case maybe isn't the kind of app the article is targeting. But I think even "simple" apps today often include some part of complexity that would be hard(er) to do in a "old style" multi page app.

That being said, I use a lot of old style apps. I use the old reddit instead of the horrible new one. I use HN, I use fastmail so I do think speed is very important.
To be honest, I have never seen any phone or computer that could boot in about 2 seconds. 6-7 seconds is the absolute minimum I've ever seen, regardless of hardware or OS.
Yes both appear to be a disaster. Vuejs is a bit better imo but i'm generally holding out for the next thing.
Whenever I read articles like this I often wonder how much overhead is due to security concerns, and how much that overhead and additional complexity contributes to the problem of slower software.
> Since he presumably meets the qualifications for many countries

Actually he doesn't, because one of the very basic requirements is to not commit perjury in the application by providing a document claiming he was an US citizen when he was not.

And I find it highly unlikely that an employee not only forgets to fill in the box attesting his legal status in the US but also an anonymous third party happens to fill it, and fills it the wrongest (and most convenient) way possible.
The irony is, Web 2.0 was enabled by a performance improvement! It's only once JavaScript engines became fast enough to be useful that all these troubles on the Web started.
This will save United Airlines a _lot_ of money!
This genius talk is so wrong. I have an bachelors in engineering from a state school. I've worked in Haskell with multiple people with no computer science education. You don't need to be a genius to know Haskell, and knowing Haskell doesn't make you a special genius.

And in my experience, the Haskell codebases I've worked in best exemplify the axiom you mention. I've solved so many problems by barely using my brain thanks to FP.

The main prerequisite is a good attitude.
Sure: If you can optimize the software that runs on many millions of computers then you can have a huge impact. If you run those computers yourself you can even save money.

But the vast majority of software is one-off stuff. It makes no sense to optimize it for performance instead of features, development time, correctness, ease of use, etc.
The main benefit of 5G is for the cell carriers. With more spectrum available and various channels usable in a more efficient way they can provide more total bandwidth if they want to. Seems likely they will just slowly inch up the speeds in a game of chicken with the various carriers. Of course they will whitelist speedtest.net. :)
As an American public school student who was forced to listen to this arrangement in multiple music and history classes, over the years I've begun to find this startling and anxiety-producing piece suspect on multiple levels. The copyright squabble is kind of funny though, they just couldn't help themselves.
WindExchange: Wind Energy Information by US State
“For Isildur would not surrender it to Elrond and Círdan who stood by. They counselled him to cast it into the fire of Orodruin.”
Similar to many of the other comments here: you should figure out what "success" means to you. It's easy to make the default assumption that success means lots of money and long working hours, at which point you've defined success in opposition to work-life balance. (Not that it's necessarily wrong to do so, but I'd contend that it is problematic to do so without explicitly deciding that this is what you want.)

I'd estimate I work 40-45 hours most weeks, with occasional bursts of 50-55 hours pre-deadline often compensated for by shorter weeks afterwards. The popular myth of insane working hours aside, this is actually pretty normal [1] in our industry. I get to work with awesome people on projects that I care about, I earn enough to live comfortably but not lavishly (as do many people in this industry), and I have enough time / energy left over to enjoy hobbies, friends, and travel. I also get to learn continuously and enjoy reasonable latitude / autonomy in decision making.

To me, this means I've been pretty damn successful. Could I have more of these things I've described? Possibly, though maybe not more of all of them at once. Am I living the hyper-optimized best possible version of my life? Arguably not, but it's also not clear to me that this exists; all important choices involve tradeoffs, and what's optimal now may not seem so to 5-years-later me. Personally, I've found it healthier to accept that my definition of success has changed and will change further, and that finding success is maybe not as important as searching for it :)

[1] https://insights.stackoverflow.com/survey/2019?utm_source=so...
I guess I still don't quite get most GraphQL designs or why a lot of people jump to implement it... I have always thought the big idea behind GraphQL is you already have endpoints (likely rest) which are cached/optimized? And then GraphQL becomes a layer over the top to map/reduce client requests for more optimized request/response cycles for clients (and I guess decouple some business logic)?

Which then makes me wonder why this is the "dark side" of GraphQL? Isn't this just not optimizing a query somehow or using a cache effectively? Is it really the nature of GraphQL that's causing this to be slow or just programmer error [1]?

I've used GraphQL in production services as an alternative to a rest endpoint (which I didn't care for) and I don't think sheer the nature of the validations ever caused that much slow down or rather, more plainly put that GraphQLs design would not necessarily cause such poor performance on such a small set of data.

/shrug I dunno, if this were me, I'd just assume I had written a bad query or validation somewhere. And to be fair to the author, they only made a post on twitter to reflect on their problem, not to say GQL has a dark side (at least from what I read in the thread).

[1] We all have made programmer errors, are likely making some "now," and will for sure make more in the future. No reason to feel bad about it, we're all human :) Mistakes are just a part of life no matter how "good" at things we are.
<fry>I see what you did there</fry>
I think it would be better to drop name and I suggest naming it

FiberFS

Also, it would be helpful to have a comparison table with ZFS BTRFS and other others from technical implementation and features
Only did a quick search but it seems like it's the iOS package name for the Amex Mobile app[0]

[0] https://www.americanexpress.com/uk/customer-service/digital/...
I don't understand. What's a "principal thing?"
My point is that unions arise in a free market, so the price with unions is the market price.

You need to show that unions are unnatural before you can claim that they aren't the market price.
The Smartest Book About Our Digital Age Was Published in 1929 (2017)
And yet at the time of its release, iOS 11 was the most buggy version in recent memory. (This record has since been beaten by iOS 13.)

I don't quite know what's going on inside Apple, but it doesn't feel like they're choosing which features to remove in a particularly thoughtful way.

---

Twenty years ago, Apple's flagship platform was called Mac OS (Mac OS ≠ macOS), and it sucked beyond repair. So Apple shifted to a completely different platform, which they dubbed Mac OS X. A slow and clunky virtualization layer was added for running "classic" Mac OS software, but it was built to be temporary, not a normal means of operation.

For anyone invested in the Mac OS platform at the time, this must have really sucked. But what's important is that Apple made the transition once! They realized that a clean break was essential, and they did it, and we've been on OS X ever since. There's a 16-year-old OS X app called Audio Slicer which I still use regularly in High Sierra. It would break if I updated to Catalina, but, therein lies my problem with today's Apple.

If you really need to make a clean break, fine, go ahead! It will be painful, but we'd best get it over with.

But that shouldn't happen more than once every couple decades, and even less as we get collectively more experienced at writing software.
The music is in the public domain, but the copyright status of recordings of music in the US is very complex. For example:

"In 2005 the landmark case of Capitol v. Naxos pitted a distributor of 1930s foreign classical recordings (Naxos) against the putative holder of the U.S. rights to those recordings. The judges of the New York State Court of Appeals ruled against Naxos, but they used the opportunity to go much further than that. They declared that since New York State had not passed explicit statutes dealing with recording copyright, it was in fact governed by “common law” (i.e., law declared by judges in their rulings). In their opinion sound recording copyright in New York derived from the laws of seventeenth-century English kings. It was absolute and perpetual. The rights holders have all rights, forever, and the public has none." (Capitol Records, Inc., v. Naxos of America, Inc., 830 N.E. 2d 250 (N.Y. App. 2005).)

See: https://recordingcopyright.org/pdf/AMuscop_fnl.pdf

Therefore, it is illegal to copy and distribute an old recording of Rhapsody in Blue if the recording was made in the US.
It's just the underlying model that is similar, but React is pretty good at abstracting all that (unlike Win32).

When it comes to developer experience I'd say that React and company are ahead of most desktop UI technologies, and has inspired others (Flutter, SwiftUI).
For reference: this was specified in article 14 of the new EU copyright directive. One of the few good changes in it:
https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CEL...
>Utter tripe. The only part of being a teacher outside the public school system that’s better is the average quality of the students.

Apparently a lot of teachers care heavily about this going by turnover rates in low-income public schools which are often the starting schools for fresh educators.
Programming is now a bureaucracy.

[1] "In any bureaucracy, the people devoted to the benefit of the bureaucracy itself always get in control and those dedicated to the goals the bureaucracy is supposed to accomplish have less and less influence, and sometimes are eliminated entirely"

[1] https://en.wikipedia.org/wiki/Jerry_Pournelle#Pournelle%27s_...
it's sort of self-fulfilling-prophecy to talk about how bad the name tarnishes the project, while simultaneously explaining to everybody your opinion about why the name is bad.

anecdote : I asked a young developer near me 'Hey, do you know the Hans Reiser story?'. The reply was 'Who?'. The reply came from someone familiar with the filesystem, and that general line of work.

tl;dr : Reiser is just a name. It was recently the name of a 'bad guy', but it hasn't always been, and won't always be.

p.s. I've lost data with ReiserFS too. I'm glad I don't have any need for it any longer.
In 1995, search engines were both worse and better. They were worse because they tended to rely on word frequency, boolean search, and an inverted index. They were better for the same reason. The search engine returned results based on what was in the box. It didn't second guess the user.

Even when Google arrived, it was not clearly better (at least for me) because it was hard to drill down a search by refining the specific search terms. But it was more adaptable to the first generation SEO methods.
No more than 1000LY, per this article:

http://www.setileague.org/askdr/howfar.htm

i.e. 1% the diameter of the Milky Way:

https://www.universetoday.com/21998/the-diameter-of-the-milk...
I think this gets to the underlying criticisms. GraphQL is not the replacement for REST and by nature an improvement - it is an alternative to REST based on a certain set of pain points. If you’re a large org with multiple consumers and your API development is silo’ed, then GraphQL may solve a set of problems you have that a small homogeneous team may not.
> Screening mammography aims to identify breast cancer at earlier stages of the disease, when treatment can be more successful. Despite the existence of screening programmes worldwide, the interpretation of mammograms is affected by high rates of false positives and false negatives. Here we present an artificial intelligence (AI) system that is capable of surpassing human experts in breast cancer prediction. [...]

> In an independent study of six radiologists, the AI system outperformed all of the human readers: the area under the receiver operating characteristic curve (AUC-ROC) for the AI system was greater than the AUC-ROC for the average radiologist by an absolute margin of 11.5%. We ran a simulation in which the AI system participated in the double-reading process that is used in the UK, and found that the AI system maintained non-inferior performance and reduced the workload of the second reader by 88%. This robust assessment of the AI system paves the way for clinical trials to improve the accuracy and efficiency of breast cancer screening.

So, there you have it: AI not "either/or" humans, but both, in conjunction, as a composition of the best of both worlds.

At the very least, that's how civilization will massively and intimately introduce true assistant AI.

It's also somewhat counter-intuitive to think that the most specialized tasks are the low hanging fruits; i.e. that the "difficult" to us, culminating years of training and experience for humans (e.g. how to read a medical scan) may be, per its natural advantages (like speed and parallelism), "easy" to the machine.

That space (where machine expertise is cheaper than human) roughly maps to the immense value attributed to the rise of industrial-age narrow AI; therein lies not a way to replace humans — we never did that in history, merely destroyed jobs to create ever more — but rather to augment ourselves once more to whole new levels of performance.

Anything more than this is AGI-level, science-fiction so far — and there's not even a shred of evidence that it's theoretically a sure thing, possible in the first place. Which is not to say that AI safety research isn't extremely important even for the narrow kind (manipulation comes to mind), but we shouldn't go as far as to bet future economic growth on its existence. Like fusion or interstellar travel, we just don't know. Yet, and for the foreseeable future, because scale.
It doesn’t help that I get headaches when I eat my garden grown tomatoes. No such reaction to eating a ribeye. How tall will my children grow up to be on a plant based diet? I want my children to grow up to be stronger than those around them.
this is the most neurotypical post of the decade. names are irrelevant. I would run HitlerFS if the performance was good.
In my opinion, most the predictions made here are dumb, to be honest.

It seems like a mix of wishful thinking and linear projection of a few trends this particular VC happen to like, but nothing bold or creative, nothing that could make me think and wonder.

Are most VCs living in their own world or something?
It's much worse than that: what is the environmental cost of buying a new phone because Slack runs too slowly on your old one?

The things I'm doing on my phone today are not fundamentally different than what I was doing ten years ago. And yet, I had to buy a new phone.
I guess it depends on what your definition of success is. I still average around 40 hours/week in the office as an SDE 3 at Amazon. I could probably advance a bit faster by putting in more hours but I'm happy with the pace so far.

I think there's a lot of hustle porn culture in tech, especially around the entry level where people brag about how many hours per week they spend leetcoding. This creates an unrealistic perception that everyone is always working themselves to the bone. They're not, my last company even did half day Fridays during the summer.
Any link on ml use in medicine ?
Not only are you supporting user freedom, you're also not at the mercy of a business model designed around planned obsolescence and selling your data.

Tuya-convert is a wonderful project and has liberated about a dozen devices on my network so that they will run Tasmota until the day they die.
China's Social Credit System is pegged to be fully operational by 2020
Apple is one company I've been willing to name as it's extremely frustrating to have such a sub par experience with such expensive products. I used to be a huge Apple fan, and now I no longer use any Apple products. I've never used Catalina, but iOS is unbelievably buggy now so I'm not surprised.
The cool thing about this for me is that list of the 'worst of 1924'. It highlights that we're trying to preserve ALL media. Not the best of the best, not some cherry-picked list made up by a bunch of critics. Every single flat comedy, ever unoriginal love song, every boring book, it's all being preserved, if found. Because even bad art matters and, besides, it's not bad to everyone. It's important to keep this attitude for the upcoming years of works, where there'll be much more stuff to save. Let's not just take care of Hitchcock's and Chaplin's and so on. Ed Woods of the world deserve remembrance as well.
The type and timbre of the instrument used, the speed and volume of playback, any post-processing decisions, etc. are all creative choices and thus can make a resulting work copyrightable.

Be careful using generic music from the Internet.
That works for balancing the Senate, but not really the House.

Adding PR to the House would significantly reduce the odds of a Republican House given that the current GOP makes a lot of noises that often seem like they're racist against Hispanics.
It's all fine until - as it often is - we want to do that task more often. Any task worth doing once is likely worth doing more than once; any task worth doing across many people is likely to be worth outsourcing to a business focused on it.

Using a real example: in a certain company that wife worked in, there was a task that - every couple of days - would be repeatedly done by multiple office workers for several hours. I was visiting that place once, and since I had to wait for my wife, I was asked to give them a hand with that task. Growing frustrated, I very quickly located a hidden option for batch processing they didn't know anything about. It solved the entire task in couple of minutes. By finding that option, I freed several man-days a month for that company. Time that can be used for other tasks (or even goofing off).

This example sticks with me because these days, a lot of work is done in front of computers, and every inefficiency there removes productivity from the economy. The way I see it, if you're developing software, and there is a possibility that that software will end up being used by someone in their job, you owe it to them to make it efficient; by ignoring efficiency, you'll be robbing such people of their life and mental health, and their employers of potential profit.
A small issue with number 5. How is an average technologist going to do any better with things like tax policy, immigration policy, energy or foreign policy than an account, lawyer or civil engineer? I wonder if we would all be better of trying to use technology to get good candidates in office that are not beholden to large agenda driven donors.
And as we all know, Google never kill a product.