Pretty much anything you might ever wanna do with a website, can be done with IE8 support. Rest is skill issue.
this post was submitted on 15 Jul 2026
205 points (93.6% liked)
Programmer Humor
32424 readers
1100 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 3 years ago
MODERATORS
I don't believe, you should expect all browsers to implement all new web features in under a year. It takes time, like new C++ or C standarts. An like with all other standarts, the more parties are involved the more time it takes to adopt it.
Haha, one year? How quaint. (Cries into ISO C++ standards)
Just don't create such a mess that you need cutting-edge features.
Cutting-edge JS is for boring stuff anyway. We've gone from formalizing the best bits of jQuery to 'click thing to make box appear.' So you're only avoiding tutorial-ass boilerplate, and quite frankly, boo hoo.
Meanwhile CSS is still in the "Jesus Christ why wasn't it like this to begin with" phase of feature adoption.
As if modern websites care about Firefox
As if ~~modern~~ websites care about Firefox
We used to have HTML+ and be happy!
You can’t count chrome and edge as two different browsers…
MDN does, not my decision
They keep them grouped together though. If you look closely, they're in the same bubble while firefox is in another one. Probably shows both for the convenience of most devs.
(also Microsoft being Microsoft might shoehorn in some feature no other normal browser would just because)
It's actually Google doing that these days, but they do it on webkit directly and so everything but Firefox gets their experiments too.
Chromium (or blink), not webkit
load more comments
(2 replies)
they are grouped and as they are different browsers that theoretically could have different blink versions I feel like it makes sense.
load more comments
(1 replies)
You know what still works? HTML tables.
Suck it, all of the 2000s webdev.
What's worse than div soup? Table ware.
Even apple phones added flexbox support in like 2022.
Flexbox spam is the new tables.
load more comments
(3 replies)
...Did you add an unescaped RTL toggle character on your user name?
</span></div>
For the record, I noticed because I use Friendica:
Jeroba only flips the instance domain, that is way more wild
No issues in Thunder.
I have display names turned off, though.
It's probably in the display name, not the username so that would make sense. Would be interesting to know what happens if display names are on
Turns out it looks the same. Wait, something is still wrong. I turned the setting on, but I still don't see display names. Oh well.
Yay I am in screenshot
What's it like being famous? 🤩
Meh
📸
load more comments
(2 replies)
Funnily enough, it is correctly escaped in the client he developed, Photon
it actually isnt intentional that it works fine, it's some miracle of how i split the instance name and the username in markup. i was a little disappointed that nothing funny happened when i added that initially
Call me unsurprised if @Xylight added it as a way to test for rendering errors across Fediverse clients
load more comments
(1 replies)
load more comments
(1 replies)
i do remember doing that a long time ago
Doing QA testing for free? You and lil bobby tables would get along great
By the way, if you want to replicate this effect for fun and profit, the control character you're searching for is U+202E RIGHT-TO-LEFT OVERRIDE (or RLO for short)
I strongly think Lemmy clients should have a toggle to show usernames instead of display names. Some of the Unicode is super obnoxious.
Some Lemmy clients like summit do (which I keep on, because display names are often cancer)
load more comments
(3 replies)
Gradual adoption is fine. It's so much better than seeing StackOverflow answers from like 2013, and knowing not a goddamn one of them works anymore. It's massively better than having to write separate code for IE and Netscape.
Wait until you find out that people made and still make sites that load on both IE and Netscape.
load more comments
(1 replies)
There ought to be some kind of 2016 css subset that everyone sticks to and then we can reconsider maybe updating it to include any newer stuff that's absolutely essential once every ten years.
that mentality is one reason websites spam JavaScript today, because native features of the markup language were being added too slow
Expecting the runtime/browser to ship a native implementation of virtually everything you might want to do in a turing-complete language, is also really not sustainable, though.
load more comments
(1 replies)
Progressive enhancement is a cool thing
That's like wanting to use a just standardized media format.
Windows native support for MKV (2002) and HEVC (2013): 2019
view more: next ›