skysight-inc/HackerNews huggingface dataset:
I'm sorry whoever I offended enough to downvote this. I didn't realize whale skeletons were a touchy subject. I'm not an American so I don't know.
For sure, you have a valid point.
Svelte. Interesting framework, I dipped into React then tried Svelte and loved it initially - very noob friendly.

I really liked having HTML/CSS/Js all in one place.

But then tailwind became popular, and I realised I could get this same UX with React + Tailwind.

Now I prefer React + Tailwind to Svelte.

No Svelte jobs, weird compiler magic. Hated SvelteKit
Ironically.. 2.5 Gbps is created by taking a 10GBASE-T module and effectively underclocking it. I wonder if "automatic speed selection" is around the corner with modules that automatically connect at 100Mbps to 10Gbps based on available cable quality.
They also posit correlations with epigenetic differences. If there’s distinct biological mechanisms at play, this gives some credence to splitting autism into separate conditions
Immich uses SvelteKit for its frontend: https://github.com/immich-app/immich

I’ve used it as a reference for a NestJS+SvelteKit app in the past, they did a pretty good job.
"How does that make Elon Musk a con artist?"

Because since 2014 he has made wildly unrealistic claims that he is smart enough to know were BS.

December 2015: “We’re going to end up with complete autonomy, and I think we will have complete autonomy in approximately two years.”

January 2016
In ~2 years, summon should work anywhere connected by land & not blocked by borders, eg you're in LA and the car is in NY

June 2016: “I really consider autonomous driving a solved problem, I think we are less than two years away from complete autonomy, safer than humans.”

October 2016
By the end of next year, said Musk, Tesla would demonstrate a fully autonomous drive from, say, a home in L.A., to Times Square ... without the need for a single touch, including the charging.

"A 2016 video that Tesla used to promote its self-driving technology was staged to show capabilities like stopping at a red light and accelerating at a green light that the system did not have, according to testimony by a senior engineer."

January 2017
The sensor hardware and compute power required for at least level 4 to level 5 autonomy has been in every Tesla produced since October of last year.

March 2017: “I think that [you will be able to fall asleep in a Tesla] in about two years.”

May 2017
Update on the coast to coast autopilot demo? - Still on for end of year. Just software limited. Any Tesla car with HW2 (all cars built since Oct last year) will be able to do this.

March 2018
I think probably by end of next year [end of 2019] self-driving will encompass essentially all modes of driving and be at least 100% to 200% safer than a person.

February 2019
We will be feature complete full self driving this year. The car will be able to find you in a parking lot, pick you up, take you all the way to your destination without an intervention this year. I'm certain of that. That is not a question mark. It will be essentially safe to fall asleep and wake up at their destination towards the end of next year

April 2019
We expect to be feature complete in self driving this year, and we expect to be confident enough from our standpoint to say that we think people do not need to touch the wheel and can look out the window sometime probably around the second quarter of next year.

May 2019
We could have gamed an LA/NY Autopilot journey last year, but when we do it this year, everyone with Tesla Full Self-Driving will be able to do it too

December 2020
I'm extremely confident that Tesla will have level five next year, extremely confident, 100%

January 2021
FSD will be capable of Level 5 autonomy by the end of 2021
Lol, it’s insane how some people will track everything back to AI
There's also the fact that TCP has an unfixable security flaw - any random middleware can inject data (without needing to block packets) and break the connection. TLS only can add Confidentiality and Integrity, it can do nothing about the missing Availability.
A negative outcome is a system failure, even if it is a personal failure that drove the outcome, because that is a failure of the system to prevent personal failures from causing negative outcomes.

You can't stop personal failures from happening because people are people. You can design processes to minimize or eliminate those personal failures from yielding negative outcomes.
It is cultish doublespeak.
I'd make the argument that people are very good at dealing with random things that shouldn't be on freeways as long as they don't coincide with blinding sun or other visual impairment.

Tesla had a long standing issue detecting partial lane obstructions. I wonder if the logic around that has anything to do with this.
As the guidelines [0] state:

