I find this the case, but I've also found anomalies where I one day watch a movie that's been in my watchlist for years. One day something that seems stale just seems new again. Not sure why.

That's also true but if I haven't felt compelled to upgrade it from a notebook scribble it's somewhat less likely

It also consistently insists, breaks functionality and nags you to try and get you to use the app instead of the browser. Its barely useable from a mobile browser.

They can steal a lot more data from you using the app, that's why they insist on you installing it.

I avoid native mobile apps for anything but the most essential for this reason. If it wasn't for the cars and public transportation I'd be using a feature phone by now.

I refuse to download the app out of principle. I just manually go into the URL bar and add "old." to get the classic experience.

How long would the currently 17 people in space survive if every human on planet earth was eradicated?

Dunno. I imagine they’d follow soon, though.

No issues here. I write a ton of Rust every day with GPT and it just keeps getting better.

At least with Go you can use "Golang" in search and get reasonable results. With Rust, I often have to write "rust programming language + [what im searching for]" which is really annoying. Not sure if anyone ever dubs Rust to "Rustlang".

The website is literally rust-lang.org.

fair point

Its actually not. The most recent drama was caused by the Rust Project, not the Rust Foundation, which are two completely separate entities. This seems to be a common misunderstanding which is being spread around here, including the top comment to this post.

It is. This is not caused by the most recent drama but by the Rust trademark shitshow, which was definitely by the Rust Foundation.

You’re right. I mistakenly thought this was a response to the latest drama show.

People often use technology without thinking about or knowing exactly how it works.

Might be worth reading the response from the other side: https://www.reddit.com/r/rust/comments/13tsmht/comment/jlxmc...

The same person also posted essentially the same message under the linked post.

FWIW it sounds genuine to me.

Can you link me to that please?

Probably this one: https://hachyderm.io/@sgrif/110447363438183593

It’s a joke. Nobody would fork an entire programming language and maintain it because they thought someone was wrong on The Internet.

Projects have forked over leadership issues plenty of times before; there have been cases where both parts of the fork stuck around (NetBSD/FreeBSD), and at least a couple where the projects' former leadership effectively gave up and handed the reins to the fork (egcs, a gcc fork which became the official gcc in 1999, after the FSF belatedly realized that their official version was getting stagnant, and X.org, which displaced XFree86 without a rename after users of the latter all abandoned it).

> NetBSD/FreeBSD

Bit of a nitpick, but I think you meant NetBSD/OpenBSD? AFAIK both FreeBSD and NetBSD independently continued the abandoned 386BSD project, but there was never any strong relation between the two projects (they did share code later on). OpenBSD did split from NetBSD, after Theo de Raadt was removed.

Other examples: FreeBSD/DragonFlyBSD, Vim/NeoVim, Mplayer/mpv, (Open)Solaris/illumos, MySQL/MariaDB, probably some more.

Also openoffice/libreoffice, bitcoin cash from bitcoin, etc.

You sure about that?

https://stackoverflow.com/questions/27309412/what-is-the-dif...

It's also happened with operating systems: https://en.wikipedia.org/wiki/DragonFly_BSD

> Dillon started DragonFly in the belief that the techniques adopted for threading and symmetric multiprocessing in FreeBSD 5 would lead to poor performance and maintenance problems. He sought to correct these anticipated problems within the FreeBSD project. Due to conflicts with other FreeBSD developers over the implementation of his ideas, his ability to directly change the codebase was eventually revoked.

I stand corrected.

But, a few months later io.js merged back with node. So, “it worked,” but was a giant mess.

There's also libav which forked from ffmpeg and lasted for 7 years. And Gitea which forked from Gogs and it's still going.

There are loads of forks that happen due to disagreements in organisation.

People have forked terminal emulators, desktop environments, and operating systems; so forking a programming language isn't that inconceivable. (-:

> forking a programming language isn't that inconceivable.

Do SQL dialects in Databases count? mariadb

If I remember it right, the word "fork" was created to describe the GCC thing.

The wikipedia article https://en.m.wikipedia.org/wiki/Fork_(software_development) has a link to a usenet post from 1995 that uses 'fork' to describe XEmacs; so that predates the gcc/egcs split by a couple of years.

What if that "wrong person" had undue influence on the project?

Python 2. Don’t make me print(“”) when I can print “”

XEmacs

Is there a specific reason that projects like these seemingly often are Chrome only. I use Firefox and I feel «left out» on a near weekly basis.

Well, speaking for myself, it's just the browser I use, I don't necessarily love it but it the standard browser with the least headache.

As for the extension, it doesn't depend on anything other than hackernews and the search api, so a port should be easy.

Update: It's now available as a userscript, tested on Firefox with Tampermonkey

As a Web Extension dev, I can say that Chrome is definitely the go-to platform for developing new extensions, as you basically target most of the market this way (incl. Chrome, Edge, Brave, etc.). Any additional browser, means ofc additional dev time and testing, some of which can be really funky, like Safari.

That said, from the two (the other one being Safari), Firefox is much easier to port the extension to and there's even webextension-polyfill that gets you >95% of the way there (most of the time).

> That said, from the two (the other one being Safari), Firefox is much easier to port the extension to…

Is it? Has anyone in this thread tried this? (I have not.) https://developer.apple.com/documentation/safariservices/saf...

Yeah, I have done it twice now. Safari doesn't have as good of a support as Firefox for a lot of Web Extension API, and that's on top of various compatibility issues with Safari itself. Not to mention having to deal with Xcode to just bundle the extension into Mac app-like wrapper.

To be more precise the last time I did this I had to: - Adjust cookie SameSite attribute (cookies didn't work properly otherwise) - Migrate back from MV3 to MV2 (Safari DevTools are really bad for MV3 for some reason and there were also other issues that didn't appear in MV2) - Adjust JS and CSS (some newer techniques were simply not supported in Safari)

Firefox didn't have any of those issues. On top of that, there's much more resources available online than there is for Safari - though, to be fair, it's mostly because its support for WebExtensions is newer and there aren't as many extensions for Safari. But, when you do find some resources you have to verify whether they're actually on the most recent standard - Web Extensions - since Safari supported multiple over the years, that have nothing to do with WE, and are very similarly named: Safari Extensions, Safari App Extensions, Safari Web Extensions

Safari also has random weird (read: highly annoying) things where it purports to support a given component of the WebExtensions API, and then totally doesn't. Storage.sync is a perfect example—why I should have to build my own syncing infrastructure purely to support safari (particularly given that apple always talks about wanting to protect user data)?

https://developer.apple.com/documentation/safariservices/saf...

FF is my primary browser too, but with the user base down to 3%, it's not exactly relevant any more.

"3 of 100 people" - I'm one of those three.

I would be willing to bet that the 3% stat doesn't hold true for HN users

Oh … my naive ass thought it was like 50/50 between Chrome and Fx :(

There's a script available now - just installed it in FF with Greasemonkey.

How hard is it to create a cross-browser plug-in?

Trivial

it's <200 js code lines just port it.

Yes, so one could either make the argument of why don’t projects like this «just» do that? Or the other way around.