How many more "frameworks" do you need before you recognize that your language of choice is garbage? So the myriad of frameworks that wrap around JavaScript, the node framework that wraps around those, then the nvm framework because npm is garbage, then you have the other systems lol like webpack because your frameworks around frameworks around frameworks do such a complete and horrible job of managing themselves and the output they produce.
Embracing the future should not mean inheriting a giant pile
I think it is in most cases just much easier to wrap something and make something new in JS. There is basically no way to "wrap" something around the j2ee framework, no people make sonething very new: apache spark or spring.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
How many more "frameworks" do you need before you recognize that your language of choice is garbage? So the myriad of frameworks that wrap around JavaScript, the node framework that wraps around those, then the nvm framework because npm is garbage, then you have the other systems lol like webpack because your frameworks around frameworks around frameworks do such a complete and horrible job of managing themselves and the output they produce.
Embracing the future should not mean inheriting a giant pile
I think it is in most cases just much easier to wrap something and make something new in JS. There is basically no way to "wrap" something around the j2ee framework, no people make sonething very new: apache spark or spring.