5 ms·

Lol, what? NPM is amazing

by nawgz 4y ago

nawgz 4y ago
These downvotes are absurd. The parent comment asserts, without evidence, that "NPM being easy to use is a double-edged sword that will swing back at you". I have never seen any evidence of this in action. What would it even mean!? Something being easy to use being casted as a negative in-and-of-itself sounds like Stockholm Syndrome. If you'll downvote a long-time NPM user for questioning what's wrong with NPM given how much better it is at navigating the complex corporate environment I sit in than Gradle or Maven, at least leave an anecdote.
- speed_spread 4y ago
  It's all on you. You brought npm into the discussion which was until then quite generic comparing java builds against "others". You barge into a thread of people praising a certain ecosystem by defending your own turf and trying to convince everyone that your tools are actually ok. What did you expect? Sure bro, use npm, whatever.
  - nawgz 4y ago
    How is it "on me" that stupid "opinions" are being expressed? First of all, the context was: my initial comment's GP: "I do really like how easy the packaging is in Python and JS is", "Maven and Gradle are a bit of a pain to configure in comparison" my initial comment's parent: "True but beyond hobby projects this becomes a double-edged sword that swings back at you." This comment CONTINUES to be a naked assertion based on nothingness. The negative points about NPM I've heard are: * You should never touch human-readable files with CLIs (like package.json) * NodeJS imports make many files because it's interpreted code * running a command to install a package is "weird" and doing it manually is better * Something about module resolution that was fixed half a decade ago but still didn't impact most shops that avoided drowning in libraries You can't be serious that this is meaningful feedback.
    - speed_spread 4y ago
      > stupid "opinions" Whatever the subject, I expect people who like a certain tech to express their distaste about other techs. I just, you know, let it slide cause otherwise it's never over. If you're looking for a bone to chew, I'd suggest you go to Reddit. Seriously.
kaba0 4y ago
For stress testing file operations?
- nawgz 4y ago
  For my Java projects, to support different environments - corp proxies, let's say - I have to have entire different gradle files, plugins, options, routing, it's just disgusting. For my JS projects (obviously actually TS these days), I use the exact same config, it's parametrizable to take in one argument - the private registry to use. It's amazing for really using. Unlike Java package managers.
  - thrwawaies34 4y ago
    Have you tried using profiles? Maven supports build profiles. Spring and other frameworks also supports runtime profiles, where you can have a YAML file for each profile/environment
    - nawgz 4y ago
      The root of this thread is the person I responded to claiming NPM, as an easy-to-use package manager, would "become a double-edged sword that swings back at you" Meanwhile, you are having to tell me Java package management is actually better because... it has profiles I think that Java guys might have their heads too far up their asses
      - kaba0 4y ago
        No, we have just worked with huge enterprise applications for 20 years and attempted to get the build system right a few times already, learning from previous attempts — as opposed to creating some mess of ad-ridden (seriously — having terminal ads, are we crazy?!!), slow (windows literally chokes up on deleting the node_modules folder, which is not a rare operation), displaying some insane number of vulnerabilities no matter what, which is also due to having way too many too small packages, and every one bringing in a huge deal of other bullshit tiny dependencies. Oh, did you know that maven wasn’t hit by those dependency confusion attacks, being almost alone in that? Also, I can literally build a million lines repo faster than the frontend which is relatively small and just outputs goddamn js and css files..

Lol, what? NPM is amazing

by nawgz 4y ago

Lol, what? NPM is amazing

These downvotes are absurd. The parent comment asserts, without evidence, that "NPM being easy to use is a double-edged sword that will swing back at you". I have never seen any evidence of this in action. What would it even mean!? Something being easy to use being casted as a negative in-and-of-itself sounds like Stockholm Syndrome. If you'll downvote a long-time NPM user for questioning what's wrong with NPM given how much better it is at navigating the complex corporate environment I sit in than Gradle or Maven, at least leave an anecdote.

speed_spread 4y ago
It's all on you. You brought npm into the discussion which was until then quite generic comparing java builds against "others". You barge into a thread of people praising a certain ecosystem by defending your own turf and trying to convince everyone that your tools are actually ok. What did you expect? Sure bro, use npm, whatever.
- nawgz 4y ago
  How is it "on me" that stupid "opinions" are being expressed? First of all, the context was: my initial comment's GP: "I do really like how easy the packaging is in Python and JS is", "Maven and Gradle are a bit of a pain to configure in comparison" my initial comment's parent: "True but beyond hobby projects this becomes a double-edged sword that swings back at you." This comment CONTINUES to be a naked assertion based on nothingness. The negative points about NPM I've heard are: * You should never touch human-readable files with CLIs (like package.json) * NodeJS imports make many files because it's interpreted code * running a command to install a package is "weird" and doing it manually is better * Something about module resolution that was fixed half a decade ago but still didn't impact most shops that avoided drowning in libraries You can't be serious that this is meaningful feedback.
  - speed_spread 4y ago
    > stupid "opinions" Whatever the subject, I expect people who like a certain tech to express their distaste about other techs. I just, you know, let it slide cause otherwise it's never over. If you're looking for a bone to chew, I'd suggest you go to Reddit. Seriously.

kaba0 4y ago

For stress testing file operations?

nawgz 4y ago
For my Java projects, to support different environments - corp proxies, let's say - I have to have entire different gradle files, plugins, options, routing, it's just disgusting. For my JS projects (obviously actually TS these days), I use the exact same config, it's parametrizable to take in one argument - the private registry to use. It's amazing for really using. Unlike Java package managers.
- thrwawaies34 4y ago
  Have you tried using profiles? Maven supports build profiles. Spring and other frameworks also supports runtime profiles, where you can have a YAML file for each profile/environment
  - nawgz 4y ago
    The root of this thread is the person I responded to claiming NPM, as an easy-to-use package manager, would "become a double-edged sword that swings back at you" Meanwhile, you are having to tell me Java package management is actually better because... it has profiles I think that Java guys might have their heads too far up their asses
    - kaba0 4y ago
      No, we have just worked with huge enterprise applications for 20 years and attempted to get the build system right a few times already, learning from previous attempts — as opposed to creating some mess of ad-ridden (seriously — having terminal ads, are we crazy?!!), slow (windows literally chokes up on deleting the node_modules folder, which is not a rare operation), displaying some insane number of vulnerabilities no matter what, which is also due to having way too many too small packages, and every one bringing in a huge deal of other bullshit tiny dependencies. Oh, did you know that maven wasn’t hit by those dependency confusion attacks, being almost alone in that? Also, I can literally build a million lines repo faster than the frontend which is relatively small and just outputs goddamn js and css files..