4 ms·

Congratulations on spotting a single keyword and otherwise failing to read the entire post! Throwing your fucking "credentials" around and writing your own asse

Congratulations on spotting a single keyword and otherwise failing to read the entire post! Throwing your fucking "credentials" around and writing your own assembler out of Ruby or whatever doesn't excuse you from exercising some basic fucking reading comprehension. The largest system built in Scala is probably pretty small at this point. But like I said if you had bothered to read the fucking post, the risks of moving to a new language when you can keep the rest of a deployment stack are relatively small. You're compiling to the same bytecode, running on the same VM, running on the same server, and so forth. Your IT department or hosting provider doesn't even need to know you switched languages. Please, do me a favor. If you're going to respond to this and tell me that Ruby is the most proven language ever and you can't trust Scala to display hello world, could you try to read the post this time and make at least a passing attempt to respond to the substance of it?

tptacek 18y ago
Wow, that struck a nerve, didn't it?
- wanorris 18y ago
  Thanks for making it clear that you have nothing to contribute to the substance of the matter except for snide remarks.
  - tptacek 18y ago
    You went from reasonable-but-wrong to very-angry in the span of just one comment. Why are you taking this personally? I'm sorry, but the fact that neither Scala nor F# have ever been successfully used in a well-known large-scale project is a substantive argument. Address it! I'm not a fan of C++ either, but guess what? It has a better track record than Scala. The idea that I'm going to pick Scala over Java "because they run on the same VM" is as silly as the idea of me trying to sell management on building their next product in ObjC, because, after all, they're both generating the same native X86 code. Of course, the real costs and risks have to do with training, maintenance, community, and support, which is why we still use Java. I'm not sure if you noticed like 4 comments above, but I'm a systems programmer; I have no idea why you think I care that something runs on the JVM. I do, however, sell to enterprises. The VM they care about isn't the JVM: it's VMWare ESX. You could write your app in SNOBOL and they won't care as long as they can plug it into their clusters.

tptacek 18y ago

Wow, that struck a nerve, didn't it?

wanorris 18y ago
Thanks for making it clear that you have nothing to contribute to the substance of the matter except for snide remarks.
- tptacek 18y ago
  You went from reasonable-but-wrong to very-angry in the span of just one comment. Why are you taking this personally? I'm sorry, but the fact that neither Scala nor F# have ever been successfully used in a well-known large-scale project is a substantive argument. Address it! I'm not a fan of C++ either, but guess what? It has a better track record than Scala. The idea that I'm going to pick Scala over Java "because they run on the same VM" is as silly as the idea of me trying to sell management on building their next product in ObjC, because, after all, they're both generating the same native X86 code. Of course, the real costs and risks have to do with training, maintenance, community, and support, which is why we still use Java. I'm not sure if you noticed like 4 comments above, but I'm a systems programmer; I have no idea why you think I care that something runs on the JVM. I do, however, sell to enterprises. The VM they care about isn't the JVM: it's VMWare ESX. You could write your app in SNOBOL and they won't care as long as they can plug it into their clusters.