3 ms·

When I went from Java to Ruby on Rails it was an incredible breath of fresh air, and a massive, massive time saver, and truthfully Ruby can do many things Rails

When I went from Java to Ruby on Rails it was an incredible breath of fresh air, and a massive, massive time saver, and truthfully Ruby can do many things Rails can not, and it worked well. On a language level though (I still hate java) but the type safety was nice and did save you a lot of worry. In retrospect I realize most of the issue was the frameworks available and all the terrible configuration stuff. I love that today you have so many more options because for a lot of time you do save time on a per line level..

masklinn 4y ago
> In retrospect I realize most of the issue was the frameworks available and all the terrible configuration stuff. Also that Java’s type system is… not great. So you have to put in a lot of effort (especially if it was before java 8, to say nothing of Java 5) and you just… don’t get much out of it. Even more so given the syntactic overhead of defining java types before records (or without Lombok), to say nothing of the performance cost.