Viewing profile — simon_o
simon_o
HN member- Joined
- Tue, May 16, 2017, 12:42 PM UTC
- HN karma
- 149
- Public activity
- 112 items
- HN profile
- View on Hacker News ↗
About simon_o
No profile information was provided.
Recent public activity
- comment
-
comment
Comment #41670238
Or maybe you don't want to. If that's the hill you want to die on, good luck.
-
comment
Comment #41659225
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?
-
comment
Comment #41657563
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 …
- comment
-
comment
Comment #41657249
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 …
-
comment
Comment #41657221
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 depen…
-
comment
Comment #41657063
> 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 …
-
comment
Comment #41444743
Unlikely, I'd expect most people to not have a meltdown about this.
-
comment
Comment #41059757
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 …
-
comment
Comment #41037667
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 embe…
-
comment
Comment #41035568
Some Rust people just have to be that dramatic.
-
comment
Comment #41035563
It has everything to do with Rust's decisions.
-
comment
Comment #41034648
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".
-
comment
Comment #41034561
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 rati…
-
comment
Comment #39929847
> 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'…
-
comment
Comment #39928713
> 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 pa…
-
comment
Comment #39928678
Mozilla only does what Google tells them.
-
comment
Comment #39204739
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.
-
comment
Comment #39054052
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 embarrass…
-
comment
Comment #38276375
Most likely not wanting to repeat Rust's mistakes.
-
comment
Comment #37791791
Ah, here it is, the clueless/idiotic comment about the CCC being left that is guaranteed to show up every year on HN.
-
comment
Comment #37224111
If you know nothing, maybe don't comment?
-
comment
Comment #37035232
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…
-
comment
Comment #36984579
[flagged]