> React Router is probably one of the most widely deployed JavaScript libraries ever and is the furthest thing imaginable from a project created by grifters to sell online courses.
This is a funny example (to me) because in 2017, one of the two co-creators of React Router (Michael) came to my job and gave a two or three-day in-person training course on React. I think he also covered Redux and React Router. We had a great time getting to know him.
It turns out that Ryan and Michael spent a substantial amount of time and effort on a side business called React Training. It is fair to say that their speaking engagements were a solid revenue stream, but agreed - definitely not grifters.
Not sure why this was dead. VoiceOver is an iOS/macOS feature and the comment author was expressing that the software quality has been declining.
This is an important issue IMO. After having worked on accessibility for mobile and web applications for several years, I gained a lot of empathy for assistive technology users. Apple should know better.
I think a lot of the people who use merge do so because that’s what they learned initially.
Anecdotally, a lot of my coworkers who use merge are conceptually trying to stack their commits on top of previous ones. My lukewarm take: most of the time, rebase is actually the intended operation and merge is used as a hammer.
In my opinion, the browser has been much better since 2017/2018. Have you used it in the last few years? Complaints about Firefox aside, the Manifest V3/uBlock Origin issue should be a major concern for tech-savvy Chromium-based browser users.
I was a hardcore Firefox user for many years. Today, Chrome just blows it away. Platforms are Android and Gnome Desktop.
I tried Firefox again about once a year, up until about 2022, and left disappointed again each time. Rust was important. Servo too. I'm not just hopping on the 'Mozilla blows money' train for no reason, I'm sad to see the browser languish while they blow money on things that don't matter. This doesn't matter.
I use Brave now, which has a whole host of haters, some for good reason. But it blocks ads and runs circles around Firefox on every platform that I use.
As a person who never used Chrome in a capacity to replace Firefox (I just refused to give up), I'll just share this [0].
As I understand, no amount of words can convince you because I neither know what your standards are, nor I have the right words to convince you to try Firefox again. So, you have to give it a try and see it for yourself.
As a matter of principle, I'd never use a browser which is funded by an advertisement company which lives off my data to show me ads and rob me of my privacy and cognitive capacity.
In my book, Brave is even worse on that matter.
Edit: To clarify: I still have Chrome installed for the odd, unmaintained site which happens to require something Chrome specific, but I just don't open it, since Firefox works for everything and works very well.
The problem is, benchmarks are never a fair game. It's the nature of the benchmark as a genre. You can always bias a benchmark towards some code path to show that you're superior.
Also, there are other factors to consider:
- Some of the benchmarks are "lower is better", so reading Y axis is important.
- Some results are very close (e.g. speedometer), but the zoom makes difference bigger, so reading the Y numbers again is important.
So, Firefox beats Chrome on WebAudio, StyleBench, AssortedDOM. However, this is still "benchmarks", The real world performance is very, very close.
The bigger picture is, when you look at longer histories, the performance is still being tuned and improved. So, Firefox people are not sitting on what they have.
Lastly, Firefox is way more sensitive to DNS response time when compared to Chrome, and a crowded site makes tons of requests. A fast DNS makes a ton of difference, which is way overlooked.
I used to run a DNSMasq instance when my ISP DNS was very slow. Now, my routers have their own tuned DNSMasq instances, so DNS is instant, so Firefox is as well.
> As a matter of principle, I'd never use a browser which is funded by an advertisement company which lives off my data to show me ads and rob me of my privacy and cognitive capacity.
Sure I do think we need to be pragmatic which is why I was questioning your original principle, but you don’t seem willing to abide by your stated principle at all. I’m just not sure why you said it if you have no intention to stand behind it
Just tell me a viable alternative. I'll migrate to it.
- Not funded by an advertising company / data broker, etc.
- Not chromium based.
- Not a Firefox fork.
- Works on Linux & MacOS natively.
- Daily-driveable (i.e. functionally equivalent with Firefox).
There isn't one, which was my point. By your originally stated principle, you are screwed, but now you seem to be just pretending you never stated that principle. I can quote it again if you like:
> As a matter of principle, I'd never use a browser which is funded by an advertisement company which lives off my data to show me ads and rob me of my privacy and cognitive capacity.
That is what YOU said. All you've been doing is against your own quote. I think the quote is stupid, for the reasons you pointed out. I'm just trying to show you that you're the one who said it, but you seem to be totally unwilling to admit that you did, even though it is clearly publicly there
Still upcoming (already in Nightly), but I'm very excited about vertical tabs, tab grouping, and a better profile UI. And proper uBlock Origin support is table stakes for me.
Better does not mean good. Quantum indeed fixed many of their old performance-problems, but at the same time they lost so many in terms of ability, and performance still feels second rate compared to Chrome. But to be fair, this also depends on what you do with them. And yes, I do use them both.
What do you mean by index files? It might depend on the bundler, but I haven’t heard of index.js/index.ts files being a hard requirement for a directory to be traversable in most tooling.
Russ - can you please explain the rationale for "In person NYC 5 days a week" and that it's non-negotiable? It seems that you're restricting your talent pool in a labor market that prefers remote work. Given that the Svelte talent pool is smaller as-is, this is counter-intuitive.
