simon_o

8 ms·

1.
by simon_o 2y ago
Or maybe you don't want to. If that's the hill you want to die on, good luck.
2.
by simon_o 2y ago
It's not an either or. We have hundreds of languages made to please the corporate overlords. Can't we just have one language that's actually nice to use?
3.
by simon_o 2y ago
That seems to be an absolute win to be honest. Not sure how you think this is helping your case. Maven Central people nuked the artifact that may have caused confusion, and if the owners try anything like that again, it's likely thei
4.
by simon_o 2y ago
I think Rust's `async` has been a great success for commercial "sponsors" of Rust, because it increased the complexity of the language so much that it's hardly possible anymore to contribute to it without being full-time
5.
by simon_o 2y ago
The problem is the ecosystem split and the decades of man hours of churn caused in libraries and user code – that's time and effort that could have been spent on making those dependencies better. This applies to both suggestions (&quot
6.
by simon_o 2y ago
> Namespace is not a solution for name squatting: namespace is just yet another identifier that can be squatted. If you are worried about squatting, the only effective solution is sandboxing, everything else is just moving the goal post.
7.
by simon_o 2y ago
Unlikely, I'd expect most people to not have a meltdown about this.
8.
by simon_o 2y ago
Not to mention that this boats gentlemen is on account number 3 already, so it appears that moderators on this site have already told –him more than once– that he should offer his "generous donations of free time" somewhere else i
9.
by simon_o 2y ago
I think there are some lessons that can be learned from Java's virtual thread approach – note that there is a huge gap in requirements and design trade-offs, especially around embedded, when compared to Rust. I'd just wager that t
10.
by simon_o 2y ago
Some Rust people just have to be that dramatic.
11.
by simon_o 2y ago
It has everything to do with Rust's decisions.
12.
by simon_o 2y ago
Agreed, it's just that in Rust async/await hurts more than in e. g. JavaScript where the browser gives you enough hooks to have a "fresh start with(out) async".
13.
by simon_o 2y ago
This. The harmful decisions Rust made highlight its ingrained culture of doubling down on previous mistakes at all costs. There seems to be no reevaluation of the cost/benefit ratio once the "preferred approach" turns out to
14.
by simon_o 2y ago
> you never need to think about it, only get smaller and more beautiful files People said the same thing last time and it took more than 10 years until decoding worked reliably. I'm simply not interested in dealing with another JPEG
15.
by simon_o 2y ago
> It's a yes! Reminds me of "You Scientists Were So Preoccupied With Whether Or Not You Could, You Didn't Stop To Think If You Should." The arithmetic coding feature was already painful enough. I'm simply not i
16.
by simon_o 2y ago
Mozilla only does what Google tells them.
17.
by simon_o 3y ago
You seem to have serious issues, and I hope that you can work them out. That's the prerequisite for me to engage any further with you.
18.
by simon_o 3y ago
That quote is programming language design's "We should improve society somewhat" – "Yet you participate in society! Curious! I am very intelligent." I. e. it's stupid and embarrassing to watch people use it.
19.
by simon_o 3y ago
Most likely not wanting to repeat Rust's mistakes.
20.
by simon_o 3y ago
Ah, here it is, the clueless/idiotic comment about the CCC being left that is guaranteed to show up every year on HN.
21.
by simon_o 3y ago
If you know nothing, maybe don't comment?
22.
by simon_o 3y ago
Your "it's just a matter of taste" just shows a lack of research. The decision has a lot of important second-order effects, and a lot of people are heavily invested in denying that because they are more familiar with "Ty
23.
by simon_o 3y ago
Exactly. Mozilla management is the Stephen Elop of Firefox.
24.
by simon_o 3y ago
Citation needed.
25.
by simon_o 3y ago
I'm not comparing sandboxing against SELinux/AppArmor. It's a social problem, not a technical one. I'm comparing "app developers holding themselves accountable" to "package maintainers dish out consequence
26.
by simon_o 3y ago
This has to be the dumbest take on this thread. If you want the dystopian hellhole you seemingly long for, just use Android and enjoy the ad-infested crapware? No reason to moan about things you seemingly don't understand.
27.
by simon_o 3y ago
> want sandboxing to work by default Yeah, wake me up when Flatpak is remotely close to doing this. Most "apps" simply disable the sandbox. Not to mention I'm not going to trust "app" developers setting their own
28.
by simon_o 3y ago
Yes. Deal with it.
29.
by simon_o 4y ago
What kind of dystopian bullshit is this? Occurrences of phrases like "better pay"/"higher wages"/"more benefits" in this BBC article: 0 Creative descriptions for intentionally burning people out: I st
30.
by simon_o 4y ago
> could do automatic semicolon insertion a-la javascript If you want to make a good faith argument against semicolon inference, that's not the way of doing it.

More ›