CorpusCalcium

14 ms·

1.
by CorpusCalcium 8y ago
Well then use Chrome, where you don't have to suffer the pea under your mattress that is typing about:profiles once in a while.
2.
by CorpusCalcium 8y ago
Wow, is it really that difficult to click "launch profile in a new browser"? I mean I know we're all becoming spoiled brats over time, but to consider a click or two "unusable" is truly beyond the pale.
3.
by CorpusCalcium 8y ago
>Mozilla refuses. about:profiles
4.
by CorpusCalcium 8y ago
Why can't the community do this for themselves, without having to make Mozilla do everything?
5.
by CorpusCalcium 8y ago
Nobody is "prohibited" from doing so. You want a Firefox that lets you do whatever you want, you can easily use an unbranded or pre-release build, or even roll your own or use someone else's lightly-tweaked fork. Nobody owes
6.
by CorpusCalcium 8y ago
Those modems should no longer be being used, period. If someone cannot afford a replacement and has an incompetent ISP incapable of providing them with a subsidized replacement, then that is a separate problem that needs addressing as soon
7.
by CorpusCalcium 8y ago
Assuming that device is actually worth accessing, then you could still keep and use an old version of a browser for that purpose. Newer browser versions should be pushing the web forward where possible.
8.
by CorpusCalcium 8y ago
Again, I have to wonder what divisions in Apple you're talking about. The folks I know working on WebKit practically have zero decision making power. It's all about saving face and keeping Safari viable as the only engine on iOS.
9.
by CorpusCalcium 8y ago
Not in any of the areas I'm familiar with. For instance they can't even fix long-standing standards-compliance bugs or other interop issues in Blink or YouTube or Google Search... they're way too busy pushing redesigns and fe
10.
by CorpusCalcium 8y ago
Not really, Firefox and Chrome supported the picture element well before Safari did. It was part of the nascent HTML5 standard. I believe what WebKit introduced was the analogous CSS image-set property, which likely influenced the picture&#
11.
by CorpusCalcium 8y ago
It would essentially have to, in order to support WebP as the web uses it.
12.
by CorpusCalcium 8y ago
No, he wasn't. He wasn't accepted as CEO by enough employees, but he could have stepped down and retained another position in the company, like CTO. Even he recognizes that Mozilla leadership wanted him to stay on board, but he ch
13.
by CorpusCalcium 8y ago
>legitimizing DRM like they have By this logic they had already long legitimized it through their grudging support for Flash. But don't let that stop you from trying to act like it's magically different. >where Mozilla will
14.
by CorpusCalcium 8y ago
It strikes me as intriguing that people think there was ever a "severe backlash" over Pocket, let alone that it was what would have caused Mozilla to buy Pocket. Why would they not have bought it right away if that was the case? F
15.
by CorpusCalcium 8y ago
Feel free, but I don't see why you would draw the conclusion that your money is not needed from what I said (even if Firefox has enough revenue to work with for now, your donations keep the whole organization viable as-is; you're
16.
by CorpusCalcium 8y ago
>Disclaimer: I donate to Firefox. No, you really don't. You donate to the Mozilla Foundation, who are the non-profit parent company who do these kinds of things, not build Firefox. Firefox is made by their subsidiary Corporation, wh
17.
by CorpusCalcium 8y ago
Sadly, in general this is a case of "we made a Chrome-specific site/app years ago because it was the easiest thing to do, and despite other browsers and some of our employees working hard since then to standardize the Chrome-speci
18.
by CorpusCalcium 8y ago
Not quite, but new and unproven features are supposed to be hidden behind a runtime flag to prevent a hot mess like what was caused with CSS/JS vendor prefixes. The Blink team are getting better at this, but they still really need to p
19.
by CorpusCalcium 8y ago
Very few people can devote the significant time necessary to make free professional-grade stuff just for the sake of a wider audience. And unless you're an artist who does that yourself, it's a bit much to ask others to meet your
20.
by CorpusCalcium 8y ago
I honestly don't remember the actual message from Mozilla varying much over the past two years when it comes to Vimperator-needed APIs. But then I don't remember anyone doing much to get things figured out on that front, so a la
21.
by CorpusCalcium 8y ago
Isn't that what this bug is mostly about? https://bugzilla.mozilla.org/show_bug.cgi?id=1215061
22.
by CorpusCalcium 9y ago
It's also fair to say that some people subconsciously go well out of their way to treat every vague similarity as part of some broader conspiratorial case that Firefox is trying to clone some other browser in general. Even when the pro
23.
by CorpusCalcium 9y ago
See https://addons.mozilla.org/en-GB/firefox/addon/smart-referer...
24.
by CorpusCalcium 9y ago
Sure, but that's the JS version. wasm is meant to produce smaller, less resource-intensive versions (and there is a wasm version of sqlite I believe [1]). I'd much rather see CDN and caching tech improve along with other low-level
25.
by CorpusCalcium 9y ago
What practical benefit would that really have over just using your choice of SQL engine with wasm, though?
26.
by CorpusCalcium 9y ago
But the full picture also includes the fact that if all people were willing to do was wait for someone else to do the work, then they really have no high ground to complain that it didn't get done in the time-frame they wanted. Other
27.
by CorpusCalcium 9y ago
Anyone can read the bug report there and see what actually happened. Nobody even tried to detail what they needed until the VimFX came around a year ago to do so, and to begin workin on an experimental API. That experiment didn't reall