Xusontha@ls.buckodr.ink to Programmer Humor@programming.dev · 1 year agoMy poor RAM...loot.buckodr.inkimagemessage-square9fedilinkarrow-up19arrow-down10file-textcross-posted to: programmerhumor@lemmy.ml
arrow-up19arrow-down1imageMy poor RAM...loot.buckodr.inkXusontha@ls.buckodr.ink to Programmer Humor@programming.dev · 1 year agomessage-square9fedilinkfile-textcross-posted to: programmerhumor@lemmy.ml
minus-squareasyncrosaurus@programming.devlinkfedilinkarrow-up1·1 year agoWeb & mobile development took a wrong tern 10 million miles back, and no one wants to turn the car around and admit it.
minus-squareBipta@kbin.sociallinkfedilinkarrow-up1·1 year agoIt took a wrong turn in the 90s. There’s been no real feasible way to fix it without breaking the web for many decades now. Some things are just forever despite their problems, like QWERTY.
minus-squareThrowaway@lemm.eelinkfedilinkarrow-up1·1 year agoHalf the problem is that js was made over a weekend and we cant seem to come up with a different solution.
minus-squareFal@yiffit.netlinkfedilinkEnglisharrow-up1arrow-down1·1 year agohttps://htmx.org/ I’m working on a little project to try this out.
Web & mobile development took a wrong tern 10 million miles back, and no one wants to turn the car around and admit it.
It took a wrong turn in the 90s. There’s been no real feasible way to fix it without breaking the web for many decades now. Some things are just forever despite their problems, like QWERTY.
So let’s break the dang web
Half the problem is that js was made over a weekend and we cant seem to come up with a different solution.
https://htmx.org/
I’m working on a little project to try this out.