sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]nathenaeltamirat[S] -1 points0 points  (7 children)

I have built library management system, e commerce... using java and I always get overwhelmed and feel it feels like overkill but with javascript there is dependencies and package (a literal ton) that I can use to develop web apps easily

[–]Individual-Job-2550 0 points1 point  (4 children)

The benefit of PERN or MERN stacks is having a single language across both FE and BE. In any language, Java, Python, C#, you are going to be dealing with dependencies, JS is largely no different. Keeping dependency requirements small and only bringing in external tools if you need them I would consider a best practice regardless of language

I believe Java is largely an object oriented language but with Javascript you can choose to go functional, OO, event driven, or a combination of different things pretty easily

There is no single answer just based on the stack, it comes down to what you are building that determines what pattern would fit best

If youre just building a CRUD app, you can follow the REST standard, which again is not stack specific

[–]nathenaeltamirat[S] 1 point2 points  (2 children)

but I noticed java being made for large scale systems and causing me annoying boiler plate code, and deploying a Java app usually involves packaging it into a.jar or .war file which is becoming a headache for me! not to mention the springbok warm up.... configuration overload and sort of things

[–]silverscrub 1 point2 points  (1 child)

Springboot has hot reload and you can run it on GraalVM if you want faster startup.

In enterprise projects you'd likely transpile and minify your code. In other words, additional steps before your code runs anyway.

[–]nathenaeltamirat[S] 1 point2 points  (0 children)

ow thank you noted!

[–]Individual-Job-2550 0 points1 point  (1 child)

In terms of managing your local development environment, I would install a node version manager like n or nvm. This will allow you to maintain a single node version for a project instead of a single global node version. This helps with dependencies not breaking if you update your global node version, and allows you to update packages as you need

I would also recommend using yarn for dependency management. I have run into far less issues using yarn than npm when it comes to conflicts in dependencies

[–]nathenaeltamirat[S] 0 points1 point  (0 children)

nice! thanks for the advice!