5 ms·

> I've read somewhere that Firefox telemetry showed that hardly anyone used the bookmark descriptions. > In that case, understandable they chose to remove them

by 394549 8y ago

> I've read somewhere that Firefox telemetry showed that hardly anyone used the bookmark descriptions. > In that case, understandable they chose to remove them. It's not understandable. That logic leads to dumbed-down, point-and-grunt products because the "telemetry" shows most users aren't power users. Anyway, how much effort does it really take to maintain a text field on a bookmark entity?

Karunamon 8y ago
I do kind of wonder how many power users are opting out of telemetry for privacy reasons... Unrelated, but dear god that bug tracker was infuriating to read. As in I had a strong desire to reach through the screen and shake a few by the shoulders asking "What the FUCK is wrong with you people?!" Concern over data loss nearly dismissed out of hand, a smug "you should have backups" response to intentionally caused data loss, and all this over what amounts to a property field on a bookmark... It's like I was reading the GNOME tracker! All this over "maintenance burden". Is the "maintenace burden" of a non-searchable field that's only visible in a single context really that high? Really? It seems like this is quickly becoming the go-to excuse to eliminate power user features in a way that those users will not see until its too late. "Developer" is already a subset of "power user", and "developer who reads the bug tracker for unwanted future surprises" is an even smaller subset.
unethical_ban 8y ago
>Anyway, how much effort does it really take to maintain a text field on a bookmark entity? My thought too! Legacy extension APIs are one thing. An extra DB column / key:value pair is nothing.
- StillBored 8y ago
  If you think about, how this simplifies anything, you will start to understand the mess that is the FF codebase (not that chrome is noticeably better, particularly if you try and build it anywhere outside of ubuntu/x86_64).
  - PurpleRamen 8y ago
    It's not a mess, it's just a case of "not used by me, so remove it". Instead of improving the feature they let it rot away, like so many others, and then ignore that people still used it. Really sad.

by 394549 8y ago

Karunamon 8y ago

I do kind of wonder how many power users are opting out of telemetry for privacy reasons... Unrelated, but dear god that bug tracker was infuriating to read. As in I had a strong desire to reach through the screen and shake a few by the shoulders asking "What the FUCK is wrong with you people?!" Concern over data loss nearly dismissed out of hand, a smug "you should have backups" response to intentionally caused data loss, and all this over what amounts to a property field on a bookmark... It's like I was reading the GNOME tracker! All this over "maintenance burden". Is the "maintenace burden" of a non-searchable field that's only visible in a single context really that high? Really? It seems like this is quickly becoming the go-to excuse to eliminate power user features in a way that those users will not see until its too late. "Developer" is already a subset of "power user", and "developer who reads the bug tracker for unwanted future surprises" is an even smaller subset.

unethical_ban 8y ago

>Anyway, how much effort does it really take to maintain a text field on a bookmark entity? My thought too! Legacy extension APIs are one thing. An extra DB column / key:value pair is nothing.

StillBored 8y ago
If you think about, how this simplifies anything, you will start to understand the mess that is the FF codebase (not that chrome is noticeably better, particularly if you try and build it anywhere outside of ubuntu/x86_64).
- PurpleRamen 8y ago
  It's not a mess, it's just a case of "not used by me, so remove it". Instead of improving the feature they let it rot away, like so many others, and then ignore that people still used it. Really sad.