skysight-inc/HackerNews huggingface dataset:
I work in ERP space, which is the ultimate uncool from typical HN perspective; but sometimes "uncool" has a Venn diagram overlap with "mature".

A modern top tier RDBMS is an incredibly powerful, fast, mature, stable tool - when wielded wisely by the knowledgeable wizard. To be fair, the developers must have a solid understanding of programming language, and business domain, and SQL / data dictionary / ERD - which I've always taken for granted but eventually realized is not the norm.
Ask HN: Need ideas for a programming language name
I need some ideas for a programming language name. I originally came up with "Rylang" for my language, but it turns out there is a language with a similar name "Rye" already.

So far my best idea is "Magnesium" but it doesn't roll off the tounge very well.

Anyone want to volunteer a suggestion?

It is a low level (C/C++-like) systems programming language.
Copy and patch is a variant of QEMU's original "dyngen" backend by Fabrice Bellard[1][2], with more help from the compiler to avoid the maintainability issues that ultimately led QEMU to use a custom code generator.

[1] https://www.usenix.org/legacy/event/usenix05/tech/freenix/fu...

[2] https://review.gerrithub.io/plugins/gitiles/spdk/qemu/+/5a24...
I'll preface this by saying I'm for sure not denying there's problems to be fixed with this plane. There for sure are. But man, people in threads like these seem so out of touch with reality. You know that you have an incomplete picture of reality right?

You're on US-based websites and consume US-based media, both of which amplify every bad thing related to Boeing, but don't amplify the same types of issues for other manufacturers. When Airbus planes fall apart and crash and have problems those events almost never get upvoted to the top of Hacker News, and you don't see those events covered nearly as often in the media. All you are exposed to is Boeing bad news, and not bad news from other manufacturers and you have a pretty skewed perception of reality.

It's still lottery ticket odds to be involved in a crash with one of these planes. You likely risk your life more every time you get in a car than getting in one of these planes.
I understand where you're coming from, but there's a fine distinction. Most never wind up testing their safety net. In my mind, the real benefit is the risk tolerance you develop knowing you have one as a young adult.

When you don't that drive for safety can leave one with a very risk adverse mindset. So yeah, you can be FI at 40, but that won't magically change the temperament that got you there.
Even "safe" drivers who aren't speeding, driving recklessly, or consuming alcohol are at greater risk of death and injury than on any major U.S. air carrier.

So you do have control, and can put yourself into a safer cohort of drivers, but the best you can do still falls wildly short of the state of aviation safety.
Every time I tried to use event sourcing I have regretted it, outside of some narrow and focused use cases.

In theory ES is brilliant and offers a lot of great functionality like replaying history to find bugs, going back to any arbitrary point in history, being able to restore just from the event log, diverse and use case tailored projections, scalability, ...

In practice it increases the complexity to the point were it's a pointless chore.

Problems:

* the need for events, aggregates and projections increases the boilerplate tremendously. You end up with lots of types and related code representing the same thing. Adding a single field can lead to a 200+ LOC diff

* a simple thing like having a unique index becomes a complex architectural decision and problem ... do you have an in-memory aggregate? That doesn't scale. Do you use a projection with an external database? well, how do you keep that change ACID? etc

* you need to keep support for old event versions forever, and either need code to cast older event versions into newer ones, or have a event log rewrite flow that removes old events before you can remove them from code

* if you have bugs in you can end up needing fixup events / event types that only exist to clean up , and as above, you have to keep that around for a long time

* similarly, bugs in projection code can mess up the target databases and require cumbersome cleanup / rebuilding the whole projection

* regulation like GDPR requires deleting user data, but often you can't / don't want to just delete everything, so you need an anonimizing rewrite flow. it can also become quite hard to figure out where the data actually is

* the majority of use cases will make little to no use of the actual benefits

A lot of the above could be fixed with proper tooling. A powerful ES database that handles event schemas, schema migrations, projections, indexes, etc, maybe with a declarative system that also allows providing custom code where necessary.