> Please don't post comments saying that HN is turning into Reddit. It's a semi-noob illusion, as old as the hills.

See the link for some examples, but I can also recommend looking at some old front pages from over the years and poking through the discussions. Unscientifically, it seems that quality is pretty similar to me.

[0]: https://news.ycombinator.com/newsguidelines.html
It's amazing what you can do with just gears, cams, and levers. Project-Rho provides a quick survey of mechanisms. https://www.projectrho.com/public_html/rocket/astrodeck.php#...
Edge cases like intersections?
> I don't see how these definitions help me write better tests

> What I would like to see instead …

If you hire me, I can address those needs.
Kinda: https://svelte.dev/blog/runes

> Svelte 5's reactivity is powered by signals, which are essentially what Knockout was doing in 2010. More recently, signals have been popularised by Solid and adopted by a multitude of other frameworks.

> We're doing things a bit differently though. In Svelte 5, signals are an under-the-hood implementation detail rather than something you interact with directly.
Nuclear reactors are not nuclear bombs. Nuclear reactors are very safe on a Joules per death bases
Different opinions is not the problem. My own opinions differ plenty from my peers. Even that the opinions are outside my Overton Window isn't itself a problem, because (as with most of my nationality) that window excludes the 2nd Amendment and yet I can be here on this American website.

Problem is, quite a lot of the weird stuff looks like defections in the IPD sense.
https://archive.is/wOQDL#selection-633.0-633.39
This is actually very well known: current QUIC implementation in browsers is *not stable* and is built of either rustls or in another similar hacky way.
> Could you expand more on why this seems like evidence that Google unilaterally dictating bad standards?

I guess I'm just generally disgusted in the way Google is poisoning the web in the worst way possible: By pushing ever more complex standards. Imagine the complexity of the web stack in 2050 if we continue to let Google run things. It's Microsoft's old embrace-extend-and-extinguish scheme taken to the next level.

In short: it's not you, it's your manager's manager's manager's manager's strategy that is messed up.
End-to-end tests verify high-level expectations based on the specification of the system. These high-level expectations generally stay stable over time (at least compared to the implementation details verified by lower-level tests), and therefore end-to-end tests should have the best maintainability score.
Shovel sellers predict that definitely a lot of shovels are going to be sold in the coming years.
40-50C? What is the brand?

Mine were over 90C, resulting in thermal shutdowns. I had to add an improvised heat exchanger to lower it down to ~70C: https://pics.archie.alex.net/share/U0G1yiWzShqOGXulwe1AetDjR...
Another area that could be open and cooperating in the operating system is network controllers, most have an offload engine of some kind but you can't extend what it does or fix bugs in it.
Doesn’t tell me anything i don’t already know
A lovely write up.

Regarding the formatting of commit messages: if everyone on your team is doing things slightly differently is something going wrong and what could fix it?

Is it a respect issue: people don’t follow a consensus because everyone is a headstrong individualist who refuses to play along with others?

Is it a communication problem? Are people just not intermingling in the commit message culture enough that they all naturally converge on a house style?

Is it a leadership issue? Are there no clear leaders in your engineering team who collude — consciously or subconsciously — to set the tone for everyone else?

Is it a technical issue? Without a pro-forma commit message template or additional tooling, are you failing your eng org by not giving them the framework / training wheels / guard rails they need to align on a house style for technical documentation?

I’ve been part of very healthy teams who largely ended up self organising into a consistent house style with a little help from tooling. I’ve also been part of unhealthy teams who fork themselves into multiple internal cliques that don’t intermingle enough to build up a monoculture. The healthiness of the teams might correlate with the commit message / commit graph style, or it might not. I wonder how it could be done better.
Who has he mistreated?
Large Language Models and Transformers
Pretty much everything you've said here isn't true. You are just repeating tropes that are fossil fuel industry FUD.
Also a global warming denier. I’d love to see him explain how this is wrong?

