premium-concern

14 ms·

91.
by premium-concern 10y ago
It provides zero abstraction, which is especially painful when handling errors. In Go you basically _have_ to handle the error right when you receive it, there is no way of usefully combining or composing it. Also error handling itself is v
92.
by premium-concern 10y ago
That's wrong. Feel free to present an example.
93.
by premium-concern 10y ago
Let's not oversell that. There are maybe in total 2 compilers out there which are still usable (i. e. not 10 years out of date and unmaintained). The specification is "open" in the sense that you can't build your own imp
94.
by premium-concern 10y ago
I think this would help a lot. It would also help to check whether the code mentioned in an issue that triggers a crash is equivalent to the code you have. Even if you can't publish your code, it might help to say "I'm seeing
95.
by premium-concern 10y ago
> I get a few crashes per week related to known bugs Interesting! Can you link to the issue?
96.
by premium-concern 10y ago
Do you have some examples for "type inference fails"? Do you have some examples for "compiler bug"?
97.
by premium-concern 10y ago
Which version of sbt-android do you use?
98.
by premium-concern 10y ago
Thanks. I couldn't have said that any better!
99.
by premium-concern 10y ago
> Not sure why you're bringing up Scala-Native again Weren't talking about that? > @tailrec has existed since 2.8 Yes? > I was thinking (given your mention) that maybe Scala-Native had done away with the problem It uses f
100.
by premium-concern 10y ago
Yes, because Scala-Native only exists for a month at this point in time.
101.
by premium-concern 10y ago
> It's still sad it can't be relied upon per language spec. :/ There is a @tailrec annotation which ensures that a method was optimized. It probably needs to be updated to understand Scala-Native's new abilities, but
102.
by premium-concern 10y ago
> but when thinking of Scala I can't help but think "Well, it's not quite Haskell, is it?". (The poor type inference, the whole OOP thing, the lack of TCO means that any Monadic abstraction must be trampolined and tha
103.
by premium-concern 10y ago
That sounds weird. How did you build it? Can you paste the SBT error?
104.
by premium-concern 10y ago
I recommend you try the JavaScript backend. I'm so sick of people spewing JetBrains' marketing points without checking the substance of it.
105.
by premium-concern 10y ago
Scala compiles to JavaScript, to the JVM, to Android, and (soon) to native. Give it a try!
106.
by premium-concern 10y ago
Well, if you think the most important technical improvement to language design discovered since the creation of Java in 1995 is some shorter syntax, go ahead. I guess. Despite some very loud people on the internet, it seems to have close to
107.
by premium-concern 10y ago
Wrong parent? (_and_ wrong content, btw)
108.
by premium-concern 10y ago
>> > Specifically, don't introduce new syntax > Hearing this in the context of Scala is hilarious[0]. I'm confused, I don't see any syntax in this link. Wrong link? > You have to ensure that the build system, b
109.
by premium-concern 10y ago
What's the "middle ground"? Java with a more concise syntax?
110.
by premium-concern 10y ago
Huh? None of that will be in 2.12 except unification, and that's already planned for backporting to 2.11 (and you can just use the compiler plugin until then). > I don't want to be stuck on an old version as the language moves
111.
by premium-concern 10y ago
Why?
112.
by premium-concern 10y ago
I think that's pretty much untrue. That program is 0.x seconds on Scala-JVM and 0.0x seconds on Scala-Native.
113.
by premium-concern 10y ago
I'm pretty sure that neither Go nor Elixir have anything to compete against Hotspot/Azul in the GC department.
114.
by premium-concern 10y ago
Which ones?
115.
by premium-concern 10y ago
> For Kotlin, all I need is to install the plugin on Android Studio and am off to the races. What is preventing you from doing that with Scala? I see that you filed a ticket that the setup of IntelliJ != Android Studio, but is there anyt
116.
by premium-concern 10y ago
There is no "dropping" except if you assume that Scala 2.11 will just disappear tomorrow. I don't get the whole dooms day scenario. - Google is working on Java 8 support. - The current version of Scala supports the current An
117.
by premium-concern 10y ago
> Every time I think about using Scala and go through the list of configurations I need to do, I just give up. It's pretty easy. You have to setup less things than with Gradle, because SBT deals with all the downloading, installing
118.
by premium-concern 10y ago
"workstation" ... "OSX" Yeah, sure! :-)
119.
by premium-concern 10y ago
Getting a bit desperate, Cedric?
120.
by premium-concern 10y ago
No.

More ›