| Website | https://dafzthomas.com/ |
| GitHub | https://github.com/dafzthomas |
| Threads | https://www.threads.net/@dafzthomas |
| Website | https://dafzthomas.com/ |
| GitHub | https://github.com/dafzthomas |
| Threads | https://www.threads.net/@dafzthomas |
Only use 3rd party libraries if you couldn't write a solution in a reasonable amount of time.
And try and be biased towards the written solution.
I can't stand over-engineered projects. Almost impossible to work with.
Makes my brain switch off and want to throw it in the bin.
To serve users at the global P75 of devices and networks, we can now afford ~150KiB of HTML/CSS/fonts and ~300-350KiB of JavaScript (gzipped). This is a slight upgrade on last year's budgets, thanks to device and network improvements. Meanwhile, web developers continue to send more script than is reasonable for 80+% of the world's users, widening the gap between the haves and the have-nots. This is an ethical crisis for frontend. Meanwhile, the most popular tools and frameworks remain in stubborn denial, but reality is not moved by ignoring it: when digital is the default, slow is exclusionary.
Every news outlet should stand up a Mastondon instance for their reporters & staff.
It’ll be great to see [email protected] or whatever domain they want to use.
Built in verification. Every reporter for the Washington Post on a washpo domain. Every reporter for the New York Times on an NYTimes domain. Etc, etc.
Plus the “local” feed for each instance becomes a feed of all the posts from that institution mixed together — providing extra discovery.