I'll take a look at Rama I guess.
A bigger source of effective (at driving division and getting Your Side riled up) slant isn't when the same story is covered differently, but when an outlet or set of related outlets cover a "story" that evaporates entirely if you fill in basic, deliberately-omitted context. There's not another side to cover, because it's not even a story.

Example: I see "[Administration] transporting migrants from the border to cities around the country, in secretive nighttime flights" receiving heavy coverage on a certain news channel (you can probably fill in the gaps here, but I'll leave the specifics out because that's not important for the illustration). Like, it's most of what they're talking about, for the entire hour or so I happen to be in a room with them on the TV, and not during an opinion segment.

Quick google:

1) Not secret,

2) Some are at night, but that's just because of, like... flight scheduling, same way some commercial flights are after sundown and others aren't, plenty are during the day, and it's not as if nighttime flights are somehow significantly harder to track than daytime ones or like it's weird for passenger planes to fly at night, so that whole bit was silly to begin with, worst evil plan ever if that was a deliberate part of it (as was implied), and

3) It's part of longstanding, ordinary operation of immigration control, isn't a new thing, and is happening for non-crazy (and certainly not secret) reasons—though one could disagree with them and say something else should be done instead, sure, but that's not how it's being covered, it's being covered as (implicitly) a new program (not new) being carried out for mysterious reasons (not mysterious) in secret (not secret).

Is this "story" receiving similar heavy coverage with a different slant on perceived-as-opposing channels? No, the info on it's mostly to be found on simple factual sites that published info on these activities from before it was "a story", and sites dedicated to debunking "fwd: fwd: fwd:" crap, because it's, emphatically, not even news, so how would an ordinary news program cover it? It's simply absent.

The less-brazen version of this is to not cover or downplay something that is news but that you'd rather bury but this stuff is... on another level. The "other side" can't provide a different slant, or uncover a story you're hiding, because it's not even a story. (the evolved version of this tactic, of course, is that your opinion-focused programs accuse the "other side" of burying the story and use it as Yet More Evidence that they can't be trusted, which story they can't even responsibly cover because it's made-up, unless their story is to report that you're inventing news) Bonus points that this gives you stuff to talk about if you're the ones trying to avoid a real story that's inconvenient. It's brilliant, really.
Car and light truck tires are apparently only about 19% rubber.[1] More than half of a tire's composition is synthetic polymers, fillers, and textiles (e.g. polyester, rayon, nylon).

[1] https://www.ustires.org/whats-tire-0

Tires generate more particles of pollution than exhaust.[2] EVs are good. But eliminating car exhaust apparently isn't the big car pollution problem.

[2] https://www.theguardian.com/environment/2022/jun/03/car-tyre...
We've released many examples.

