yay, my web hosting provider customer portal now suddenly works with SeaMonkey

...and refuses to login from vanilla Firefox. WTF.

...nevermind

the payment portal is on another webapp that does NOT work on SM

> SyntaxError: import declarations may only appear at top level of a module

> import{T as m,M as f,V as h,u as C,i as g,_ as o,p as b,c as w}from"./MainContentHeader-da3c99a6.js"

what the hell is this noise

since when JavaScript became Python?!

wtf is this obfuscated js nonsense. who can even read that shit?

nobody

it's a sad ongoing trend

you push a bunch of code that doesn't fit in a floppy, then there are probably things pointed as reasons to do this

be it taking less space, parsing faster

or, where is it

jwz.org/blog/2024/04/this-is-a-god-damned-war-crime cdn.jwz.org/images/2024/grab-20240404_115223.jpg

the reality is that obfuscated and minifed js make it much harder to support a site that uses that, at least with readable code people can see where is it failing and what needs to be done

I still think the world was nicer when most of this madness was also ECMAscript but as in ActionScript and the javascript for the browser was kept under check for MSIE6 compatibility

(but I guess I should name my JS variables _0xc0ffee?)

this is not a problem just with JS: many many years ago when I was trying this thing called Google+, one of the main problems was that they autogenerated it, so the CSS class names kept changing, you couldn't just have and keep CSS hacks

(On top of they ruining it more over time, one of the reasons why I stopped using it was probably it being resource-intensive. I guess Mastodon's web UI is the new Google+.)

(At least that one is more or less customizable, and has human-readable names. Sadly, they don't really care about compatibility and have broken things on at least two occasions. But to be fair the whole project would need to shift from the "let's mirror twitter" mindset, anyway...)

njsg, are they scared of people reverse engineering their shit and making addons like betterfacebook or socialfixer or whatever its called

in both cases of google+ and mastodon's web ui, probably not

google+ was probably just because of how it was generated, probably something resembling Google Web Toolkit where the final thing is autogenerated

there was surely a flaw in that the generation did not guarantee stable names, but it probably just happened to be that way because that's how the generation does it

same goes for mastodon in another way, they're just using bloated ways to do things, and they're more focused in "let's be like twitter"

there really isn't a worry about compatibility, they'll use incompatible syntax because it looks cleaner, but then the whole thing is a heavy monster that requires a lot of RAM and CPU. But it doesn't lock people out of Mastodon because it allows other clients. It's just that the official web-based client is a mess.

the thing is full of usability issues, and it doesn't even try to cater for tabbed browsing

buttons that don't look like actionable UI items at all, buttons that look like links but aren't (oh you wanted to open in a new tab!?)

(what's worse, I think (but I'd have to check) that some might actually react to middle click by replacing the current view, which is wonderful in a UI that goes with "endless scroll" instead of paginated views

)

Hello all

njsg: is there anyone here that understands in newsgroups using seamonkey

just mentioning, not concerned, but a page like, github.com/BtbN eats SeaMonkey CPU & presumably ever increasing Mem