No, it has been worked the way GP wrote since approximately forever.
True in the sense that Scala has a magnitude higher number of repos, commercial adoption, libraries, than F# (while being much closer to ML than F# in a few important was).
Every dollar earned by advertising prescription drugs to the general population is a dollar that shouldn't have been earned in the first place. See the Opioid epidemic that is still taking lives in the US for more than…
> But if their revenue levels in the U.S. were at the level they are in Europe, they absolutely could not justify their enormous fixed costs. Maybe the public could help them substantially lower the costs by not…
So you blame Scala both for Java's mistakes as well as addressing them, while Kotlin, which doubles down on Java's poor decisions does everything right? This makes literally no sense at all. Also, only a few of the…
> (Option, nullable return value, and throw an exception if not found) Which Map are you talking about? I don't see the method that returns nulls for missing values. > Kotlin has only single way. ... with the nice…
Consider two functions (excuse my Scala): val str: Function[String, String] = s => if (s.length > 3) s else null val num: Function[String, Integer] = s => if (s == null) -1 else s.length With Optional, you receive…
> Also, Optionals are a light introduction to functors which is nice. Optional is not a functor, in fact it violates the functor laws quite blatantly.
This problem was coined by Paul Graham as the "blub paradox": you can only notice inferior languages, abstractions and paradigms to what you currently know, but you can't easily notice superior ones, unless you make an…
Someone measured it and and it is fact it's substantially slower than Scala: https://twitter.com/kmizu/status/817570546179194881 Kotlin marketing != reality, it seems.
I recommend watching the talk.
Do you have an example of what broke between 2.11.7 and 2.11.8?
In my experience Scala(.js) works way better than "(node -> JS, Java -> GWT, etc)". There is a large gap between those and the way Scala _just works_ across platforms. The huge difference is that you can depend on…
That says more about your preferred language than the listed concepts. A language limited to a level of advanced beginners is not necessarily bad, though.
I'm not the one being ignorant. See your other comment where you have been flat-out misinformed.
If all you found was an old API from half a decade ago that doesn't even exist anymore, than I think that's a pretty good case for Scala.
> theoretically capable of supporting even banks https://scala.epfl.ch/ > The examples you mentioned are relative small. You know what's big? Walmart. WellsFargo. Honeywell. Novartis.…
I'd say this is blatant non-sense usually coming from people who lack any kind of experience in C++, Scala or both.
(value, no error) (value, error) (no value, error) (no value, no error)
(int64, error) gives you exactly four possibilities. Either gives you exactly the two you want.
cringe. How ecactly is having to check twice the amount of cases an improvement (note btw, that checking for Left/Right is doing it wrong)?
Method count has nothing to do with size. Nobody ever said that. It should still be obvious though that 30kB can't even remotely fit the method overhead you are claiming. Look at your own link: Java => 16,306 Scala =>…
Method count forces multidex insanely early into development and for people who want the best UX that alone is a show stopper. That's a complete non-problem. Minimal overhead of Scala is 30kB (see…
Scala-Native has already a sizable community around it. It got almost 100 PRs shortly after it was published. Is everything perfect? No! Can you write stuff with it and have it work? Absolutely!
How? Even the tooling seems to be vastly superior to the Gradle one. Deals with SDK dependencies automatically, typed resources and views, better Instant Run, ProGuard caching, extremely low overhead, fast compiles, ...
No, it has been worked the way GP wrote since approximately forever.
True in the sense that Scala has a magnitude higher number of repos, commercial adoption, libraries, than F# (while being much closer to ML than F# in a few important was).
Every dollar earned by advertising prescription drugs to the general population is a dollar that shouldn't have been earned in the first place. See the Opioid epidemic that is still taking lives in the US for more than…
> But if their revenue levels in the U.S. were at the level they are in Europe, they absolutely could not justify their enormous fixed costs. Maybe the public could help them substantially lower the costs by not…
So you blame Scala both for Java's mistakes as well as addressing them, while Kotlin, which doubles down on Java's poor decisions does everything right? This makes literally no sense at all. Also, only a few of the…
> (Option, nullable return value, and throw an exception if not found) Which Map are you talking about? I don't see the method that returns nulls for missing values. > Kotlin has only single way. ... with the nice…
Consider two functions (excuse my Scala): val str: Function[String, String] = s => if (s.length > 3) s else null val num: Function[String, Integer] = s => if (s == null) -1 else s.length With Optional, you receive…
> Also, Optionals are a light introduction to functors which is nice. Optional is not a functor, in fact it violates the functor laws quite blatantly.
This problem was coined by Paul Graham as the "blub paradox": you can only notice inferior languages, abstractions and paradigms to what you currently know, but you can't easily notice superior ones, unless you make an…
Someone measured it and and it is fact it's substantially slower than Scala: https://twitter.com/kmizu/status/817570546179194881 Kotlin marketing != reality, it seems.
I recommend watching the talk.
Do you have an example of what broke between 2.11.7 and 2.11.8?
In my experience Scala(.js) works way better than "(node -> JS, Java -> GWT, etc)". There is a large gap between those and the way Scala _just works_ across platforms. The huge difference is that you can depend on…
That says more about your preferred language than the listed concepts. A language limited to a level of advanced beginners is not necessarily bad, though.
I'm not the one being ignorant. See your other comment where you have been flat-out misinformed.
If all you found was an old API from half a decade ago that doesn't even exist anymore, than I think that's a pretty good case for Scala.
> theoretically capable of supporting even banks https://scala.epfl.ch/ > The examples you mentioned are relative small. You know what's big? Walmart. WellsFargo. Honeywell. Novartis.…
I'd say this is blatant non-sense usually coming from people who lack any kind of experience in C++, Scala or both.
(value, no error) (value, error) (no value, error) (no value, no error)
(int64, error) gives you exactly four possibilities. Either gives you exactly the two you want.
cringe. How ecactly is having to check twice the amount of cases an improvement (note btw, that checking for Left/Right is doing it wrong)?
Method count has nothing to do with size. Nobody ever said that. It should still be obvious though that 30kB can't even remotely fit the method overhead you are claiming. Look at your own link: Java => 16,306 Scala =>…
Method count forces multidex insanely early into development and for people who want the best UX that alone is a show stopper. That's a complete non-problem. Minimal overhead of Scala is 30kB (see…
Scala-Native has already a sizable community around it. It got almost 100 PRs shortly after it was published. Is everything perfect? No! Can you write stuff with it and have it work? Absolutely!
How? Even the tooling seems to be vastly superior to the Gradle one. Deals with SDK dependencies automatically, typed resources and views, better Instant Run, ProGuard caching, extremely low overhead, fast compiles, ...