Conversation

Notices

1. Node (node@furry.engineer)'s status on Thursday, 30-Mar-2023 21:01:47 JST Node

   thanks, i hate it

   • Disinformation Purveyor :verified_think: (thatguyoverthere@shitposter.club)'s status on Thursday, 30-Mar-2023 21:01:45 JST Disinformation Purveyor :verified_think:

     in reply to

     • errante
     • brea
     @errante @node @driftwood I think JavaScript is a decent language. My main gripe is the way it's used in browsers is often exploitative (fingerprinting etc), but the language is actually quite capable and doesn't add a ton of performance overhead in spite of being an interpreted language.
     
     I recently created a shitty prime sieve in c, js, perl, python, and then for absolutely no reason bash. The c was able to find 10k primes in 0.75 seconds on my laptop and JavaScript took 1.2 while python and perl were closer to 20 seconds. I didn't try 10k primes with bash because 100 primes took 20 seconds lol.
     
     Point is that despite the fact that I browse the internet with JavaScript disabled by default, I think it's a pretty capable language with a low barrier of entry.
   • brea (driftwood@rot.gives)'s status on Thursday, 30-Mar-2023 21:01:46 JST brea

     in reply to
     @node i mean how often are you going to have to check most of these equalities? and in a lot of cases something like typeof will serve you better anyways
   • errante (errante@rot.gives)'s status on Thursday, 30-Mar-2023 21:01:46 JST errante

     in reply to

     • brea
     @driftwood @node brea is defending javascript... shes taken the pill... its over
   • Disinformation Purveyor :verified_think: (thatguyoverthere@shitposter.club)'s status on Thursday, 30-Mar-2023 21:17:59 JST Disinformation Purveyor :verified_think:

     in reply to

     • errante
     • brea
     @driftwood @node @errante yeah I mean a bloated js frontend can definitely make a website less responsive, but the language is definitely not the weak kneed js of yore.
     
     I do think npmjs should die in a fire. I think the culture of going to npm and finding a module to solve every problem instead of solving it yourself leads to more bloated (and vulnerable) code. It sucks because now you might find one really useful module, and when you go to use it find out it has 97 dependencies and 29 of them have 5 year old critical CVEs and haven't been touched in 7 years.
     
     Luckily modern node (16+) has so much of the critical stuff built in (crypto, fs, dns, cluster, etc) that doing more complex things using pure javascript without a ton of dependencies is a lot easier to accomplish).
   • brea (driftwood@rot.gives)'s status on Thursday, 30-Mar-2023 21:18:00 JST brea

     in reply to

     • Disinformation Purveyor :verified_think:
     • errante
     @thatguyoverthere @node @errante JS slow haha is mostly a meme these days anyways, what with all the work the V8 engine does
     
     people who complain about it being used everywhere don't code in it anyways - the more they work elsewhere the more they actively undermine that paradigm
   • brea (driftwood@rot.gives)'s status on Thursday, 30-Mar-2023 21:25:18 JST brea

     in reply to

     • Disinformation Purveyor :verified_think:
     • errante
     @thatguyoverthere @node @errante oh 100%
     
     i really really hate npm, and i most of all hate working with people whose first impulse is to librarise shit
     Disinformation Purveyor :verified_think: likes this.
   • brea (driftwood@rot.gives)'s status on Thursday, 30-Mar-2023 21:27:08 JST brea

     in reply to

     • Disinformation Purveyor :verified_think:
     • errante
     • brea
     @thatguyoverthere @errante @node i also don't understand what aversion people have to imperative declaration that leads them to use a framework for the most minor shit when you could just use vanilla js
     
     i think people just don't wanna learn webpacks
     Disinformation Purveyor :verified_think: likes this.