3 ms·

@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 C

@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.

pier25 7y ago
> 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.