https://bugzilla.mozilla.org/show_bug.cgi?id=1687635
(Speaking as someone whose native language is non-Latin-based, I think it was a very bad idea. Worse still is their attitude that if some website becomes unusable, "just file a bug".)
https://bugzilla.mozilla.org/show_bug.cgi?id=1687635
(Speaking as someone whose native language is non-Latin-based, I think it was a very bad idea. Worse still is their attitude that if some website becomes unusable, "just file a bug".)
Mozilla is run by one of the most inept group of designers, who seem committed to killing off the last non-Chrome browser.
You know what feature they need to remove? Telemetry.
Their telemetry must show that practically zero of their users actually use the collected telemetry, and Mozilla itself can't seem to avoid using the "data" to make bad decisions.
Safari is still huge.
My previous point was that a walled garden being "huge" offers no benefit for the vast majority of people outside of the walled garden. How does this not apply to these arguments according to you? Because if they do, and I claim they do, then that reinforces my other statement that talking about walled gardens being huge is completely missing the point.
The presence of a proprietary web browser that only works on a specific platform restricted to a certain class of individuals which can afford to be on that platform doesn't really add much to the competition.
> another reason might be handing Google de-facto control over standards
I don't see Apple having that control to be any better although from what I've been reading about web browser engines and the underlying technology, I doubt anyone else, besides a few behemoth tech companies, can take any sort of control. The web is too far gone for that.
Overall, yes it is still a major player (20%) but notably almost all of that is on mobile where it's 27% of users worldwide (presumably in large part because of the iOS browser ban).
On desktop meanwhile, Safari is now below 10%, slowly but steadily declining, and it looks like to be overtaken by both Edge and Firefox within the next year or two. Bad news for Safari, but honestly surprisingly good news for Firefox. Edge's success is promising for the web too imo, if it gives Google less influence over Chromium.
> Safari is still huge.
Sorry, I meant to say WebKit-based.
Edit: On second thought, how can you even attempt to use telemetry to justify feature removal when a sizable portion of your userbase disables telemetry?
If you are up for a second serving of irony, comments for that bug are restricted because someone tried to incite the HN mob onto it a few days ago: https://news.ycombinator.com/item?id=30379655
https://memex.marginalia.nu/log/36-localized-programming-lan...
We all draw different lines for what feature is not common yet not rare enough to remove, so the context always matters.
For this subject of character encodings, browsers have already reduced their repertoire of suppported encodings for a good chunk of the last decade: the Encoding Standard [1] is substantially smaller than what it used to be (I know because I did implement all of them back then). Some of them (e.g. UTF-7, not exactly "removed" from the Standard because it was never added AFAIK) caused security issues but others (e.g. HZ) didn't and only got removed by the lack of usage. This kind of decision, either for or against, can be only backed with telemetry-like quantification anyway. No criticism in the issue was based on the concrete evidence; Henri Sivonen is right to say that he "can't address remaining non-Latin problems without seeing concrete examples that need addressing".
Wow, this is exactly what happened to me (probably between 8 and 10). I had an old 286 computer, where I learnt BASIC by reading programs already available on the computer.
I wrote programs, but had no idea what the keywords meant. I remember reading out loud "IF … THEN … ELSE" that I pronounced "if … ten … elsse", and my father in the room corrected my pronunciation, "it's if … then … else".
I was very surprised, because he didn't know BASIC at all. "How do you know this?" "It's how we pronounced it in English. It means 'si … alors … sinon'." o_o
It was a revelation to me: the "keywords" I typed in BASIC programs were not just meaningless tokens for the BASIC language, they came from English and had a meaning outside BASIC.
> Notice: "String" and "Thread" are the same thing to non-computing people. #True #Programming
Note that they are not actually removing any encodings themselves, so the argument from security / attack surface doesn't arise: the website can still send text in any of those encodings (or malformed but autodetected as such). This is purely about UX.
No. If the visitor is able to freely choose the page encoding, then the attacker can lure one into doing so by presenting a seemingly malformed partial text. So it will allow the attacker to control the victim page's encoding, only less effectively though.
---
I'm also very annoyed about the disproportional amount of criticism received by Firefox compared to Chrome here, because Chrome has proactively removed the encoding selection UI well before Firefox tried to do similar. And---to elaborate what I referred to the "telemetry-like quantification" before---Firefox concluded that the UI can't be completely removed without breaking a lot of existing pages using the telemetry [1], hence this "Repair Text Encoding" feature. It is hopelessly absurd to blame Firefox alone for this issue.
The good thing is that we have Vivaldi, Opera's spiritual successor in many things including this one: if somebody needs a knob, it'll be there.
> "just file a bug".
It's not just "a bug", it's "a low priority bug" - it's a polite way to say "I couldn't care less".
Bad in principle or bad because you've personally encountered pages where the menu item doesn't work but macOS Safari's submenu does?