https://climate.nasa.gov/vital-signs/global-temperature/?int...
Oh wow, I had no idea, thanks.
The main advantage of 555 timer is that it is configured with a resistor/capacitor kit. No computer or programming required.

Microcontrollers obviously have more than 1 bit of memory + 2x analog comparators + one 33% / 66% voltage divider (which is all a 555 timer truly is).

What is surprising however is how flexible 1 bit of memory + 2x analog comparators + one 33% / 66% voltage divider
I already have if you don’t count HN.

You don’t need social media, and I think less of people who need the acceptance of others.

I quit all social media about 10 years ago, when I wasn’t yet 20. I don’t watch or read the news either.

People are sheep though, so they thought that odd. But I’m not a sheep. You soon learn the important relationships, and the pointless ones.

I have nothing but HN. I don’t even have a LinkedIn, I still have a good software job.

You don’t need any of it, it’s all just noise and self-felating, distractions.

I have a great quality of life, very close friends and proper relationships with people, and I spend my time outside or furthering my studies.

I don’t care what Stacy ate for breakfast yesterday, and I don’t care about John’s new car. I don’t care about Bobs new position, I don’t care about Jacks political prowess. I don’t care about the “edgy” meme that Kate posts.

You are what you consume. So if you consume banal, shitty content, non-genuine surface level relationships, and manipulative advertising, and put up a false digital grandiose mask of who you are- what does that make you?
Completely plausible: invest 17M EUR in dutch or belgian 6 month bonds
The past was allowed to play itself out. Why not the present too?
You fix this by letting Boeing fail. They keep going because our government keeps bailing them out. We deem them too important to fail so we keep holding their corpse up Weekend at Bernies style and hope the voodoo music doesn't cut out.

Fix the regulatory regime but also streamline it so other companies can begin to compete. We'll be without a domestic Airliner manufacturer for a bit but I don't think you fix this without eating that pain for a while.
One should be enough to wake a million people, with fan out.
Drew isn't well-respected, he's been far too antagonistic to far too many people over the years for that.

Latest news is that he authored/published a controversial character assassination on Richard Stallman while trying and failing to stay anonymous. Then some further digging after this unmasking found he's into pedophilic anime. Sitting on his computer uploading drawings of scantily-clad children to NSFW subreddits.

No-one with any decency can respect that behavior, it's disgusting.
Quantized random sampling regression
I would say the Ice trade was crazier.

And if your rulers are bloodthirsty heart burners and skin flayers, even satan will be received warmly. I mean Huitzilopochtli is giving Kali run for her money in the deities I don't to live under competition.

And east india - you replace the elite and the people underneath will continue following orders - the same happened with the Manchu conquering of china.
Indeed, specialist knowledge is a real constraint, but I think it’s possible to at least _orient_ towards building systems that require no baseline level of skill (the fast food model I guess) or towards training your staff so they acquire the necessary level of skills to work with a less accessible system. I suspect that the second pathway results in higher productivity and achievement in the long term.

However, management tends to align with reducing the baseline level of skill, presumably because it’s convenient for various business reasons to have everyone be a replaceable “resource”, and to have new people quickly become productive without requiring expensive training.

Ironically, this is one of the factors that drives ever faster job hopping, which reinforces the need for replaceable “resources”, and on it goes.
Pretty much everyone who prices out Gemini has the same question - these prices just seem WAY to cheap to be sustainable long term.

I've tried bouncing this off some Google employees and the general vibes I got back from them is that Google is very good at running stuff like this at a scale that drives down the cost for individual queries, so they seemed confident that these prices were not a loss leader strategy.

I don't know if I can believe that though. It's just SO cheap!
> QUIC is faster than prior versions of HTTP, but its still HTTP. It will never be fast enough because its still HTTP:
> * String headers
> * round trips
> * many sockets, there is additional overhead to socket creation, especially over TLS

QUIC is a transport. HTTP can run on top of QUIC, but the way you’re equating QUIC and HTTP doesn’t make sense.

String headers and socket opening have nothing to do with the performance issues being discussed.

