lmorchard · HackerTrans

há 11 diasdiscuss

The Firefox repo gets 100-300 changesets per day, up to 1000 commits per week. Around 100-150 contributors land those in any given week. That's activity comparable to Linux or Chromium. And, the release schedule is accelerating from a four-week cadence to a two-week cadence this fall.

Just because other efforts and initiatives are flasher or noisier doesn't mean Firefox isn't the main priority.

lmorchard

há 11 diasdiscuss

Yeah, this is a real thing: Mozilla doesn't have a team dedicated optimizing Gecko-based Firefox for iOS just in case it can be shipped someday. That Firefox can be built and will run on iOS doesn't mean it will immediately be a great browser there - there are some things you just don't know to optimize until you've gotten the thing into a lot of users' hands over a decent span of time.

lmorchard

há 11 diasdiscuss

> I'd say Mozilla should take the money they're spending on their current nonsense and spend it here instead.

Mozilla makes roughly $500m per year with maybe $1.5b in the bank. That's about 1-2 orders of magnitude short of what would be required to poke Apple in the eye and make them feel it.

lmorchard

mês passadodiscuss

Why lol? If you only want to scale to a few dozen or a few hundred or even a few thousand folks, a Mastodon instance is fine. You don't have to scale to the whole world.

lmorchard

mês passadodiscuss

Scaling is not useful if that's not your goal

lmorchard

mês passadodiscuss

I'm interested in ATProto, but honestly this kind of "cheeky" post just turns me off. These are different approaches to the problem, they don't have to be adversarial.

Another way to look at it: the Twitter-brained perspective is that it's a good thing to build a system where everyone has access to everyone else all of the time - that the global firehose is a primary goal.

That notion is not universally agreed upon as desirable. Some folks and groups of folks value membranes with varying degrees of permeability.

With Mastodon, each instance is a self-contained community server with the option to link up with peers of similar shape. That this arrangement makes a whole-world view difficult is seen as a feature-not-bug by many users.

Also, since each instance is a self-contained complete unit of microblogging-shaped community, that means a relatively small technical team can host & maintain that unit for a decent-sized group of folks with relatively cheap cost.

Put a bunch of those together in federation, and you have a chance at a pretty well-distributed spread of moderators and caretakers. Depending on how any particular instance's funding and governance is setup, that can also result in members being more or less involved in the running of the place. (Which, also, is why some folks value being "belonging" to a particular instance.)

In ATProto, the "instance" is the complete stack you'd need to have ownership over the whole shebang. Some folks and communities value that. Versus Mastodon, Bluesky is just a much much bigger box.

You can also separate Mastodon from ActivityPub. You can make new apps atop ActivityPub - and folks are. Photos, videos, calendars, etc. It's based on JSON Linked Data, and that's expandable to other types of activities and data. If you really wanted to, you could make a great big all-encompassing app UX that handles everything. But, I guess no one's found that interesting enough for it to take off yet.

lmorchard

mês passadodiscuss

And then once you've self-hosted ever component in the stack, you have one (1) Mastodon instance equivalent :)

lmorchard

há 4 mesesdiscuss

Meanwhile, Undertale, one of the most celebrated video games, famously has a 1000+ line switch statement and AI had nothing to do with it. Sometimes you have to bang out something that works, just to even get the chance to be annoyed at how bad it is for next version.

lmorchard

há 4 mesesdiscuss

No, but it's increasingly penalizing folks for focusing on well-crafted code on company time.

lmorchard

há 5 mesesdiscuss

My comments are often more off-the-cuff than my blog posts—I spend more time editing the posts, usually

lmorchard

há 5 mesesdiscuss

As I'm asking folks what bits they think are LLM imprints, they keep showing me bits that I originally wrote. It's really weird.

lmorchard

há 5 mesesdiscuss

I mean, the irony is that those sentences were in my original draft before running it past the LLM

lmorchard

há 5 mesesdiscuss

> The web was objectively awful as a technology

I, for one, remember when I could crash Netscape Navigator by using CSS too hard (i.e. at all) or trying to make a thing move 10px with DHTML. But I kept trying to make browser to thing.

lmorchard

há 5 mesesdiscuss

I guess I have a grating LLM-voice, then, because I don't think it sounds particularly different than how I've written other posts.

lmorchard

há 5 mesesdiscuss

Which bits? And don't say the em-dashes because I've been over-using them since high school

lmorchard

há 5 mesesdiscuss

Sure, I ran the post past an LLM for some ideas on clarity and tightening it up - but I wrote, edited, and published it myself.

lmorchard

há 5 mesesdiscuss

Well, yeah, that's what a lot of folks are sad about - they can't practice the craft concurrently with the livelihood quite as much. But if you don't have a livelihood, you probably don't have as much space for craft at all.

lmorchard

há 7 mesesdiscuss

Yeah, this is a lot of what I'm doing with LLM code generation these days: I've been there, I've done that, I vaguely know what the right code would look like when I see it. Rather than spend 30-60 minutes refreshing myself to swap the context back into my head, I prompt Claude to generate a thing that I know can be done.

Much of the time, it generates basically what I would have written, but faster. Sometimes, better, because it has no concept of boredom or impatience while it produces exhaustive tests or fixes style problems. I review, test, demand refinements, and tweak a few things myself. By the end, I have a working thing and I've gotten a refresher on things anyway.

lmorchard

há 7 mesesdiscuss

What you consider fun isn't universal. Some folks don't want to just tinker for half an hour, some folks enjoy getting a particular result that meets specific goals. Some folks don't find the mechanics of putting lines of code together as fun as what the code does when it runs. That might sound like paid work to you, but it can be gratifying for not-you.

lmorchard

há 7 mesesdiscuss

Like, fine, here's a personal example: I wanted to build a system that posts web links I share to a bot account on the fediverse. That seemed like a fun result to me.

I wanted to self-host the links, so I installed Linkding. (I didn't write Linkding.) For the fediverse bot, I installed gotosocial as the service host (I didn't write gotosocial.)

From there, a cronjob running a small program using Linkding and gotosocial APIs could do the trick. Decided to do it in golang, because the standalone binaries are easy to deploy.

Writing that small program didn't seem like fun - I've already played with those APIs and golang. What I wanted, for my enjoyment, was the completed system.

So, I took 10 minutes to write out a quick spec for the program and what I wanted it to do. I loaded that up as context for Claude Code along with some pointers for building CLI apps in golang. I let it rip and, in about 20 minutes, Claude produced a functional tool. It also wrote a decent README based on my original prose.

I reviewed the code, did some testing, made some tweaks, called it done. My bookmarks are now regularly posted to a bot account on the fediverse. This is an enjoyable outcome for me - and I didn't have to type every line of code myself.

For bonus points, I also had Claude Code gin up some GitHub Actions workflows to lint, test, build, and release multi-platform binaries for this tool. I've done these things before, but they're tedious. More enjoyable to have the resulting automations than to build them. And now I have them: I can make tweaks to this tool and get builds just through the GitHub web UI.

I've since repeated this pattern with a handful of other small personal tools. In each case, I wanted the tool and the utility it offered. I didn't care about the process of writing the code. It's working pretty well for me.