Personally, I (guiltily) love using ol'fashioned contractions. I wish it were more normalised.

Running smaller 4B-7B models entirely on the GPU VRAM will get you fast inference, but you will need to scope and define the tasks well. eg, using it the model as a classifier and just feeding it from a queue.

The best performing "agent"-like model to plug into a harness that I have found so far has been Qwen3.6-35B-A3B (mixture of experts) model as I can park most of it in system RAM and CPU, while the VRAM holds the attention/shared weights.

It's definitely workable as a local AI homelab. But expect homelab levels of tuning/fiddling with it.

With the improved support for AMD GPUs I'm finally considering getting a modern 16GB card (and maybe a second one in a few years assuming prices come down)

Google likes to make up its own "standards" and push them out on chrome, but Safari tends to be the late-comer to supporting impactful standards, not Firefox.

Do you have a particular use-case where Firefox's lack of support blocks you?

I think this meme has almost run its course.

Funnily enough I just had to fix a Safari layout quirk yesterday (for iOS 16 & 17 devices only). I was excited to pick it up because it had been _so long_ since I had to deal with a CSS-related browser incompatibility. I was nostalgic :')

I raced Claude to fix it. I knew which CSS had the issue, but I needed to set up an iOS simulator to verify my fix. So I had to download xcode, which download 10GB of data for a current simulator and Apple's embedded code-assist model. Then another 8GB for the iOS 16 simulator.

Claude took about 5min to find the right CSS file and then got stuck at the same point as me: needing to simulate it to verify. It just got the old webkit binaries and hacked together its own minimal browserstack clone.

It finished before me because of those downloads, but it only found half the fix. So... I won!

Except...I made a typo (`no-wrap` instead of `nowrap`) and had to do a fixup commit.

So I guess we'll call it a draw :(

The era of VC-funded home-delivery recipe boxes is still my favourite.

I suspect this is the only use-case I would consider...and I don't really have a use-case for "creative writing" that I would delegate to an LLM. I suppose for dialogue generation in games?

But yes, hard agree. Why on Earth would you ever want to write code with a model that is supposedly "jailbroken"? So it can put great backdoors into everything it touches? Pass.

Off-topic, but I stumbled upon the first Newcomen engine imported into Australia in a museum in Sydney and I was unexpectedly charmed (not an Engine Guy). It's large, but nothing like the awe of "mega-engineering", it's crude, but it clearly has such amazing utility (when compared to a reality without it) and it changed the world

Banning CFCs perhaps?

If you want to go older and more localised you could look at forestry and fisheries laws. Sometimes we self-regulate and form a stable state, other times we over-extract until collapse

Because the correct response to that query is "I have no idea -- you will need to provide more information"

and LLM Agents suck at that.

Sounds like you should start listening to some community radio stations. They don't even have to be your local community, I promise that somewhere in your timezone there is a community radio station broadcasting something you want to listen to.

Try our local one in Brisbane (where Bluey is from) that has been running since 1975 and started as a university student protest station: https://4zzz.org.au

You might not like the show you hear when you click, but look at their catalogue of shows and you'll find something.

Community can always be rebuilt.

Do they need 1000 frontend developers?

Aside from the Giants maybe some consultancies or hire-firms have that many? But they use whatever the client uses. If you're not in the business of selling frontend development services then a big part of your competitive advantage is _being able_ to make technology choices that are more-optimal than the labor market's lowest-common-denominator slurry.

Between JS/ECMAscript being abandonware for a decade and CSS' historical immaturity (cross-browser layout, custom properties, more pseudoclasses, etc) the Web was more of a wild west "whatever you we can cobble together" place. So of course we built an entire toolchain ecosystem for all the cool new tools we would reinvent from scratch.

but Things Are Pretty Good these days. We even have the world's only fully system portable assembly language: WASM! And the browser's Web APIs are becoming something like the missing Standard Library (shoutout to Deno).

The author's point seems to be that we are past a tipping point where we need all that additional complexity. You don't _need_ a separate system of reactivity these days, you can write a (closer to pre-hooks React, even!) React-style component library with Web Components now.

Personally I would need for Type Annotations to be a fully supported part of the spec before I made the point to "use the platform" professionally. Until some market force causes the core web technologies to truly fork my skills are useful for life. It's like a pale shadow of how UNIX users must feel :')

Which is why dieting and quitting smoking are famously easy things to do! ;)

There's something to be said for the "scrappyness" of resource limitations inflicted upon you when solving some problem. A sense of Triumph against the Universe itself is a nice pay-off

We've adapted: - our CI and git hooks so that our dependency or .lock files are visible when they change, and error if they change inconsistently - and our team procedures to confine dependency updates to dedicated commits

The idea being that when you see one of those "messy" .lock file changes...you were expecting it. If you see one and are annoyed by it (like OP) that's actually a waving red flag that a dependency changed.

Just to nitpick (because what else is this thread about? :))

They aren't equivalent! Tabs carry more semantic information than spaces. 1 Tab character == 1 Level of nesting

Space-based systems _can_ provide the equivalent semantic information if they are 100% consistent.

...but part of the argument in favor of spaces is that they allow an escape hatch of the strict indentation in order to allow pleasing visual alignments.

People lamented semver not being trustable but that ship sailed a long time ago, and supply chain attacks are going to get worse before they get better.

Our team is pretty minimal when it comes to enforced hooks (everyone has their own workflow) but no one could come up with an objection to this one.