smcj

33 ms·

1.
by smcj 15y ago
"I believe these figures are implausibly low - and an insult to IE users." MISSION ACCOMPLISHED!
2.
by smcj 15y ago
Could you elaborate?
3.
by smcj 15y ago
Yes, sure. There is much less discrimination against "other" people on non-Apple platforms and that's great!
4.
by smcj 15y ago
This is a great and honest article and has changed the way I think about Apple users/developers. Before that, I considered Apple users to be a group of gay douchebags, but today I have learned that there is at least a sane person on the oth
5.
by smcj 15y ago
It is still painfully slow, right?
6.
by smcj 15y ago
You ignorance is so painful embarrassing, it almost hurts to read your non-sense.
7.
by smcj 15y ago
What's wrong with List.of(...)? I think adding special syntax rules is a pretty bad idea.
8.
by smcj 15y ago
Oh god. Please no, collection literals are the worst idea ever. Making up special rules for some special classes in a language? What the fuck!?
9.
by smcj 15y ago
Mitigation would just have required to make an optimizer option non-default, like in 6.
10.
by smcj 15y ago
It is more like C/C++.
11.
by smcj 15y ago
Wrong.
12.
by smcj 15y ago
Just a few thoughts... - Scala has function inlining, look at @inline. - Module system: this looks extremely wonky, especially considering what Oracle is planning with Jigsaw - Pattern matching is extremely hard to get right - "No hybrid",
13.
by smcj 15y ago
Couldn't say it any better, thanks!
14.
by smcj 15y ago
The state of IDE support has pretty much changed since a year ago. IntelliJ pretty much rocks, Eclipse is done by the Scala team itself (no idea about Netbeans, though). While Scala IDEs haven't reached the level of maturity or the wealth o
15.
by smcj 15y ago
>>> Is driving a car better than eating a banana? >> They serve completely different goals. > Show us numbers. That makes sense, doesn't it? > That was the main request of my comment, and you come with a list of
16.
by smcj 15y ago
Why and how should actors outperform OpenMP or TPL? They serve completely different goals. Scala ships by default with sequential, lazy and parallel collections and actors. Akka (akka.io) provides a different implementation of actors (which
17.
by smcj 15y ago
Well, the Scala developers are currently moving their build system to Scala. This means they can fully bootstrap their language/compiler, library and build system from one source language. The .NET port has only added some minor changes to
18.
by smcj 15y ago
Well, there is also a JavaScript compiler in the works and a LLVM backend. Who cares? Adding more supported platforms makes the language and its libraries more stable and mature, because less things are taken for granted. Things in the Java
19.
by smcj 15y ago
Well, some might actually want co-variant return types and "real" variance instead of the interface/delegate as well as non-broken array variance, real type inference, higher-kinded types (to not loose the collection type like in LINQ) and
20.
by smcj 15y ago
I found the authors mistake: "But now that students and parents are paying the majority of the cost of the education [...]" WTH? Every society which basically favours people with deep pockets instead of intelligent, gifted people (and don't
21.
by smcj 15y ago
As commented on the blog: I pretty much don't understand the comment about loosing exception information is about. Isn't that exactly what getSuppressed() does? printStackTrace() also mentions the suppressed exception, even with nice indent
22.
by smcj 15y ago
Yeah sure. Why should you do backups when you can start whining and pointing at Google instead...
23.
by smcj 15y ago
I'm really interested in that idea. That would create the possibility to clean up the remaining Java cruft like "every object is a monitor", clone vs. Cloneable, ...
24.
by smcj 15y ago
The compiler can only optimize simple calls in tail position, so recursive algorithms can overflow the stack, because the JVM lacks the support for any optimization here. No good IO/File API (because it needs support from the JVM for certai
25.
by smcj 15y ago
You have never looked more than 5 seconds at Scala, right? Option[X] is only a crock if you haven't understood it. Stop thinking of it as a "null check", start as thinking of it as a collection which can either hold 0 or 1 elements and then
26.
by smcj 15y ago
Failure to compile is always better than generating wrong bytecode.
27.
by smcj 15y ago
Hi Tony, isn't #963 more or less fixed? (It crashes the compiler, but doesn't fail at runtime anymore ...) Could you post a new example of it if it isn't?
28.
by smcj 15y ago
I had a completely different experience. Code is very readable, because it describes what it does and not how.
29.
by smcj 15y ago
> (even in Java/Scala, all method-dispatching is done at runtime, as you're dispatching based on the implicit parameter). Uh ... invokestatic? > For example, Scala cannot implement the Hindley–Milner algorithm for type-inference, be
30.
by smcj 15y ago
"works great" doesn't necessarily exclude "it's a stupid thing to do". I wonder how things like concurrency are expected to work, if no single line of code can be sure that things it expects will exist at runtime. Or maybe exists every 5 se

More ›