A while ago I was looking at the Element properties that reflect to attributes (title, role, tabindex, etc.) and which ones remove the attribute when you set it to null or undefined, and whether the default value is null or the empty string or 0 or something else, and I came away reflecting that you could really drive yourself nuts with all this stuff
The worst part of building a JavaScript framework is that you really gotta sweat the details:
- some tags are self-closing (<input>), others are not (<div>) - SVG is case sensitive, HTML is not - `! important` is valid CSS (yes with the whitespace)
I feel like I discover some weird thing every other week.
This is from an iOS developer, but as an Android developer, I came to basically the same conclusion 10 years ago. The web isn't perfect, but it's a near-universal platform not owned by anybody.
Entertaining and slightly horrifying talk about how buggy HTTP resource priorities are across browsers, servers, HTTP versions… My takeaway is that I will probably just defer to the experts on this stuff instead of trying to go mucking around in the priorities myself.
The WebKit team has been doing amazing work recently, but it doesn't help users stuck on old versions of the OS.
E.g. Safari 16.4 was a massive release from back in March, but about a third of Safari users are still on <=16.3. This accounts for 6.5% of *all* browsers! https://caniuse.com/mdn-api_elementinternals
I know the solution is "just buy a new iPhone," but how much e-waste is that going to generate? And how many people can afford it?
@alex I gave it a shot, I really did. But the whole "let me handle all your module loading and script transformation and also simulate a whole browser for you, but slowly" just drives me nuts
One weird (possible) downstream impact of the recent chaos at Twitter: I notice that Twemoji is still stuck on Emoji v14, and the contributor graph shows no significant updates since 2022.
If you use Firefox, this means you can't see the shaking face emoji (🫨), or you see the version provided by the OS/website instead of the one built in to Firefox.
It looks like there is a fork, but I wonder what Mozilla or other apps/websites that depend on Twemoji will do. Go with the fork? Switch to OpenMoji? (Which is also only on v14 it seems.)
Emoji are (ostensibly) a commons overseen by the Unicode Consortium; it seems weird that so many took a dependency on Twemoji, which may now be backfiring.
In related news, emoji-picker-element is now updated to Emoji v15, and I am just now noticing some weird things like how Apple's "saluting face" (🫡) is only half a face for some reason
I'm sure some people would think this is incredibly stupid, but to me the passion and dedication here is amazing. It's like finding the perfect way to fold 1,000 paper cranes or something.
It's also fascinating to watch as a programmer, to see how "integer overflow" could become "parallel universes." ?
The server is back up to running at full capacity. If you see any more load issues, please let me know.
Unfortunately, some folks who migrated away from toot.cafe when the server was swamped have reported some problems: missing followers, wrong followers. I can only assume that Mastodon dropped some of the Sidekiq jobs because of the massive load. I'm not aware of any way to solve this problem. I'm really sorry about that. ?
Also: thank you very much for the $128/month on Patreon! I really don't think we need that much, though; the current forecasted costs are $55, and I don't see a need to beef up the server any more. Please feel free to downgrade your donation to $1. https://www.patreon.com/user?u=5535137