Re:Why We switched from Python To Go
by tetha on Sunday April 09, 2017 @02:12PM
(#14073559)
Just my personal anecdote, but I recently had to port the backend of one of my pet projects away from ruby due to performance issues - parsing around 50MB of string in ruby isn't an amazing idea.
So I figured the natural choices there would be go because it's new and in demand, and java because I have a couple years of java se experience.
So, figured, let's evaluate java... and I just failed to comprehend the spring stack just from googled tutorials. There's such a dense layer of magic going on in there, I'd either need to not understand most of my stack, or spend weeks and weeks reading and understanding.
Re:Why We switched from Python To Go
by zaphar on Monday April 10, 2017 @07:46PM
(#14083590)
Yeah, Spring is one of the worst offenders I've seen. At my current job I'm working on code written with Spring and debugging takes probably 5 times as long as it should.
So I figured the natural choices there would be go because it's new and in demand, and java because I have a couple years of java se experience.
So, figured, let's evaluate java... and I just failed to comprehend the spring stack just from googled tutorials. There's such a dense layer of magic going on in there, I'd either need to not understand most of my stack, or spend weeks and weeks reading and understanding.