Viewing profile — airless_bar

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. I…

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 …

I don't think anyone considers Python or Java modern. Nevertheless, this isn't about where adoption comes from, it's about how the language design was influenced by the advancement…

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".

Hey, they are Google! Java 6 is probably the most "modern" thing they can think of!

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 tho…

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. _Ever…

To save him time and frustration due to his project going nowhere?

I think it's a very valid question. Given that the constraints by the Python BDFL rule out any reasonable solution, why not move on?

> 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 an…

Comes off as a bit "me too" from my perspective. In the whole list of things there is literally only a single thing which isn't already shipping/existing in Scala.

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 …

> 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 …

Sorry, was meant to be a light-hearted response.

The whole point of this was to show that Scala's types preserve the structure of the computation. It might not be very interesting in the Option[Option[String]] case but imagine Tr…

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…

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 …

> formal name non-shitty > a trend in newer languages yes, only discovered a few decades ago :-D

They preserve the structure of the computation.