oxnrtr

8 ms·

31.
by oxnrtr 4y ago
I readily believe that PHP devs struggle with anything more complex with Go, but that makes me question how people end up with the lack of will to learn and improve in this profession.
32.
by oxnrtr 4y ago
Go doesn't have a one-page spec, so what do you expect the GP to point to? You are proving his point.
33.
by oxnrtr 4y ago
Especially when other languages got them right.
34.
by oxnrtr 4y ago
Read the article maybe?
35.
by oxnrtr 5y ago
Maybe the core issue is that you are just not a good programmer.
36.
by oxnrtr 5y ago
Do you really think your incredibly arrogant and condescending comment adds anything to the debate? I encourage you to try and consider the author's points instead of simply attacking her character. I'll be there if you need help
37.
by oxnrtr 5y ago
I can't tell whether this satire.
38.
by oxnrtr 5y ago
Tell me you have basically no understanding of the subject matter without telling me you have basically no understanding of the subject matter.
39.
by oxnrtr 5y ago
There are good reasons for it, and I'm certain you will gain a better understanding as you gain more experience as a developer.
40.
by oxnrtr 5y ago
No.
41.
by oxnrtr 5y ago
fun read(path: &Path): io.Result[Vec[UInt8] { var file = File.open(path).orReturnErr() var bytes = Vec.new() file.readToEnd(&mut bytes).orReturnErr() Ok(bytes) } would be good enough for me, tbh
42.
by oxnrtr 5y ago
Paying people properly has very little impact on customer prices, see countries who enforce this.
43.
by oxnrtr 5y ago
CanBuildFrom got killed in 2.13, but taking a step back is exactly the right thing to do: The desire to return the same type of collection lead to overall slow performance; it turned out it's a design dead-end that Scala is still suffe
44.
by oxnrtr 5y ago
Joking? Scala 3 added 20 keywords (14 of them contextual), many of them with entirely new syntactic constructs behind it.
45.
by oxnrtr 6y ago
Using [] is the optimal choice for languages in general, but they can't even use that because they blew away that syntax for indexing.
46.
by oxnrtr 6y ago
They parse it one way, and if they figure out the other parse option was right, they go back and fix the parse tree. Basically, unlimited look-ahead.
47.
by oxnrtr 6y ago
Not really. That Rust forced total order and partial order into a sub-typing relation is a completely unnecessary, self-inflicted wound.
48.
by oxnrtr 7y ago
Can you link to such an action happening?
49.
by oxnrtr 7y ago
... and on Lobsters you would neither need to speculate what happened nor kneel in front of the mods to fix it, because moderation actions are publicly logged¹. :-) ¹ https://lobste.rs/moderations
50.
by oxnrtr 7y ago
Having a smaller community doesn’t mean "same composition of people, just fewer of them". I think Lobsters has done extraordinarily well in attracting domain experts while keeping out the valley-style surveillance capitalist block
51.
by oxnrtr 7y ago
Core team didn't care about Android. Simple as that. :-)
52.
by oxnrtr 7y ago
It absolutely does not. It removes a few things and adds a whole lot of new stuff to it. It's a bigger, more complex language, even if you credit all the cleanups that were already in Scala 2 to Scala 3.
53.
by oxnrtr 7y ago
So, no, Scala 3 won't help. Most people who cared left years ago.
54.
by oxnrtr 7y ago
As the person who was involved in Scala on Android (and particular in creating the website), I'll chime in with this: What sunk Scala on Android was largely the completely lack of interest from the core team. Everything that Scala on A