simon_o

9 ms·

61.
by simon_o 8y ago
That's true. More importantly, Rust and Kotlin work on improving things that matter to users, not on features that read nicely in a paper, but are largely irrelevant in the grand scheme of things. Just compare Rust's announcement
62.
by simon_o 8y ago
It seems like it. I recently took the liberty to update the language rankings on https://en.wikipedia.org/wiki/Scala_(programming_language)#L... and compared to 2016, Scala took a hit on pretty much every ranking. Outl
63.
by simon_o 8y ago
Not going to happen. I assume that the "added feature" section of the Dotty documentation and this blog entry have been written by different persons, because it's utterly impossible to reconcile those documents: More complica
64.
by simon_o 9y ago
Not surprising. Compatibility between minor releases has been unceremoniously jettisoned.
65.
by simon_o 9y ago
> Low wage immigration from Eastern Europe has put downward pressure on UK wages. How is this Europe's fault? That was a decision made by the UK, not the EU.
66.
by simon_o 9y ago
Scala has always been big on advertising it's abilities to abstract over things with it's type system (higher-kinded types, constructs from category theory, Haskell-inspired typeclasses), but has failed to actually out those capab
67.
by simon_o 9y ago
The ironic thing us that Scala could have just implemented java.lang.Iterable and/or java.util.Iterator, instead of rolling their own interfaces with largely the same methods with identical signatures.
68.
by simon_o 9y ago
No, because Option/Maybe can nested, nulls can't.
69.
by simon_o 9y ago
But those language communities also have to do some self-reflection. People are often hostile to things they don't know. Not taking this into account when trying to introduce new things is a recipe for disaster. This means ... – pickin
70.
by simon_o 9y ago
> The minor versions are interchangeable. They are not, at least in Scala. See 2.12.x.
71.
by simon_o 9y ago
I'm not sure what you are arguing against. All I'm saying is that the situation is bad as-is, and it would be good to not make it any worse.
72.
by simon_o 9y ago
But having to worry about compatibility between minor versions is still bad. People have come to expect that minor versions are interchangeable (modulo fixes for clear regressions and changes made in reaction to important outside events lik
73.
by simon_o 9y ago
> If all you had was single return values (aka "int or throw Exception"), how would you model the io.Writer? This is not an problem, because a single return value is _not_ everything one has.
74.
by simon_o 9y ago
It is superior for readability and parsing, and combined together with ident: Type, you have a very consistent syntax (unlike other languages with generics, where you define e.g. generic methods one way, but call them in another).
75.
by simon_o 9y ago
Just without the callbacks. At least you could abstract over error handling with callbacks...
76.
by simon_o 9y ago
> The last two options are not idiomatic Go. Who are the authors of https://golang.org/pkg/io again? Yeah, 90% of Go devs agree with you. 10% think it is a really great idea. So you can never be sure without reading
77.
by simon_o 9y ago
Like nil interfaces not being nil. Or using characters from the Canadian Aboriginal Syllabics unicode block to emulate generics.
78.
by simon_o 9y ago
Exceptions are bad outside the "your computer just started burning" cases, but Go has replaced them with something even worse, "multiple return values". So instead of some imagined return of "int or throw Exception&
79.
by simon_o 9y ago
Wrong thread? Nothing you wrote has any relationship with what GP commented on.
80.
by simon_o 9y ago
I think the Scala version does exactly what you want it to do, but you seem to be confused about something that I can't really pin-point. > Why do I need a separate Person and Dog class? You don't. It's an example. > Ca
81.
by simon_o 9y ago
> Mesa is lacking in terms of features compared to Nvidia's implementation Mesa is open-source. Nvidia can submit patches at any time they want.
82.
by simon_o 9y ago
The right approach is to include your own package repository in the deb file so that it gets automatically added to the system when people install the application.
83.
by simon_o 9y ago
The biggest issue with claims like "there are only diminishing results when using a type system better than the one provided in my blub language" is that it assumes people keep writing the same style of code, regardless of the ass
84.
by simon_o 9y ago
Then let's ban cars in cities, considering the harm car traffic has caused to inner cities andvtgeir inhabitants. Oh, and don't complain that infrastructure built for cars sucks when used by bikes.
85.
by simon_o 9y ago
Migrated to Vivaldi after 15 years of Firefox. I highly recommend Vivaldi and would pay for it, given the option.
86.
by simon_o 9y ago
It's 2017, I'm not placing ; by hand anymore. We have computers they are perfectly able infer them for me. > Javascript's handling of semicolon is nuts, I wouldn't say Rust's is. - JavaScript does insane things,
87.
by simon_o 9y ago
> I just think that using the semicolon to make the function return unit instead is problematic. Agree. The idea to attach additional semantics to ; is completely nuts, especially as ; is mandatory in Rust (usually, there are odd corner
88.
by simon_o 9y ago
This hardly makes any sense, is not practical to implement and theoretically questionable. It makes decisions that break existing code and introduce pointless complexity, while failing to offer any tangible benefits in return.
89.
by simon_o 9y ago
> Maybe collections of values should be different from collections of references. The sensible use cases for the two are quite different. I think all existing code disagrees with that. There has been great value derived from being able t
90.
by simon_o 9y ago
"Dynamically" typed languages are untyped, and are therefore likely considered out of scope in this document.

More ›