←back to thread

Mozilla lays off 70

(techcrunch.com)
929 points ameshkov | 1 comments | 15 Jan 20 19:48 UTC | HN request time: 0s | source
Show context
dman ◴[15 Jan 20 21:11 UTC] No.22058629[source]▶
Brendan Eich has a helpful chart of Compensation of Highest paid executive at Mozilla vs Firefox market share over time.

https://twitter.com/BrendanEich/status/1217512049716035584/p...

replies(8): >>22058725 #>>22059044 #>>22059122 #>>22059260 #>>22059384 #>>22059453 #>>22059705 #>>22060015 #
throwaway123x2 ◴[15 Jan 20 22:02 UTC] No.22059260[source]▶
It's crazy how much FF's marketshare has dropped. It's such a great browser.
replies(7): >>22059466 #>>22059499 #>>22059567 #>>22059596 #>>22059736 #>>22059800 #>>22060719 #
pier25 ◴[15 Jan 20 22:35 UTC] No.22059567[source]▶
Hmm I don't know. I switched to FF 4 months ago and while the engine and dev tools are great, it's simply not as polished as the competition.

For example just look at the alert popups[0], or the non native contextual menus, or the video pop icon. The UI is full of little quirks like that. The tab bar is by far the ugliest one of all current browsers, at least on macOS.

It also misses important features such as multilingual spell checking. For people writing in multiple languages it's a real PITA. I know this functionality can be added with an extension but it slows down FF too much IMO.

[0] https://imgur.com/lODjWSm

replies(11): >>22059585 #>>22059635 #>>22059668 #>>22059780 #>>22059919 #>>22059953 #>>22059956 #>>22060062 #>>22060128 #>>22060191 #>>22060207 #
somishere ◴[15 Jan 20 23:35 UTC] No.22060062[source]▶
@pier25 Would honestly disagree on your 'polish' concerns. I consciously 'returned' to Firefox macOS a little over a year ago from a contented experience with Chrome, for entirely non-practical reasons (it just felt like a good idea). And it's been nothing but pleasant. I'm a massive fan of the UI, it's simplicity, flexibility, but also its bold sense of self. I despise the too-polished feel of safari. It is impractical. And chrome I return to semi-regularly for debugging or QA, but it honestly feels like a downgrade. It's so plain. So lifeless. So google. Sure there may be edge-case usability issues on FF, such as your multi-lingual spell check, but this seems like an entirely workable extension challenge. Safari on the other hand is drowning in edge cases ... and chrome - privacy.
replies(1): >>22060891 #
1. pier25 ◴[16 Jan 20 01:41 UTC] No.22060891{3}[source]▶
> Sure there may be edge-case usability issues on FF, such as your multi-lingual spell check, but this seems like an entirely workable extension challenge

It's an issue that affects anyone that writes in multiple languages. This accounts for the majority of internet users in the world since they write at least in their own language and English. This is not an edge case that affects 10% of users.

Like I already explained, it can't be solved properly with an extension. The ones that try to solve it slow down FF. This has to be solved at the native level, not in JS.