4 ms·

This thing has been flying since 1977. Meanwhile a javascript app of mine from 2022 does not build now because I can’t get it to install the dependencies for s

by eknkc 2y ago

This thing has been flying since 1977. Meanwhile a javascript app of mine from 2022 does not build now because I can’t get it to install the dependencies for some reason. BTW, that transmitter apparently can not transmit back to earth at this point because it is too far away. But looks like it can receive (we can transmit with much higher powers here?) and they managed to send a command to restart the primary transmitter. Now debugging. Debugging on a 2 day feedback loop. Fuck that.

Cthulhu_ 2y ago
Caveat, the output from your build (JS/HTML/whatever) will likely still work like it did today in 20 years time. JS isn't the problem, it's the overcomplicated dependency and build systems that were layered on top. It's why Go is a breath of fresh air. A 10 year old codebase will still build and run like it was made yesterday.
- pants2 2y ago
  Yes, just as my 10-yr-old old Java Applets and Flash games run perfectly... oh wait.
SteveNuts 2y ago
> Debugging on a 2 day feedback loop. Fuck that. This is what it's like for me, working with an offshore QA group.
blitzar 2y ago
Debugging on a 2 day feedback loop. Reminds me of working at the branch office with HQ on the opposite side of the world.
- BrandoElFollito 2y ago
  I read once about an institution that had a computer on the top of a mountain in the Rocky Mountains (IIRC). The modem dpeed was in low one-digit bytes per second so you were careful thinking about what you send.
crubier 2y ago
> Meanwhile a javascript app of mine from 2022 does not build now because I can’t get it to install the dependencies for some reason. Tired take... I promise that if your JS app ran in 2022 and you completely isolated the computer from the internet, your JS app would still run in 2067. This is completely unrelated. Also JS is probably one of the easiest language to repro, if you have a lockfile you're good to go.
- eknkc 2y ago
  Meh. I tried to npm install and run it. Npm failed with a cryptic error message. I have a built docker image of this so in any case, I can eventually fix it. Was not that important though. But then again, why the fuck does that fail now? I had a friend who was convinced that JPEGs would slowly degrade sitting on a disk. This was around 1990s so he would store important things in BMP so they would not degrade. I think node_modules has something similar.
  - deleted 2y ago
    [deleted]
  - actionfromafar 2y ago
    Your friend was sort of not entirely wrong. A JPEG decoder can do many decisions on how to decode, while a BMP is just pixels. (So then it's "only" a matter of color spaces.)
    - moron4hire 2y ago
      I haven't experienced this with JPEGs but wouldn't be surprised, as I have experienced it with MP3s. Newer decoders can't play some of my MP3s made with older encoders.
      - actionfromafar 2y ago
        Well, a compliant JPEGs will still open in any reader, but can look slightly different. In a low-resolution image, it could change some fine detail you really cared about.
theandrewbailey 2y ago
> Meanwhile a javascript app of mine from 2022 does not build now because I can’t get it to install the dependencies for some reason. I wager that Voyager 1 is way simpler than Node.js.
needaname 2y ago
How do people still not know how to use npm ci in 2024, then complain about their JS app 'breaking'.
- mgkimsal 2y ago
  because it's nothing something that ever surfaces in the first page of google when searching "how to use npm" and it's never discussed in any youtube videos or bootcamp programs. it's only ever something 'found' when dredging through stackoverflow when searching for error messages.
- j16sdiz 2y ago
  Older nodejs don't support newer TLS/SSL version.
2OEH8eoCRo0 2y ago
Nothing (most) software engineers do resembles engineering.
dominicrose 2y ago
comparing js to a spacecraft is like comparing junior-level PHP to top engineers using Rust

by eknkc 2y ago

Cthulhu_ 2y ago

Caveat, the output from your build (JS/HTML/whatever) will likely still work like it did today in 20 years time. JS isn't the problem, it's the overcomplicated dependency and build systems that were layered on top. It's why Go is a breath of fresh air. A 10 year old codebase will still build and run like it was made yesterday.

pants2 2y ago
Yes, just as my 10-yr-old old Java Applets and Flash games run perfectly... oh wait.

SteveNuts 2y ago

> Debugging on a 2 day feedback loop. Fuck that. This is what it's like for me, working with an offshore QA group.

blitzar 2y ago

Debugging on a 2 day feedback loop. Reminds me of working at the branch office with HQ on the opposite side of the world.

BrandoElFollito 2y ago
I read once about an institution that had a computer on the top of a mountain in the Rocky Mountains (IIRC). The modem dpeed was in low one-digit bytes per second so you were careful thinking about what you send.

crubier 2y ago

> Meanwhile a javascript app of mine from 2022 does not build now because I can’t get it to install the dependencies for some reason. Tired take... I promise that if your JS app ran in 2022 and you completely isolated the computer from the internet, your JS app would still run in 2067. This is completely unrelated. Also JS is probably one of the easiest language to repro, if you have a lockfile you're good to go.

eknkc 2y ago
Meh. I tried to npm install and run it. Npm failed with a cryptic error message. I have a built docker image of this so in any case, I can eventually fix it. Was not that important though. But then again, why the fuck does that fail now? I had a friend who was convinced that JPEGs would slowly degrade sitting on a disk. This was around 1990s so he would store important things in BMP so they would not degrade. I think node_modules has something similar.
- deleted 2y ago
  [deleted]
- actionfromafar 2y ago
  Your friend was sort of not entirely wrong. A JPEG decoder can do many decisions on how to decode, while a BMP is just pixels. (So then it's "only" a matter of color spaces.)
  - moron4hire 2y ago
    I haven't experienced this with JPEGs but wouldn't be surprised, as I have experienced it with MP3s. Newer decoders can't play some of my MP3s made with older encoders.
    - actionfromafar 2y ago
      Well, a compliant JPEGs will still open in any reader, but can look slightly different. In a low-resolution image, it could change some fine detail you really cared about.

theandrewbailey 2y ago

> Meanwhile a javascript app of mine from 2022 does not build now because I can’t get it to install the dependencies for some reason. I wager that Voyager 1 is way simpler than Node.js.

needaname 2y ago

How do people still not know how to use npm ci in 2024, then complain about their JS app 'breaking'.

mgkimsal 2y ago
because it's nothing something that ever surfaces in the first page of google when searching "how to use npm" and it's never discussed in any youtube videos or bootcamp programs. it's only ever something 'found' when dredging through stackoverflow when searching for error messages.
j16sdiz 2y ago
Older nodejs don't support newer TLS/SSL version.

2OEH8eoCRo0 2y ago

Nothing (most) software engineers do resembles engineering.

dominicrose 2y ago

comparing js to a spacecraft is like comparing junior-level PHP to top engineers using Rust