this post was submitted on 06 Aug 2023
145 points (97.4% liked)

Programming

17488 readers
123 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago
MODERATORS
snowe
Ategon
[email protected]
145
Why is the Node ecosystem so demanding? (sh.itjust.works)
submitted 1 year ago by [email protected] to c/programming
55 comments fedilink hide all child comments
 

Steps to reproduce:

  1. Start a Node project that uses at least five direct dependencies.
  2. Leave it alone for three months.
  3. Come back and try to install it.

Something in the dependency tree will yell at you that it is deprecated or discontinued. That thing will not be one of your direct dependencies.

NPM will tell you that you have at least one security vulnerability. At least one of the vulnerabilities will be impossible to trigger in your particular application. At least one of the vulnerabilities will not be able to be fixed by updating the versions of your dependencies.

(I am sure I exaggerate, but not by much!)

Why is it like this? How many hours per week does this running-to-stay-in-place cost the average Node project? How many hours per week of developer time is the minimum viable Node project actually supposed to have available?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 86 points 1 year ago (2 children)

Because 99% of Node projects are web related, and if something's vulnerable on the web it won't take long to be abused

[โ€“] [email protected] 13 points 1 year ago (1 children)

Hey, a good answer! ๐Ÿ™Œ

[โ€“] [email protected] 7 points 1 year ago* (last edited 1 year ago) (2 children)

Also a great disadvantage with JavaScript being the official scripting language of the web so it needs to work in every browser, but not every browser will implement it the same way. Syntax between the browser and servers also gets conflated.

I've done frontend development in Java and it sucks major ass. The "advantage" of using one language for the whole project really ended up as a net negative. For any server-side project I'm totally fine using Java because for all it's verbosity it's secure, performant, and examples from 10 years ago aren't useless.

[โ€“] [email protected] 3 points 1 year ago (3 children)

Fron-end development with Java? You mean Java applets or something?

[โ€“] kameecoding 4 points 1 year ago

JSF for example. e.g. Primefaces https://www.primefaces.org/ I think there is something like Omnifaces too

[โ€“] [email protected] 3 points 1 year ago (1 children)
[โ€“] [email protected] 1 points 1 year ago

Honestly looks like any other UI library/Framework for C#/Java.

However usually these elements are not instantiated/configured directly but from xml, yaml or json files that are built using some sort of GUI/Editor.

[โ€“] fabian 3 points 1 year ago

Google Web Toolkit was a thing at some point in time. ;y current company still maintains some apps which are written in it.

[โ€“] [email protected] 3 points 1 year ago (1 children)

JSP used to be the shit back in the day. Imagine server-side rendered html through Java. Nowadays it's properly regarded as shit, fortunately.

[โ€“] [email protected] 2 points 1 year ago

I tought JSP was just one templating solution like mustache, jinja2, Thymeleaf etc. But guess theres more to it.