soc88

14 ms·

91.
by soc88 14y ago
Care to explain? I have not experienced that. From which language do you come from? It certainly has less syntactic sugar than Java...
92.
by soc88 14y ago
If stuff like length and indexing depend on the actual underlying representation, the implementation is broken regardless of the actual format used.
93.
by soc88 14y ago
Claims like this are exactly the reason why we will still be stuck with multiple useless encodings in 2030. I wonder how long it will take until people find their balls and decide to move towards the right direction.
94.
by soc88 14y ago
I like how Oracle educates developers about the proper handling of DTD's. (They didn't break it by accident for the third time already, right? RIGHT?!)
95.
by soc88 14y ago
... and also in Scala, although I agree that COBOL will remain in use until the end of mankind. :-)
96.
by soc88 14y ago
> That must be a accident of the way TIOBE is put together yes? No! I had at least expected that the author did his 5 minutes of research to discover that there are indeed issues affecting rankings of languages like Scala, Haskell, ...
97.
by soc88 14y ago
So basically vanilla PHP has won in your opinion, with Ruby not even being a small glimpse on the map?
98.
by soc88 14y ago
Replied to the wrong comment?
99.
by soc88 14y ago
About which year are you speaking exactly? 2005?
100.
by soc88 14y ago
Complains about length units, then goes on to use feet. Oh, the irony.
101.
by soc88 14y ago
Thanks. I updated my original comment.
102.
by soc88 14y ago
Dart is such an uninspiring, imagined-in-1995 language that I still wonder if I ever find a use-case for it. This we-are-from-Google-and-everyone-else-is-stupid approach to language design is imho the real disease (also see the comment on G
103.
by soc88 14y ago
"They copied the entire API ..." They are using Apache Harmony. Ask Oracle, they will tell you it is not Java.
104.
by soc88 14y ago
Yes. Just because it comes from Apple doesn't mean it has magic dust in it which makes broken stuff work. There is a reason no one is doing it except Apple. Apple choose ARC over GC because they never managed to get their GC to work reasona
105.
Scala SLICK — Next generation LINQ for the JVM(scalaquery.org)
2 points by soc88 14y ago|0 comments
106.
by soc88 15y ago
With a common bytecode there would probably be a chance for languages to be fast and not stuck with translations to JavaScript for the next decade.
107.
by soc88 15y ago
Why should that "scrap years of JavaScript optimization"? That doesn't make sense. (Completely ignoring the fact, that JavaScript is not fast and will never be.) Source-to-source-translation _always_ sucked and that's known for a few decade
108.
by soc88 15y ago
What a useless parade of hand-waving. If you actually read the article, you knew that one of the author's point was that PHP's problems are magnitudes of magnitudes worse than other languages in the wild. That's more or less a matter of fac
109.
by soc88 15y ago
It is amusing that most people defending PHP are not able to write a coherent English sentence. Just read the comments under the article.
110.
by soc88 15y ago
The problem with Scala (and Haskell, too) is that the search phrase TIOBE uses doesn't take different naming schemes into account. For many functional languages "Programming in X" is a lot more common than "X programming" Compare "Scala pro
111.
by soc88 15y ago
Yes, the sad all stuff which has been used to argue over a decade now. Do you think people are stupid? I don't think there is anyone left who didn't hear these straw men. People moved on, maybe you should too?
112.
by soc88 15y ago
Aren't for loops already fixed since months? (see https://github.com/scala/scala/commit/4cfc633fc6cb2ab0f473c2... ) Regarding ArrayBuffer: It is not as easy as it looks like, because of the conflicting nature of Arrays vs. Generics (yet an
113.
by soc88 15y ago
Almost every problem you mention is a problem of the underlying runtime. Are you sure you bash the right thing?
114.
by soc88 15y ago
This comment with all its hand-waving reads like it comes straight from 1990.
115.
by soc88 15y ago
> There's no concept of a user defined pass-by-value type. Everything is pass-by-value, but I understand what I mean. > Second paragraph ... Yes, it all sounds legit. But in reality, it is often quite different and after the JIT com
116.
by soc88 15y ago
Sorry, if I appeared as I tried to sell you something. > No, Scala cannot optimize all forms of tail recursion (such as mutually tail-recursive functions). In that case, you have to use scala.util.control.TailCalls to do it via trampoli
117.
by soc88 15y ago
That's why I said: > Most of it is supported in Scala scalac does not use trampolining. It rewrites tail-recurisve calls into “loops” (or jumps if you look at the bytecode). This is a case where the JVM lacks the necessary feature. Ther
118.
by soc88 15y ago
> but isn't really bad I keep hearing this from PHP people, too. :-) Yes, it is not as bad as PHP, but probably just 15 years behind modern language design.
119.
by soc88 15y ago
- Yes, HotSpot is “the real” thing and includes the best Oracle has. There is a JVM implementation from Azul too, which people consider to be excellent. - The case between Oracle and Google is not related to the code released by Sun/Oracle
120.
by soc88 15y ago
Most of it is supported in Scala, without much problems.

More ›