They appear to be “coming soon”. While I’m sure there’s a lot of interesting stuff they say, I too hope that the exclusively male and white selection of lecturers (and presumably philosophies!) is an artefact of how young the site is.
Just had a quick look but I like the look so far. I’ve been thinking along similar lines for ages but never quite got around to making something. I very much support any effort to make remoting less dependent on the archaic character grid.
I don’t think dismissing direct democracy as “fucking stupid” is the kind of constructive commentary this site is after. It’s a complex issue and I wouldn’t advocate for it claiming it would fix everything, but in the representative democracy that we (supposedly) have, and the representatives that we tend to get, often cowed or corrupted by huge corporate interests, is it surprising that people want to take some influence back into their own hands? I’m not ever going to be against that kind of democracy.
Sorry, no, but I’ve been using the latest DeepSeek model for personal stuff and it’s pretty good, way cheaper, and can be used in Claude Code directly.
I hope it’s an improvement on their current PR review code scanning, which alerts on code that only looks possibly vulnerable in isolation, without looking at the context. I guess I assumed it was an LLM being extremely lazy, but maybe it’s just static analysis. Anyway it’s pretty annoying.
Only? It was half your comment. The point is that the amount of "real use" (I think we can all guess at a good-enough definition) of a phone without WhatsApp in a country where it's pervasive is not enough for most people. And what do you mean by "maps exist"? Paper maps?
We're talking about governmental document-like websites with relatively simple forms here, not your particular legacy web app, there is no excuse for not getting them right. Gov.UK did. Plain HTML, used in a straight-forward way that is very clear from the approachable documentation on, say, MDN, is already responsive, readily consumable by screen readers, and works with any backend that already exists. If you have to fix a mess left by someone else you have my sympathy - I've been there too. But the original post is appealing to people who have a choice between plain, standard-use HTML, and any alternatives. And yes, I'm all for much harsher penalties for private companies that produce inaccessible web sites/apps too.
The point of a UI library is to interface with users. If it totally fails to interface with a subset of users then it is obviously deficient to some degree. It is callous and foolish to dismiss offhand users who rely on assistive technologies. You probably have a poor idea of who they are and how many people we’re talking about. You never know when you or someone you care about will become one of them, even temporarily. You never know how far your software will reach when you write it.
Sorry, I don’t buy it. There’s nothing “expert-tier” about plain accessible HTML, and with LLMs, there’s even less excuse. I’m not primarily a frontend web engineer and I can manage it.
My point is that websites are particularly amenable to being cheaply built in a fast and accessible way. I would say classes of, say, macOS apps are similar. Government certainly should be insulated from at least the market pressures that push websites into being slow and inaccessible. Competence is more a roll of the dice, I’ll grant you, but I’m not as pessimistic as you on that.