Induane

You'll be able to stop the signal if they add cellular data. Still annoying though.

Arcan has a decent model for this.

Apparently still being hugged. Can't load a single image on a gigabit connection.

I think something about the node ecosystem makes it particularly vulnerable. Maybe it's the insane "dry" ethos. Or something else.

Nothing I have ever used has a comparable dependency tree nightmare.

Malware has started sprinkling references to nuclear shit and other strings that trigger model safety so they'll refuse to actually scan them.

There are a couple of things:

1. Locality of behavior - the classes are the description of the style once you know tailwind, and they live where the thing they're styling is. I can look at a template and know pretty well how it is going to look without having to go lookup a sites personal bespoke CSS and match what's written there to the markup.

2. It's the same classes as you move from project to project. I have tons of small one-off apps I maintain, all using tailwind and I don't have to figure out the custom CSS classes and their meanings. It is a knowledge set that reduces friction between projects and I really need things that reduce cognitive load like that.

3. No dead CSS. There are tools to help with this in regular CSS but I just don't have to think about it with tailwind and that's nice. I work on my templates and the CSS is updated and minifed on the fly without extra steps (or unnecessary CSS).

4. Easy to build a personal component library that doesn't also require relevant CSS to be bundles with it. For me this one is pretty great. Thanks to template engines (for me it's Django's, but Jinja or others are grand too) I have a simple place to pull components (really just template partials) and widgets I've made and they just work because the underlying classes are the same. There are some exceptions around color schemes and the like but now all my little components take a colour scheme arg and voila, no proballo.

I think the key here is that a description of the visual is embedded in the markup. That lets the actual mark-up delivered to the front-end describe pretty much the whole kit. With server-side rendering ( I use HTMX ) I can even write unittests that responses contain expected markup, including CSS classes (I built a few helper assertions that all of my test suites use) which gives me some interesting checks.

I really ultimately don't think there is one correct way to do things. The things I value may be utterly irrelevant to another developer.

This was an amazing read. The nature of the auther explains why I'm using Wayland instead of Arcan, but perhaps it isn't too late.

It's nice when I want to be lazy though.

Or when I'm working two contract gigs. I can spec things out for one and turn it loose and trust it. Then work more closely with deepseek on the other project.

Turn Claude loose I guess.

I don't know; I am not sure I'm marketable in THIS particular market.

As for FastAPI bring a mistake - that's an overgeneralisation to be sure. It has it's uses.

My first issue is that it falls into the same kind of small footprint as Flask. Every Flask project I work on slowly reinvents Django via a combination of plugins of varied quality and custom code/plugins. Get some Auth plugins, build step for manifest static files, add in Jinja2, grab an ORM like SQLAlchemy (or hopefully PeeWee), a migration system, test runners with fixtures/dB integration and rollback and on and on and on.

FastAPI is operating more at that level but also adds the often unnecessary complexity of async. In Python this is a cooperative setup meaning you have to yield to the event loop yourself (otherwise despite being "async" it blocks). Plus with a webapp all async often does is let you hammer your services (i.e. dispatch more queries to your poor DB) harder. The actual performance improvements don't manifest so much at scale as people often think. Plus you end up with a whole second set of ways to call functions and... makes me pine for gevent.

There are absolutely cases for this kind of async, even in webapps, but it's often not actually that helpful in places that it's used (and doesn't actually need to be everywhere). Good development imo means picking the right tool for the job rather than jumping on hype trains.

MongoDB is webscale!!

I have began to use AI to flesh out unittests and honestly am kind of digging that part. All the actual code is still me though.

I've been doing full-stack Dev (mostly Django though I foolishly had a brief moment where I kinda thought Flask was okay then fell for the same dumb thing briefly with FastAPI) for 20+ years and don't feel marketable.

I went from jQuery to a brief dalliance with Angular to HTMX+_HyperScript. Everyone wants full stack Devs to use react and struggle eternally with insane dependency trees and challenging client side state management.

I like to build things that can be maintained in perpetuity by small teams.

So I'm not very marketable.

It was a loaded question for sure. And when it comes to technical stuff it is often more subjective that people care to admit.

That's a whole ass Spartan letter.

That Fucking Asshole mummy from Bubba Ho Tep.

I actually find the opposite. I don't actually think either of us are wrong, it probably comes down to what we got started with. I love that in Gimp layers can have totally different canvas sizes, and I prefer it's foreground select tool.

But most of all, any comparison is going to be silly. Photoshop has lots of amazing features and in sure is better in a technical comparison to Gimp in many ways.

A lot of times the best tool for the job is the one that works great for you.

I removed collision detection so I could throw bananas through buildings

This is one of the real advantages to the (often insulted and/or chastised) vision only approach to FSD.

People can easily adapt to different vehicles in a similar manner.

Python has nothing on the sprawl of nodejs packages.

It is a fair criticism and some languages do fare better than others. Python is kind of in the middle there in my opinion. It's pretty easy to keep a relatively simple dependency graph with a little bit of discipline.

I believe that LLMs will eventually be a small component of AGI; most likely it'll function like the Broca's region of the brain.

I always love seeing pros and cons of whitelist vs blacklist sorts of strategies in different scenarios.

I've been copying/modifying the same nginx config file for like 15 years

Little tweak here, little tweak there...

Way overcomplicating design is one challenge that keeps getting worse.

Another gigantic unspoken issue is that people have started building tons of stuff with React on purpose for some reason.

You really need a large volume of repeated results by different groups doing the experiment/research so you get the proper regression to the mean. Individual papers are more important at saying "here is something interesting that others should also check out".

Except that four cans of soda is not much more than a single 44oz soda fountain drink at QT and folk gobble down those often 3 times a day.

I bet it wasn't actually the bootloader but something with autoexec.bat - you could setup choices in it and windows was just one launch option.

Relentless striving without any kind of real meaning isn't healthy. Even people who aren't deeply Christian in the religious sense are still inherited of much of the values. I.E. people must prove their value via an extraordinary work ethic.

Not entirely. An iPhone can be "located" with it's find-my-phone features even if powered off (on by default, I believe you can disable this feature). Even if you disable it, you are trusting that it isn't discoverable in some form.

The only way to be vaguely safe is to disable or not bring a cellphone with you, travel to and from places in some form of disguise, and to pay with cash.

I thought it was a joke but someone is serious.

This is one of the worst things I have ever heard of proposal wise.

The worst. I can't even. Literally.