-
Sompi_
Many websites have already stopped working on Firefox ESR because it is "too old"
-
franstam
how tf is firefox esr too old?
-
franstam
i dont get why those chromisms infected people keep chasing latest greatest like some dumba$$e$?
-
franstam
i want a stable non breaking browser
-
Sompi_
because they think that it must be unsecure because it is not new
-
Sompi_
nightly builds are secure, ESR releases are unsecure because they are old
-
franstam
my friend literally changed his mobile cos oneplus 7t is "no longer supported" with no security updates
-
franstam
what a n00b
-
franstam
i guess goggles loves him cos he bought a pixel 8
-
Sompi_
how people suddenly started accepting that kind of bullshit
-
Sompi_
I cannot afford buying new things all the time
-
Sompi_
my CPU is ten years old, but it is a Xeon and it has more calculating power than new cheap computers
-
Sompi_
but many new programs don't work anymore because they need newer instruction set extensions than I have
-
Sompi_
nowadays everything is compiled for max. 5 years old computers...
-
Saijin_Naib
It is a shame that ESR runs afoul of many critical websites. That was the main reason I had to drop SeaMonkey, despite loving using it for everything at once
-
Sompi_
The ESR version is always safer, but idiot thinks that it isn't because "iT Is OlD!!11"
-
franstam
fk that shiet
-
franstam
i recall previously that i could continue using firefox 2.0 when i refused to upgrade to 3.x way back, well into the 12.x version.
-
franstam
thats like literally 6 years
-
franstam
no sites mysteriously "broke"
-
franstam
how long stone tablets were in use for?
-
franstam
apparently even now thousands of years later people can still read some of them
-
njsg
Sompi_: we've finally solved the Microsoft antitrust scenario from the 90s, and the wintel monopoly. by normalizing it further?
-
njsg
what's fun, *again*, and yes, I keep getting back to this, is how part of why the web didn't break so much in the recent past (but not-so-recent past) was... MSIE6.
-
Sompi_
microsoft was moving slowly back then
-
njsg
also interesting how so many things could work better if breaking changes were done with versioning
-
» njsg looks at whatwg
-
Sompi_
now we have HTML5 which is a "running standard", things just change without the version number of the standard changing
-
njsg
"living standard", and yes, that's whatwg.
-
njsg
my prime example for that so far was the change in fetch() defaults
-
njsg
which broke login in at least one site I use, and I think also picture loading at some Lidl sites (at least .de? I don't recall whether other TLDs affected)
-
Sompi_
so if a webpage is "HTML5 compliant", no-one knows which year's and month's HTML5 it is
-
njsg
because whatwg decided it should now default to sending credentials, which is stupid, as the proper compatible way for developers would then have to be still explicitly set the same value as the default just in case
-
Sompi_
can standards without version management even be called standards...
-
njsg
I don't know if I want to know the answer to that question :-D
-
njsg
let's make c++ a living standard so that nobody knows whether side-effect-less infinite loops are undefined behaviour or not!
-
Sompi_
and then they say that HTML 4.01 is "obsolete"
-
Sompi_
and "you should not use it" (why?)
-
Sompi_
nowadays even software developers don't know what their CPU target is...
-
Sompi_
and then they "accidentally" push a software update that requires instruction set extensions that weren't required before
-
franstam
i wish m$ would make windows 10 evergreen
-
franstam
i could technically stay on windows 10 2015 build 10240 and be on "windows 10"
-
franstam
but m$ broke their promist
-
franstam
promise
-
franstam
lets just go back to plain old html
-
franstam
-
franstam
this is an issue
-
franstam
i cant be bothered to keep up to date with my android mobile that people just deprecate just because someones pocket is not enough profits
-
njsg
one of the issues is probably that some of the ideas in use today don't really help with old devices
-
njsg
if instead of JS-powered lazy-loading, we had something that didn't require JS, maybe that'd be one step in the right direction
-
njsg
but, overall, the problem continues to be basing things on top of piles and piles of JS with no consideration for speed, load time and graceful degradation
-
njsg
at one point, I could get something decent out of an android phone by disabling JS and CSS in a browser: things just loaded instantly. This was, of course, before it became more prevalent to require JS or newer SSL algorithms
-
njsg
but it illustrates how much slowness the bloat adds
-
franstam
lazy devs. nuff said
-
franstam
hope im not offending any web devs here
-
franstam
ooops