|
|
|
|
|
by toocool
3145 days ago
|
|
I took on a project in Java (web backend project) a few months ago, first Java experience, I was excited. After a couple months, the gratuitous (or what felt like gratuitous to me at least) verbosity of the language and all sort of abstractions and intricate relationship of classes/interfaces in libraries (the typical Java programmer mindset) drove me insane. Icing on the cake was the atrocity of frameworks (had to work with a legacy Spring codebase) and the need for using an extremely complicated IDE with a billion options and knobs in order to write any sort of code. I was incredibly happy when I finished and deeply regretted taking on that work. I didn't think it would have been that bad. I think if Java was my only option, I'd probably switch to a different non-programming career. To put things in perspective, I am a C (kernel development)/C++ (system programming)/Go (backend development) programmer usually, working with tmux+vim and respective plugins for lightweight code completion and navigation. |
|