Just read my other reply.
Wrong.
You are obviously wrong. While attacking a single package would be possible, covering any interesting amount of "typo"-space would require registering huge amounts of namespaces. If package manager developers are smart,…
Scala! Great language, huge ecosystem, good tooling, many platforms supported.
This only seems to be an issue for languages where packages reside in a global namespace, like Python, Rust etc. I think most languages these days are a bit smarter and avoid this beginner mistake (for various reasons).
I think dismissing anything invented after 1960/not invented at Google counts as "inflexible and unadaptable; unable to keep up with new languages or idioms".
Costly: yes. Why not use another language? I think it's a perfectly valid question for that guy to ask. My personal opinion on "Why not use another language" is a bit different though: Adopting a different language…
I don't believe that the question was meant to be a joke or a trolling attempt. The guy's competence isn't the issue. It's the requirements of what the fix can and cannot do. _Everything_ is a mess due to the massive…
> For example, you have both an option types and `null`, and libraries being inconsistent in which they pick. Which ones?
Yes, Scala is great. Way ahead in terms of providing developers with useful tools compared to most other languages. (It's not the usual run-of-the-mill language which takes Java and adds some syntactic sugar, so some…
I agree with lmm. The only thing where Kotlin wins is in marketing and hype.
No?
> I think the idea that API's (or implementations as you said) can be copyrighted is completely insane and I can't believe any software engineer would be okay with it. Which makes me think you're not a software…
> Missing values are not errors. Call it whatever you want. ? only covers a small subset of interesting "conditions" while tremendously hurting "conditions" which could be handled in a better way. > Uh copyright what?…
Yeah, it's just that-if you look at every language ever designed-if the language ships with a built-in construct developers will use and abuse it on every occasion, and every other approach lingers in obscurity. > Which…
Not really. The main strength of the first approach is that Option is only one type out of many error-handling structures. Not every error is handled appropriately by Option/?. If you have a language like Kotlin where…
> formal name non-shitty > a trend in newer languages yes, only discovered a few decades ago :-D
They preserve the structure of the computation.
Option[Option[String]] != String??
I can recommend Scala. The libraries are top-notch and unlikely to be found in other languages due to the superior typesystem. It has broad tooling support, and Scala's JavaScript backend is stable, mature and actually…
Standard Googler behavior. :-)
Ah alright. yes, I think it makes more sense to define the GUI with code. Typed resources help with it. sbt-android-gradle has full support for Gradle projects, but to be honest: Gradle is utter shit. Just use the SBT…
Which GUI tools do you have in mind?
Android integration works fine, and the SBT builder is so much better and faster than Google's Gradle one. In fact SBT + ProGuard is faster than Gradle + no ProGuard.
The C++ comparison is great because it tells readers that that the person making it has no idea about C++, Scala or both.
Just read my other reply.
Wrong.
You are obviously wrong. While attacking a single package would be possible, covering any interesting amount of "typo"-space would require registering huge amounts of namespaces. If package manager developers are smart,…
Scala! Great language, huge ecosystem, good tooling, many platforms supported.
This only seems to be an issue for languages where packages reside in a global namespace, like Python, Rust etc. I think most languages these days are a bit smarter and avoid this beginner mistake (for various reasons).
I think dismissing anything invented after 1960/not invented at Google counts as "inflexible and unadaptable; unable to keep up with new languages or idioms".
Costly: yes. Why not use another language? I think it's a perfectly valid question for that guy to ask. My personal opinion on "Why not use another language" is a bit different though: Adopting a different language…
I don't believe that the question was meant to be a joke or a trolling attempt. The guy's competence isn't the issue. It's the requirements of what the fix can and cannot do. _Everything_ is a mess due to the massive…
> For example, you have both an option types and `null`, and libraries being inconsistent in which they pick. Which ones?
Yes, Scala is great. Way ahead in terms of providing developers with useful tools compared to most other languages. (It's not the usual run-of-the-mill language which takes Java and adds some syntactic sugar, so some…
I agree with lmm. The only thing where Kotlin wins is in marketing and hype.
No?
> I think the idea that API's (or implementations as you said) can be copyrighted is completely insane and I can't believe any software engineer would be okay with it. Which makes me think you're not a software…
> Missing values are not errors. Call it whatever you want. ? only covers a small subset of interesting "conditions" while tremendously hurting "conditions" which could be handled in a better way. > Uh copyright what?…
Yeah, it's just that-if you look at every language ever designed-if the language ships with a built-in construct developers will use and abuse it on every occasion, and every other approach lingers in obscurity. > Which…
Not really. The main strength of the first approach is that Option is only one type out of many error-handling structures. Not every error is handled appropriately by Option/?. If you have a language like Kotlin where…
> formal name non-shitty > a trend in newer languages yes, only discovered a few decades ago :-D
They preserve the structure of the computation.
Option[Option[String]] != String??
I can recommend Scala. The libraries are top-notch and unlikely to be found in other languages due to the superior typesystem. It has broad tooling support, and Scala's JavaScript backend is stable, mature and actually…
Standard Googler behavior. :-)
Ah alright. yes, I think it makes more sense to define the GUI with code. Typed resources help with it. sbt-android-gradle has full support for Gradle projects, but to be honest: Gradle is utter shit. Just use the SBT…
Which GUI tools do you have in mind?
Android integration works fine, and the SBT builder is so much better and faster than Google's Gradle one. In fact SBT + ProGuard is faster than Gradle + no ProGuard.
The C++ comparison is great because it tells readers that that the person making it has no idea about C++, Scala or both.