I want to do the opposite: Give curly braces to all the indentation based languages. Explicit is better than implicit, auto format is better than guessing why some block of code was executed outside my if statement.
Yes, because (1) they spent that money badly as can be seen from the non-Google revenue numbers of Mozilla and Firefox's market share and (2) people are comparing practices of a company that gets $500M for free and a practices of a company that is essentially bootstrapped, which makes no sense.
Of course it's probably not the same user base. But the point imo is that users did use it and get value out of it, even if die hard users cried hard their browser was invaded and that Mozilla lost the plot.
We even have commenters here saying Pocket lost Firefox some market share (without any evidence or argument in favor, so a gut feeling too), but nobody to say that maybe the feature was used by some? And maybe that was a pull for Firefox vs Chrome. (I'm not saying it was, I'm just saying we don't know)
If they support it and have an incentive to listen to their customers and not shareholders, gladly. We can't keep using those logic of being afraid to invest then be mad when companies find someone who will.
> Mozilla hasn't had the benefit of the doubt for quite a while here
In contrast to Google Chrome? This is just FUD. Ublock Origin is still working and will be working. Full customization is still there and isn't going away. All of that is unlike in Chrom(ium).
This is not a thread comparing Mozilla to Google. This is a thread where we worry about how a non google browsing alternative stays alive. Of course none of us posting here trusts Google.
> Many investments completely fail and when that happens, investors get very little tax relief
I don't really believe it. Investment is always incentivized by tax breaks and other political gifts. But once things turn bad it's the citizen's turn to pay for it. Fire all staff? We pay for unemployment. Pollute the soil? We pay for cleanup. Empty the water table? Guess who's gonna depend on the state for clean water...
> To change them purely based on vibes would be catastrophically stupid.
Please tell that to every neo liberal in my country. Reducing taxes on the rich seems to be their passtime, while every time some kind of capital gain is mentioned, everyone and their dogs become experts in economics and can tell you it's folly.
I disagree, adding context to errors provide exactly what is needed to debug the issue. If you don't have enough context it's your fault, and context will contain more useful info than a stack trace (like the user id which triggered the issue, or whatever is needed).
Stack traces are reserved for crashes where you didn't handle the issue properly, so you get technical info of what broke and where, but no info on what happened and why it did fail like it did.
It's one piece of information, but logging at the error location does that still. And if you have a function that's called in multiple places how do you know the path that got you into that place. If it wasn't useful we wouldn't try to recreate them with wrapped errors
You wrap errors primarily to avoid the implementation detail leak. Even where errors have stack traces, you still need to do that, as was already described earlier. What debugging advantage comes with that is merely an aded bonus (A really nice bonus, to be sure. Attaching stack traces is computationally wasteful, so it is a win to not have to include them).
You can get away with not doing that when cowboy coding scripts. Python was designed to be a scripting language, so it is understandable that in Python you don't often need to worry about it. But Go isn't a scripting language. It was quite explicitly created to be a systems language. Scripts and systems are very different types of software with very different needs and requirements. If you are stuck thinking in terms of what is appropriate for scripting, you're straight up not participating in the same thread.
Even if my vision is okay, it still feels like a slap to the face. Can't take some time to make sure the most important part of the page is readable by all.
I specifically have issues with strong back lighting (genetic cataracts suck - I’m only in my 40s) so bright white page and light writing is super frustrating. Dark mode is my best friend.
reply