The first two or three examples are really bad but the rest are quite good.

The description of the post said “complex yaml files”.

JSON is not easier for most strings. Anything multiline for example.

But yaml is a superset of JSON so you literally can use JSON and it’s still valid YAML.

They mention their company numerous times over, sure doesn’t seem like a personal blog. It seems like a company discovering something that has been documented over and over again.

I think it might be broken on mobile?

Article written like it’s someone that just discovered types even though a majority of the programming world said to use types for decades…

Also I completely disagree with the assertion that you should write everything including backend in typescript in order to share types. You should be using a schema and generating your types if you are writing large systems. That way any service that uses your APIs can generate the types as well and isn’t locked in to your language.

And please dear lord stop writing backend code in JavaScript or typescript or any scripting language.

Other than that, yes, use types. They literally do exactly what every proponent of types has said they do for years. Turns out it’s a huge benefit!

Everyone is biased, some less so. Use something like media bias checker or Ground News and read what they say the bias is and why.

I’m pretty sure that federally it’s mandated that you have to be able to mail it in.

None of the complexity of GitHub actions would be solved with any other configuration language. It needs to be a full scripting language at minimum. The problems with GHA have nothing to do with yaml.

You shouldn’t write complex yaml files. Keep it simple and yaml is great. Do complex stuff and you’ll hate your life.

I’ve had the invisible window issue, today for the first time, but not the other issues you’ve listed. iOS 18 on the other hand, holy fucking shit has it been a nightmare.

Awesome picture. I love the vibe