String headers aren’t even a performance issue at all. The amount of processing done for when the most excessive use of string headers is completely trivial relative to all of the other processing that goes into sending 1,000,000,000 bits per second (Gigabit) over the internet, which is the order of magnitude target being discussed.

I don’t think you understand what QUIC is or even the prior art in HTTP/2 that precedes these discussions of QUIC and HTTP/3.
Waymo for sure, but I meant also without any geolock etc., so I can't claim credit for my prediction.

They may well best Tesla to this, though.
Huly was just recently on the HN frontpage:
https://github.com/hcengineering/platform

Gradio:
https://github.com/gradio-app/gradio
It seems that syscalls might be the culprit (ACKs occur completely inside the kernel for TCP, where anything UDP acks from userspace). I wonder if BGP could be extended for protocol development.
History is already written, this is the age of everyone recording and sharing things. There's no meaningful rewriting it.

They don't get to directly and intentionally kill and/or cause death, injury and illness to high hundreds of thousands of people very publicly and proudly, while writing "death to Arabs", "good Arab = dead Arab", "Nakba 2023", and other vile shit on the walls of their destroyed cities.

Easy to see this is not Israel+USA trying to eliminate Hamas, but some holy war to eliminate Palestinians as a whole, in the most underhanded way possible, as to not get blowback from the non-USA countries.

They'll destroy themselves, continuing doing this, provoking neighbors and inciting Palestinians for a massive revenge wave in the future. It doesn't matter when this happens, but Israel is done after this. They're not a superpower and USA backing under Trump, once he wins, will only serve to make their crimes more obvious, and self-destructive behavior more bold.
What is the difference between code that blocks waiting for I/O and code that performs a lengthy computation? To the runtime or scheduler, these are very different. But to the caller, maybe it does not matter why the code takes a long time to return, only that it does.

Async only solves one of these two cases.

I’d like to draw an analogy here to ⊥ “bottom” in Haskell. It’s used to represent a computation that does not return a value. Why doesn’t it return a value? Maybe because it throws an exception (and bubbles up the stack), or maybe because it’s in an infinite loop, or maybe it’s just in a very long computation that doesn’t terminate by the time the user gets frustrated and interrupts the program. From a certain perspective, sometimes you don’t care why ⊥ doesn’t return, you just care that it doesn’t return.

Same is often true for blocking calls. You often don’t care whether a call is slow because of I/O or whether it is slow because of a long-running computation. Often, you just care whether it is slow or how slow it is.

(And obviously, sometimes you do care about the difference. I just think that the “blocking code is a leaky abstraction” is irreparably faulty, as an argument.)
I had this problem with pi 4 after frying several SD cards I found out you can setup read only file system and since then no problems for 3 years now. https://core-electronics.com.au/guides/read-only-raspberry-p...
Cold messaging on Facebook + word-of-mouth growth. We found people in one large Facebook group.

To get 1,000, we used SEO.

Our product helps people get ready for the Duolingo English Test, so our target audience was well-defined from the beginning.
Hell yeah man! Join the club
Asynchronous code is the bees knees

Async/await is a horrible fit for Rust.

> Some of this criticism is valid. async code is a little hard to wrap your head around, but that’s true with many other concepts in Rust, like the borrow checker and the weekly blood sacrifices. Many popular async libraries are explicitly tied to heavyweight crates like tokio and futures, which aren’t good picks for many types of programs. There are also a lot of language features that need to be released for async to be used without an annoying amount of Boxing dynamic objects.

Yes. So don't do it

It is entirely possible to write asynchronous code without using asyc/await.

async/await is a fun paradigm for garbage collected systems. It is a horrible mess in Rust
Yes but it would still feel weird for me to thank my employer for that.
Meanwhile here in New Zealand we can get 10 Gbps FTTH already.

