291–300 of 314 posts
Earlier quoted context omitted.
Go work with C++, and you'll pine for Java.
And go work with C# and you'll pine for nothing. I've used all three and after a few years of C#, the other two are just a distant memory.
If that was true, F# wouldn't have happened. (Nor IronRuby/IronPython). Even people who like the .NET platform often pine for something better for the task at hand than C#.
Earlier quoted context omitted.
You might want to check out Groovy. It's built on the JVM, you can use all the standard library and third party Java packages including stuff off Maven, and you can even just run straight Java code through it. However, at any time you can also drop into Groovy land, and write in a much more concise and functional style. Closures are very common (just look at anything in Gradle), it was clearly influenced by Python/Ru…
Meh, used Groovy for 2 years followed by a year of Grails 1.3.x hell. Both the language and the framework have likely improved since then, but after switching to Scala + Play there's simply no going back ;-) p.s. Haskell + Yesod (or Snap) look interesting as an alternative web stack to explore, but otherwise not seeing much out there that would draw me away from Scala land.
Earlier quoted context omitted.
Scala? It's still a very young language, though.
What have they removed from the standard library? Just curious.
Things which come to mind (comparing roughly 2.8 (released 2010-07) to 2.11 (released 2013-03)):
Classes (just from the top-level scala.* package):
- Application
- Cell
- cloneable
- CountedIterator
- NotDefinedError
- NotNull
- Responder
- serializable
- scala.actors and subpackages
- scala.collection.interfaces
- scala.concurrent (still exists, but its contents have been replaced completely)
- scala.dbc and subpackages
- scala.mobile
- scala.reflect.generic
- scala.swing and subpackages
- scala.testing
- scala.text
- scala.util.automata
- scala.util.continuations
- scala.util.grammar
- scala.util.logging
- scala.util.parsing and subpackages (includes parser combinators and JSON)
- scala.util.regexp
- scala.xml
The list is certainly incomplete anyway...
I have to admit I thought Java was dead in the water after Java 6, but Java 7 while a fairly quiet release was a decent release and Java 8 actually moves the language forward into a better place. As for the future here's what I would like to see: - Separation of language and libraries. Really the JDK should just ship with just a very small core of classes and everything else should be optional installed via a depende…
Heh? How are these things related to each other? Who in their sane mind would use tuples for error handling?
Earlier quoted context omitted.
You have probably encountered the occasional Java desktop app, without realising. If you can't easily tell it is Java, the development team have done a good job. Two of my company's three products are a Java desktop app for Mac, and they look and feel like typical Mac apps. Best practice? IMO you should spend significant time on the GUI making sure it feels native. Otherwise, Swing is still about as good as it gets f…
> You have probably encountered the occasional Java desktop app, without realising. If you can't easily tell it is Java, the development team have done a good job. I've never seen any Java desktop app that I cannot easily tell it's Java. With most of those apps, even on i7/16GB/SSD systems, you get laggy behavior with Swing and the GC. And SWT still has the "uncanny valley" look going.
Earlier quoted context omitted.
Does anyone enjoy SBT? My love for Scala is profound, but fuck SBT
Yes, I enjoy SBT. I miss it every time I end up working with similar tools for other platforms. I'm not crazy about the syntax and I avoid build.sbt files, but as a tool it's very pragmatic and takes care of my needs perfectly. It has incremental compilation and continous testing built in. For testing within SBT with something like say ScalaCheck simply works out of the box with no configuration necessary, by simply…
Earlier quoted context omitted.
Meh, used Groovy for 2 years followed by a year of Grails 1.3.x hell. Both the language and the framework have likely improved since then, but after switching to Scala + Play there's simply no going back ;-) p.s. Haskell + Yesod (or Snap) look interesting as an alternative web stack to explore, but otherwise not seeing much out there that would draw me away from Scala land.
Interesting. Scala always put me off, the sytax just seems so nasty. Does that just get better after working with it for a while?
There's a learning curve, can't hit the ground running as you can with Groovy, but with Groovy there's a ceiling; with Scala the only ceiling is (perhaps) Haskell and for that you have to leave the JVM.
Earlier quoted context omitted.
"v8 is not a browser engine either ,it's a javascript engine,just like Rhino. you are mixing up Webkit with v8." - I think you're partly correct but also confused. Webkit is a rendering engine and yes V8 is a JavaScript engine not a browser engine that was created for Chrome Browser by Google. It's used for Node.JS etc now but it's sole purpose was to make Chrome faster and that is not the same purpose of Nashorn - n…
And Nashorn is supposed to be faster than Rhino... Nashorn and V8 are both JS-engines, why wouldn't you compare them?
I have to admit I thought Java was dead in the water after Java 6, but Java 7 while a fairly quiet release was a decent release and Java 8 actually moves the language forward into a better place. As for the future here's what I would like to see: - Separation of language and libraries. Really the JDK should just ship with just a very small core of classes and everything else should be optional installed via a depende…
> Multiple return types. Scala has hacked around it, Python has them, Go has them. Bite the bullet and implement them so you can do sensible error handling without exceptions or returning `null`. Heh? How are these things related to each other? Who in their sane mind would use tuples for error handling?
f, err := os.Open("filename.ext") if err != nil { log.Fatal(err) }