4 ms·
I don't really write in Java these days, but when I did the biggest pain points for me were: - IDE: IntelliJ and before that, Eclipse, were painfully slow to u
by fareesh 4y ago
I don't really write in Java these days, but when I did the biggest pain points for me were:
- IDE: IntelliJ and before that, Eclipse, were painfully slow to use. Even now occasionally if I have to launch Android Studio I have to wait for Gradle and various other things. The entire IDE gets sluggish while it's doing indexing and all sorts of weirdness. vim integration was quite poor at the time, I don't know if things have changed since.
- Verbosity: It always feels like I am writing boilerplate and long names. I remember trying to write something with websockets and no matter what library I picked there was a ton of boilerplate to write for just connecting to a socket and sending a message.
If given a choice I'd much rather write in Python, C#, Ruby or even Typescript. The language feels very dated - or perhaps there are newer ways to do things that I'm totally unaware of.
- fenesiistvan 4y agoIDE: Borland JBuilder was a king. I am still using it Websockets: you can write your own in around 400 lines of code. I did it. The specification/RFC is really simple. Just a few bits above TCP