Sorry about your NBN!
That is a fair point. I wrote my own implementation of WebSockets in JavaScript and learned much in doing so, but it took tremendous trial and effort to get right. Nonetheless, the result was well worth the effort. I have a means to communicate to the browser and between servers that is real time with freedom to extend and modify it at my choosing. It is unbelievably more responsive than reliance upon HTTP in any of its forms. Imagine being able to execute hundreds of end-to-end test automation scenarios in the browser in 10 seconds. I can do that, but I couldn't with HTTP.
Before you say things this patiently dumb you should probably wonder what question the researchers are actually interested in and why your average experience isn't sufficient proof.
Honestly the entire comment is a head scratcher, from comparing QUIC to HTTP (different layers of the stack) or suggesting that string headers are a performance bottleneck.

Websockets are useful in some cases where you need to upgrade an HTTP connection to something more. Some people learn about websockets and then try to apply them to everything, everywhere. This seems to be one of those cases.
My experience with Bluesky has been similar to my experience with other "disruptive" platforms like Cara (the anti-AI art portfolio app/site).

When a "new" (usually overall non-corporate) internet space opens up that, in theory, caters to a broader audience, the most immediate colonizers are the type of people that have some sort of "underground" bent to them - subcultural things like furries, erotic artists, etc.

Opening up Cara produces an avalanche of large-breasted foxpeople, and the last time I opened Bluesky I was met with a photo of what appeared to be a boy in his underwear. Mastodon has its dubious reputation also for child pornography.

I'm just saying, the mainstream internet is moderated for a reason. Being mainstream, there's money behind it, and with money comes power - this results in moderation that is usually politically motivated, and so in recent years there has been an exodus of the masses to low-moderation platforms like Tiktok, or things like Kick for younger users.

When a platform or site is staffed small, such that it cannot afford to moderate, it will be suffocated by the "undesirable" groups I mentioned, earlier, as though they were some sort of choking algae. There are so many of these people "empowered" these days that, from what I have seen, it is really hard to start new social media sites without corporate resources. Twitter is already plagued with OnlyFans bots due to being smaller now, and streaming platforms are forced to aggressively build themselves to be resilient against similar sexual content creators, who are the first people that show up. Most times these creators will be working for an organization.

In the end...could Twitter have existed in a non-sh*tty form in the first place? It was rapidly approaching bankruptcy when Musk was (in the end) forced to purchase it (lol). If not him, someone else would have acquired it, probably a corporation, and monetized the content to keep it afloat.

I think in the end, the landscape is going to look more like Tiktok (computerized moderation) for anything beyond Meta. Smaller social media platforms will be seedy and not widely populated. Forums will continue to be used by countries with their own internet ecosystems, like Korea or Nigeria or Finland, but not really exist in global lingua franca English beyond a handful of major ones like SomethingAwful.
> my point is the article doesn't make it clear what kind of oil we're talking about,

The article clearly explains that it is oil form the bone marrow of the animal. Quoting the relevant part:

"Rocha explained that KOBO’s bone marrow is actually 'full of oil,' even though the whale has been dead for more than two decades.

'It’s seeping out through the pores of the bones,' Rocha said. 'The outer edges of the bone are a little more porous than human bones and [gravity is] just pulling the oil out.'"
In Soviet Russia, monitor monitors YOU.

Bwah hah hah!
It seems like the magic for the author is in the annotation. There's still two kinds of functions "fearlessly run in the UI thread" and "must be run in a worker" and async is great in that it greatly expands the number of functions
in that first pool but it's effectively the same thing as the [blocking] annotation but the other way and not totally complete. Because there are async-safe but not async functions.

So to me it seems like it all leaks because in all cases what's desired is some external signal about how the function behaves. A "badly written" async function can stall the loop and that isn't conveyed only by the async tag. It's rare to do this but you can and there might even be times where this makes sense[1]. But it happens that by convention async and ui-thread-safe line up but there's a secret other axis that async is getting mixed up in.

[1] Say running a separate event loop in a background thread used for CPU intensive tasks that occasionally perform IO and you want to make the most use of your thread's time slice.
And such coders should carry malpractice insurance.
Async is worse than leaky it often goes viral because many other parts need to be async to call it.