The first is our Twitter-scale Mastodon implementation, which is 100x less code than Twitter wrote to build the equivalent at scale (just the consumer product). It's also more than 40% less code than Mastodon's official implementation (which isn't scalable). https://github.com/redplanetlabs/twitter-scale-mastodon

The rama-demo-gallery repo also contains many short, self-contained, thoroughly commented examples of applying Rama towards very different use cases. These include user profile management, time-series analytics, atomic and fault-tolerant bank transfers, and more. https://github.com/redplanetlabs/rama-demo-gallery
I use 2x 3090, no nvlink though. I’d read it doesn’t help that much but not well read on any improvement.
The View Transitions API and Delightful UI Animations
Instantly thought this had a teenage engineering vibe and was pleasantly surprised that it's actually a collab with them. Makes me 10x more likely to buy.
Look for "equipment type" when booking flights, and on your boarding pass
You are confusing absolute free speech and free speech.

Musk asserts that he subscribes to absolute free speech, but continuously shows that he most definitely does not, usually through being a thin skinned snowflake.
This isn't in the US.
My work Teams channel
Beware that if you attempt to use an SDXC card that a lot of the really cheap made in China CF to SD adapters do not support capacities above 32GB (SDHC). I'm not affiliated with the site, but from experience modding iPods I can recommend the iFlash CF to SD adapter as one I would trust [0].

[0] https://www.iflash.xyz/store/sdcf-adapter/
A more efficient and intuitive way for me to browse Hacker News - awesome!

Glad to see privacy is addressed (to some degree) up front.

What about Right to Repair? It would be nice to swap the Rabbit R1's smooth-surfaced analog scroll wheel with a knurled metal one.
Laws are imo somewhere between code and natural language, and imo closer to the code end of the spectrum.

If you go full “natural language” approach that’s open to whatever interpretation, that’s how you get kingdoms and dictatorships. Everything seems cool and all with the “natural language” approach to a legal system, up until the point the person in power decides to arbitrarily use it against the interests of the people they are governing.

This is pretty much why laws in countries with at least somewhat functional legal systems tend to be treated more like pieces of code rather than whatever someone thinks things should vaguely and generally.

The culture of “rules lawyering” is imo the best we can do if we want the legal system to treat everyone equally and impartially. Do you think that all the people involved in legal systems over thousands of years were just not enlightened enough to ever consider “why do we have all those ultra specific and codified laws, let’s just issue a list of general things like ‘don’t harm other people’ and ‘respect property of other people’ that would cover pretty much any undesirable behavior, and then call it a day?”.

If anything, legal systems became more “rules lawyered” and more similar to code over time, precisely because the world has been moving in the direction of more fairness and equality. I mean, not that long ago at all, we had some of the most advanced nation-states being ruled by a single king/queen/emperor/etc. And their word was not only a de-facto “absolute definition of the law”, but also de-jure (as opposed to some contemporary modern nation-states, like DRPK or Russia, that where laws technically exist on paper, but de-facto their codified definition doesn’t matter much at all,).
Neat idea, worth a try. Privacy story will be interesting.
You consider it a good thing that the CEO has to get involved in mundane things like this? I would consider a failing. Ideally the CEO would fix the system, not just resolve it for the few powerful enough to get his attention.
This is a lie, and you know it. Even a mere idea about lawyers being managed by a non-lawyer would be laughed at. Same with finance, nobody would be stupid enough to even try it
https://www.youtube.com/watch?v=a2h-Hl3lewg
Population Density Explorer
Out of curiosity, why did they think 50kW was a necessary amount of energy to heat? Is the building old and poorly insulated? An A/A+ energy class 150m² home barely needs 1/10th that amount.

If it was indeed a question of insulation or airtightness, then perhaps spending a part of that money for renovations in that area and only then a fraction of the price for a reasonably-sized heating unit might be sensible. You could also do just the renovations and thus reduce your wood pellet usage substantially as well – already a big win for the environment.
A New Future for Icanhazip (2021)
The bottom line is that I think it is absolutely silly for people to try to make their own judgement about the safety of aircraft they get on based on news stories about different variants of models which have had issues that are already identified.

This is a relevant topic for regulators to address, with specificity to the actual offending parts, procedures, and processes in place. Avoiding all MAX variants is a very hamfisted attempt to address a very tiny difference in observed safety.

There are regional airlines flying much more sketchy things. Where's "isMyPlaneACessna208BeingFlownByANewPilotInPoorWeather.com"?
Muxtape was the best and I still miss it. It would be wonderful to be able to make mixtapes for friends and just share them without needing to be on Spotify or some other walled off service.
The funny thing is IDA added an x64 decompiler for the free version right after the post. The piracy could have been avoided if it wasn't for the timing.
Not that I'm aware off. It's hard to judge because I didn't check a lot of times during the night. What I know though, is that the fan was not blowing up, but sideways into our direction.
I'm happy to live in a country with good tap water. But I'm afraid by this time all of the water is already infested with plastic, including ground, river and rain water.
I wish I could upvote this more. 95+% of startups will never need to scale past one reasonably sized single-instance database. Maybe they'll want to have a couple of replicas running for a fast failover, but from a performance perspective, they should spend their time writing efficient queries instead of horizontally scaling.

It's good to think about the what-ifs along the way. Can we shard this setup if we land a huge customer, or one that's hyper-sensitive about having their data separated? If/when that time comes, you'll have ideas of what to do about it. But realistically, most companies never hit that point. Every hour spent worrying how to make their product FAANG-scale is an hour spent not making their product.
Dead platform continues to flail, news at 11.
Our Mitsubishi Hyper Heat heat pumps put out noticeably warm air, definitely warmer than 30C.
Note that this is a Teenage Engineering collab! Pretty exciting and a crazy low price point for something with their name on it.

This isn't a phone though right? The title seems wrong.
Indeed, here's the reference manual for kx systems k 2.0[1]

One thing you'll notice is that most of the operations are given names, because trying to communicate about @[d; i; f ;y] doesn't really work, while "Amend Item" does. I'd equally need some very compelling evidence that @[d; i; f; y] is inherently superior to d.amend_item(i,f,y) - or more likely if we were to translate this into a syntax more acceptable to others it'd be more likely to be something like d[i] = f y (but I haven't bothered to figure out exactly the semantics of amend item; I just picked an item from the manual) - to anyone but diehard APL/J/K fans.

Most of it can be decomposed and expanded fairly straightforwardly. E.g. after lengthy back and forth a few days back it turns out ",/+|(8#2)\textb" that someone offered up translates into a more familiar OO-syntax roughly to:

textb.encode(8.reshape(2)).reverse.transpose.concat

... where the two most unfamiliar parts to most of us would be 1) a standard library where operations that we usually expect to be on an array are usually on each item. So e.g. "reverse" is here not "reverse the array", but "reverse each item in the array", same for the rest. The other two which doesn't have "reasonable" definitions is "reshape", which in this case (two int arguments) just creates an array of 8 elements of the value 2, and "encode" which repeatedly takes a modulo from one array, applies it to each element in the other array, passes the quotient forwards and repeats until the "modulo array" has been processed (putting (8#2), which translates to [2,2,2,2,2,2,2] then basically decomposes bytes into their constituent bits, but you can also do e.g. (24 60 60)\somenumberofseconds to "encode" a number of seconds into hours, minutes and seconds, which might give a better idea of how it works)

I'd read the "decoded" version over the terse one any day. I think a "midpoint" that introduced some of these operators in a more "regular" language might well be able to remain readable, but too much density and I can't scan code and get a rough idea of what it does anymore, and that to be is a hard no.

Because while some aspects of thinking in terms of arrays this way is also very foreign, the syntax is frankly more than half the battle.

[1] https://www.nsl.com/k/k2/k295/kreflite.pdf

EDIT: Here are some of my notes from trying to figure the above out, and some horrific abuse of Ruby to modify some of the core classes to make something similar-ish to the above actually work:

https://gist.github.com/vidarh/3cd1e200458758f3d58c88add0581...
I feel like we in the software industry should do more reflection on what happened here. Yes, many of the most evil acts were the result of social non-technical problems like terrible management, stupid legacy UK laws allowing PO prosecutions, and so on.

But the root cause was bugs. So many bugs.

There isn't much the average HN poster can do about the political and justice problems, which are firmly in the realm of the British government. But there are people here who work on databases and app frameworks. What can be learned from the Horizon scandal? Unfortunately there doesn't seem to be much discussion of this. Compare vs the airline industry where failures are aggressively root caused.

I'll start:

1. Transaction anomalies can end lives. Should popular RDBMS engines really default to non-serializability by default (non repeatable reads, for example).

2. Offline is very hard. A lot of bugs happened due to trying to make Horizon v1 work with flaky or very slow connections, and losing transactional consistency as a result. The SOTA here has barely advanced since the 90s, instead the industry has just given up on this and now accepts that every so often there'll be massive outages that cause parts of the economy to just shut down for a few hours when the SPOF fails. Should there be more focus on how to handle flaky connectivity in mission-critical apps safely?

3. What's the right way to ensure rock-solid accountability around critical databases, given that bugs are inevitable and data corruption must sometimes be manually fixed? A lot of the Horizon problems seemed to involve Fujitsu manually logging in to post offices and "fixing" the results of bugs, in such a way that they didn't realize their fix created ledger imbalances that the SPMs would be blamed for. A part of why big enterprises got so excited about blockchains was this notion of an immutable ledger in which business records can't go magically changing around you without anyone knowing how. There are clearly ways to do this, but they're not the default.

4. IIRC at least some failures were traced back to broken touch screens generating false random touches, which could lead at night to random transactions being entered and confirmed when nobody was around. Are modern capacitative touch screens immune to this failure mode? If not, are consoles in embedded applications always reliably engaging screen locks?

I guess there are bazillions more you could come up with.
>What upper bounds?
Well we know it isn't acutely toxic because people aren't just dropping dead inexplicably. And we know it isn't drastically raising cancer rates because, again those haven't inexplicably shot up.
Ian Hislop (the editor) is apparently the most sued man in history! (I may be exagerating).

Seriously though, they are roped around with super injunctions and actions of every type intended to bring them down. I agree that they seem to be in rude health now (mostly because of my subscription I am sure) but it's really possible that some bastard will get them.

After all - they got Twitter...
A hyperbole about restricting free speech on a platform owned by a "free speech absolutist" will never get old.
log(2)÷log(1.1) ~= 7.27, so in principle sustained 10% improvements could double performance every 7 releases. But at some point we're bound to face diminishing returns.
They're pointing out Musk's hypocrisy after repeatedly claiming himself to be a "free speech absolutionist". If someone hurts his feelings or calls out his BS he bans or blocks them. Very thin skinned and sensitive, desperate for attention and likes. I'm not even on Twitter and I've heard of this.
I think it's OK to want your children to be healthy even if world falls apart
By what measure was England the first liberal democratic country? There are earlier republics than England and earlier countries with election process than England?
It’s still fairly common for the majority of critical data to be in a single database. Even if microservice initiatives have moved some data out.
I back up my Minecraft server with GIT, and use tags to track when I updated the version.
The final page of the company returns for ICL in 1996 (thanks to Wikipedia) notes that the ultimate controller of the company was indeed Fujitsu at that time. The rebrand happened in 2002, but it is correct to say that the system was developed by a part of Fujitsu.

https://find-and-update.company-information.service.gov.uk/c...
We have lots of replacements for plastic, what we used before plastic: Metal lunch boxes, metal cups, metal piping, etc
I am almost never a hater on people trying ambitious things, but man this is one of the most "doomed to fail" things I've ever seen.

You've got absolutely insane market saturation by two major players that have some of the most advanced AI teams on the planet.

Almost nobody is going to buy an "LLM-first phone," they will just wait for Apple or Google to put an LLM into their existing phone.
> It is too difficult and dangerous to run a website without extremely deep[0] technical knowledge

Counter point possibly. Squarespace and its lookalikes... Old school "php webhosters" generally now have "site builders" that are reasonably decent, hell I can buy a wordpress site pre setup with a theme that is automatically kept up to date for next to nothing, around what I would pay for a filter coffe every month.

For a blog do you really need more?

Being a knowledgeable developer I can spin up 10 such sites using nginx + some html and CSS and spend about 10 minutes every now and then running updates and rebooting for about the same price but for the average user generating your own content has literally become "click these 5 buttons and begin writing"
> The Mongol Hordes: They’re Just Like Us

Is that rehabilitating their image? Is your assumption that modern humans are inherently better? World War II was caused by (what I would argue are) modern humans. I believe we could see wars of similar horror in the future.