This is great news! Weird that I’m subscribed on all of the earlier Firefox GitHub discussions and didn’t notice it. I wonder which version was the first to have Firefox support feature in it.

Oh wow, I didn’t know that! Is there any official statement? Search didn’t turn up anything. I guess I don’t necessarily need to know exactly how it went down, but I wanna be nosy. :D

You shouldn’t wait because it’s going to happen. I moved all of my projects off of Github and Gitlab, and now self-hosting my own gitea instance. It’s been great and never looked back!

We’re all always dissatisfied with something

I don’t think this is an anti-React post, like the other commenters are implying.

This issue would occur when attempting to search any webpage with the web browser’s builtin search feature before the content has a chance to load in. This happens if the page requires JavaScript to load, which is the case with React apps.

deleted by creator

Not many things require a polyfill these days. My guess is a lot of older sites are affected.

Yeah, depending on the branch I’ve found that method not to be too reliable. openrss offers branches for RSS feeds for commits on every branch though: e.g. https://openrss.org/github.com/octokit/octokit.rb/commits/main

Yeah, because anything that isn’t a big new JavaScript framework is just way too complicated

Yeah git reset --soft then the sha of the last commit you want included in reset.

Mine are pretty sassy

This is helpful. Thanks. Didnt even realize it. No need to use something to point out how its not a good look. It’s still good to bring more awareness around how sites like Github are becoming a more of walled gardens. I agree with everything else you said though.

Thought it was the best way to meet hot guys

No its for grandmas who want to be sexy but hate wearing high heels

Express, JavaScript (with JSDocs+TS for type-checking) and Postgres

Looks like a decent setup. Vanilla JS is the way to go for the best performance. Avoids vendor lock-in and those skills never go out of date. 👍

And also try to make tests that don’t have to change if you refactor in future (although there are some exceptions)

Yeah they’d have to maintain upgrades security patches etc and could get pricey depending on how much storage and bandwidth is involved.

Renovate is great. Plus there’s just something about Github owning dependabot that always bothered me.

The issue with node is the single threading and having to scale with worker threads AFAIK

People always say this but its not technically correct and can be misleading.

Technically, JavaScript runs single threaded but not Node.js itself and certainly not when using it on the backend in something like Express. IO operations and other things tooling libraries do can cause you to run out of a thread pool. But Node.js, when handling requests, gives you much of the benefit of multithreading without having to deal with multithreaded code.