explodes

Some things on Earth (especially in the ocean) you'd think were extraterrestrial... What a gift to still be able to find such amazing animals out there.

Using a platform-specific tool feels like vendor lock-in. Given the recent trends, behavior, and activity of GitHub, it sure seems like this is the opposite of what the world should be going for generally.

Also if someone could help me understand: Are these so-called stacked commits not possible with multiple commits on a single branch? I prefer to write my commits as atomic, independent, related changes, on a single branch, with both Git and Mercurial. I am apparently missing something: why can't a better UI simply show a multi-change PR?

> Be kind. Don't be snarky. Converse curiously; don't cross-examine. Edit out swipes.

https://news.ycombinator.com/newsguidelines.html

Reading other comments, I noticed that this was a legitimate question.

There is a difference between "correct" and "how it is actually used by real people."

IANAL but my understanding with settlements is that It removes the possibility of the defendant risking a judgement of wrongdoing and causing more problems down the road, like having to fix their mistakes.

In all for these maps, unfortunately this is a "Show HN: paid only products", not open source maps, free maps, or anything fun like that. At least I couldn't find the actual maps that are mentioned in the title.

> starting next year

I'm guessing contracts for the existing sludge need to expire first before they improve their product.

If the webmaster notices this, the squares aren't great on mobile.

Huge miss. Again. And again. And again.

Dendrite Crack is a really cool name for something... Not sure what...

> In fact, a reliable engineer ought to be comfortable working on products people hate, because engineers work for the company, not for users.

I prefer to take pride in my work. This sounds like hiding ones neck to collect a paycheck.

I prefer to have hard discussions about pivoting or making changes so that we can improve the product, or company, for our users. Anything less is simply "not doing the job", or at least making a serious consession, in my opinion.

That part bugged me too!!! Like, why! There are two places at least, guh.

We all knew Microsoft was going to destroy GitHub eventually when it was first bought.

How much longer do you want to tolerate the enshittification? How much longer CAN you tolerate it?

When your code uses inversion of control, which can allow your code to inject different versions of your dependencies, such as a mocked disk API, or network resource, the code is often more testable because of the separation of concerns, and thoughtful design.

I would answer your question by stating your alternative _might_ be an easier test to write now, but amortizing the (already low) cost of having a code written with first practices in mind will be much easier to work with in the long run. Including across small and large teams. Ultimately we want our code to be reliable and scalable, and we can do that by making our code testable and maintainable.

Let's not pretend there isn't a huge difference between automated privacy invasion and manual.

This was a great read, even without having been working with Go for some time. It was well written, the examples demonstrated nearly everything, and being able to edit samples to test everything else, all on my phone, is quite delightful. Cheers to the author

People should always consider the "abusive friend" scenario with regards to privacy.

Even marriages can be extremely abusive...

The assumption that people on your friend's lists, Steam or anywhere (even just people in the same household) should be able to see your personal information, such as computer use, is a bananas assumption. It is an assumption that I'm pleased to say has failed privacy reviews at at least one company larger than Steam.

Point 1 may be a problem if you're embedded. Otherwise, enjoy the fact that the 150,000 lines of c-code are some of the most tested lines of code on the planet.

Point 2 doesn't tackle the reasons why there is a mismatch between in-memory representation and tabular data. Some benefits include the wins obtained from a schema built to utilize "normal form". Object databases have their place, but so do fully normalized database tables.

Point 3 doesn't strike me as useful. I don't find myself reverting rows to previous points in history that often, if I ever have. Tracking versions of rows is useful. I would argue that "reverting" is not, since the reverting would be better tracked by adding a new version as a forward update.

Overall, sure, a new, "light weight", object database that uses data structures* may have a place somewhere. But to replace SQLite? I think not.

*The Java API gives me the same recoil as Java JSON API. Pulling out data key by key feels like pulling teeth tooth by tooth.

Awesome! I've always wanted to try this game so this is a good breezy intro.

Who all have you seen crying? Nobody really? Oh ok.

Indeed. I challenge all bored-enough readers to an exercise: compare your doomscroll to your friend's doomscroll. It's wild how much they can differ.

Were these cannibalized companies working on an implementation that is not a terrible idea? I'd go as far as saying that it was a decent enough idea that we can applaud the efforts while also rooting for the 'underdogs'.

The point of saying this is to let you realize that the last ten years weren't a disaster.

Whatever the pasta is now, it cooks quite differently. You'll get softer noodles much quicker, and will congeal into a blob unlike the old recipe. Additionally the water gets extra starchy with the new recipe. I haven't seen it mentioned anywhere else but the quantity per box has decreased as well. Special shapes came in smaller weights, but now even the regular box does too.

For other mobile users:

https://www.cvefind.com/en/cve/CVE-2025-20700.html

https://www.cvefind.com/en/cve/CVE-2025-20701.html

https://www.cvefind.com/en/cve/CVE-2025-20702.html

There is config you can add to your ~/.claude/settings.json file for this. (I'm on mobile!)

So we could be run over by a black hole at any time, too? How wild is that!

There are certainly very real humans deciding if this target gets hit or not and why.

God I love Hacker News.

Link should be https://www.sciencedirect.com/science/article/pii/S027323009...