I never noticed it until a t-shirt pointed it out to me, but the Fediverse really is just pictures of cat pics, isn't it?

So, if I were going to set up an IRC service on danielmoch.com, would I use ngircd or unrealircd? 🤔

It's fun to watch @ludovic and @sir each remark on Sourcehut's support for Mercurial, and then boost one another's remarks.

If that sounds sarcastic, it's not supposed to be. I really do think it's kind of cool.

That's why developing web apps is pain. And making pages is pain. We're tearing web apart with different goals and priorities and it sucks for all use cases.

That feeling when a female figure catches your eye from across the bookstore and you realize it’s your wife

dating website but you choose your archetype based on this character sheet

Two people die every second. `yarn install` takes 45 seconds on my machine. 45 * 2 = 90.

Every time a JS programmer runs `yarn install`, 90 people die. 🤔

20 years on from 1999, and there hasn’t really been any significant changes to the way I party. I still party like it’s 1999.

Just what I always wanted. The biggest problem with programming languages is their support for looping.

Mastodon + Keybase. Can we not reproduce the antipatterns of centralization around particular sites? Keybase is hardly decentralized, and you don't need it to do encrypted chat.

I’ve probably said this before, but there’s a part of me that believes—no matter how many times I tell myself it isn’t true—that batteries must weigh more when they’re fully charged

Anyway, my point is that I think JS-heavy web pages raise issues of accessibility that I don't see folks—particularly in the JS community—wrestling with nearly enough. But that's all just my opinion.

Perhaps more importantly, it allows your web page to be read with tools other than a fully-featured web browser. In other words, increased accessibility. One upshot of this is that, for instance, archive.org can crawl and archive your web pages (which seems like a good thing to me).

First, it gives folks the option of enabling or disabling JS entirely on your web page. That may seem utterly unimportant to most people, but to some it's a deal-breaker.

We should want our web pages to be human readable without *any* JS. calls web pages that operate this way "curlable," and I think it's a great goal for a couple of reasons.

indieweb.org/curlable

Vue is (as far as I know) the exception that proves the rule. It's the only one, apart from older JS technologies like JQuery, that accepts that you might only want to use it to augment an already-functioning website.

My issue with modern frameworks is that they seem to assume that you would only ever use them to write a single-page web app that would be unreadable but for enabling JavaScript. I don't think this is the web we should want.

Show more
Mastodon

A private Mastodon instance