@p

@TradeMinister



> It is predictable, but it feels sub-optimal a lot of the time. It lacks a lot of the flexibility and power you get from the Perl/Python/Ruby/etc. family that was more Lisp-inspired and heavy on the string/array manipulation.

You *may* be talking about PHP, not sure. It did what I wanted, anyway.

I used Perl too, but it always seemed somehow sloppier, easier to wander down strange dark paths. But then tbh I never did much like Lisp, either. I guess C ruined me for anything other than lineal descendents.

> Ah, yeah, it gets over-used a lot and every damn browser leaks memory from it. (I proposed at a previous employer that we just port Tk and draw to a <canvas> element.) And it was, of course, relentlessly exploited, including by people whose names are on the spec, as an attack vector for people to get your computer to do things you'd rather it not do, as with any means of just running untrusted code by clicking.

The 'advancing' html spec seems almost as if was designed by Big Tech companies staffed substantially by 'ex'-intelligence officers to make it easy to monitor everything one does, while stealing one's data. But that would never happen.

Still, having to refresh a whole page instead of just the relevant part was ugly.

> I might be too cynical, but I wish they'd just ship a bytecode VM and be done with it.
But not Java.