Well yeah. If you want features that screws up user privacy, then its already bad to do it that way. Use js obfuacation and webassembly so thay you can hide the js running, make more and more of device info availiable to the websites you use so that they can have a tiny little featute at the cost of privacy, etc.
Not the particular web developer I had in mind, who prefers raw JS and resents having to use libraries, but sadly yeah far too common it's that, for basically no other reason than that - like, there's other ways to make "pretty" and "functional":-(. The web has truly enshittified, and I'm glad Firefox is still fighting against it.:-)
Well yeah. If you want features that screws up user privacy, then its already bad to do it that way. Use js obfuacation and webassembly so thay you can hide the js running, make more and more of device info availiable to the websites you use so that they can have a tiny little featute at the cost of privacy, etc.
Not the particular web developer I had in mind, who prefers raw JS and resents having to use libraries, but sadly yeah far too common it's that, for basically no other reason than that - like, there's other ways to make "pretty" and "functional":-(. The web has truly enshittified, and I'm glad Firefox is still fighting against it.:-)