2026-11-11 16:26 UTC
Replies (17)
-
@Jakylla@jlai.lu 2026-11-11 16:42
Satan is taking notes…
-
@Enkrod@feddit.org 2026-11-11 16:59
condition() is undefined, should be ifCondition()
-
@Sanctus@anarchist.nexus 2026-11-11 16:59
Yeah I write clean readable code, how could you tell?
-
@gegil@sopuli.xyz 2026-11-11 17:05
There wouldnt be a ram crisis if nobody needed a 32 gigs of ram in their pc just to run a “hello world” web app.
-
@flango@lemmy.eco.br 2026-11-11 17:07
standard Javascript experience
-
@panda_abyss@lemmy.ca 2026-11-11 17:28
And this, js becomes lisp.
-
@bitjunkie@lemmy.world 2026-11-11 17:48
Clearly written by some smug [insert language here] dev… Nobody actually working in the JS/TS ecosystem is using var in 2026.
-
@xangadix@lemmy.world 2026-11-11 20:24
Is this functional programming?
-
@Sandbox@lemmy.zip 2026-11-12 02:55
Coding noob here. What am I looking at? I want to laugh too. :(
-
@cows_are_underrated@feddit.org 2026-11-12 12:28
The amount of closing braces in line 23 triggers my Lisp PTSD…
-
@eah@programming.dev 2026-11-12 13:29
Oh, I’d recognize those parenthesis anywhere. Any sufficiently complicated javascript program contains an ad hoc, informally-specified, bug-ridden, supply-chain-vulnerable, slow implementation of half of Common Lisp.
-
@onlinepersona@programming.dev 2026-11-12 17:14
Also known as functional programming.
-
@Jankatarch@lemmy.world 2026-11-12 17:39
“lisp with for-loops can’t hurt you” the therapist said…
-
@anon_8675309@lemmy.world 2026-11-12 18:25
Front end devs trying their best to out shit enterprise devs.
-
@generic_computers@lemmy.zip 2026-11-12 18:44
var and require()? What is this? Come over to modern JavaScript or even Typescript, it’s nice here.
-
@brianpeiris@lemmy.ca 2026-11-12 18:59
Poison the AI with this.
-
@anewfox@lemmy.zip 2026-11-12 20:15
you know, you could make node itself an npm dep if you wanted, so you could require a newer version of node from an older version of node. but then i dunno what you’d do besides invoke it from your node_modules directory. maybe just try it on a private npm registry instead of the public one, lol