mikl

Same here. Reproducible configuration is amazing. Even a moderately complex app like Forgejo is easy to set a Nix module up for, with all the needed nginx/database/backup/etc. config nailed down and easily transferable to another machine if need be.

Same article in German, if that’s more your thing: https://www.srf.ch/news/dialog/autonomes-fahren-wie-tesla-un...

> I took action as the primary on-call engineer to lock down the AWS account and prevent any actions by possible attackers.

So he suspected an attack, but did not contact his employer about it or other team members. No action taken to mitigate the attack or to identify what was going on. Just changed the AWS root account password and nothing else.

Even assuming the very best intentions, I don’t think it unreasonable that Ruby Central found that a little bit suspicious.

I don’t really think pedantry about terms changes the overall point.

Great Britain is the big island next to Ireland. So the Scots, Welsh and English are British.

Most Irish people would not take kindly to be called British, but then there’s Northern Ireland with all its complexities.

They can just fork Rails right now, no need for dramatic open letters.

As for trying to unseat the Rails founder and BDFL, no chance.

Maybe I’m just not the target audience, but looking at the front page, I don’t see what actual problems this solves. The claims sound nice, but without examples of what they mean in real world use, it’s not really compelling.

You can't do anything like Omarchy with macOS. Everything is locked down tight, no customization or tweaking allowed.

Lots of developers are tired of being hemmed in and disrespected by Apple. Omarchy gets us back into using an OS made for developers, by developers.

This exceedingly uninformed rant makes more sense when you understand that the author has his own timestamp format he wants to push.

Counterpoints:

- UUID is not random characters, it's a 128 bit number and is stored as such in many databases. It can be presented as a hex-string with dash-separators, but it doesn't have to be.

- There are several types of UUIDs. UUIDv4 is mostly just random bits. Others have time and machine numbering, like Snowflake IDs. UUIDv7 has a combination of time and randomness.

- UUIDv7 was made to address the database index problem, rendering that point moot.

Lots of tools understand and/or support UUIDs.

You can complain about the overhead of storing and indexing 128 bit numbers if you want, but realize that a string like 2025_P5U5_326662 is likely also going to be stored as 128 bits. And the added value of having the year in front (the rest is not going to mean anything to the average user) is not that great.

There’s also a more community-driven/open source fork of Gitea, called Forgejo: https://forgejo.org/

How relevant is this now, if you have a modern server that supports HTTP/3?

HTTP/3 uses UDP rather than TCP, so TCP slow start should not apply at all.

Will be interesting to see if they can make it stick. Everyone is used to Windows + Office, so there’ll be a lot of resistance to trying something else, and if their IT department is not ready for it, it can quickly become a shit-show.

That’s the nice thing about Open Source. Nothing’s stopping you from organizing this yourself.

Everyone likes their mother tongue better, so does Mark Twain. No need to write a whole treatise about it.

Having lived 10+ years in Switzerland and having learned the language (and the local dialects), I really like German. But like many delicacies, it is an acquired taste.

One might hope it’ll cause Tesla to drop the price for their “full” self-driving too. $8'000 for a software feature is just bonkers. Especially in Europe, where there’s no subscription option, so you can’t even try it without paying the full price first, and many of the fancier features are not supported here. Even regular auto-pilot is not very reliable for me, it often fails to recognize city limits signs, and fairly often panic brakes because it misinterprets cars driving on the other side of the road as being on collision course.

So would all the other western automakers. The lower wage- and energy costs in China would strangle them all.

Hindenburg goes down in flames?

You can say that, but on the power flow maps, it was quite clear. At the same time we were paying ~$1.5 USD for 1 kWh, we were exporting power to Germany (and other energy-unstable countries like Italy). Sure, better energy links inside Sweden could have helped, but part of the reason the price was being bid up so high was the exports to Germany.

Hello world might be simple, but you don’t have to build very much before you start to run into problems with the simple “props down, events up” and you start needing to learn about contexts, hooks in general and so on.

Hooks is really one of those things where you need an IDE to tell you that you’re doing it wrong, since there’s a whole bunch of footguns. It’s doing its best to solve a hard problem inside the limitations of JavaScript, but it is essentially a kludge.

1. Release your code as open source.

2. Make a fortune.

3. Complain that people are freeloading.

4. Abuse your power as project founder to punish them, torching the community trust you’ve built up over decades.

5. Profit?

Whatever Mullenweg hoped to gain by undermining WPEngine can’t possibly be worth the damage he’s done to WP and his own company.

The interesting point is how the value of 10 is not defined in Rust’s source code, but passed down as “word of mouth” from compiler to compiler.

He’s really working hard on torching his reputation. The whole WPEngine debacle just makes him look petty and mean.

Always fun to see the spyware merchants whining about how Apple’s privacy protection efforts makes creeping on users difficult.

Cry harder, dirtbags.

A more efficient image format helps everyone on the web. We’re looking at 30-50% fewer bits sent over the wire for the same image quality. Massive bandwith savings for everyone. JPEG-XL is basically a better version of what Google was already trying to do with WebP, and a suitable long-term replacement for all image formats currently in use.

This is essentially the COBOL argument. Sure, it might not be very good, but it’s long-term stable.

Fortunately, many other frameworks are long-term stable, but also have a good programming language behind them. Django, Ruby on Rails, and there are similar options in Java or C#.

As for the other points, sure, PHP might be the one language where there are exactly two strong web frameworks. But I don’t see the problem of there being 3 or 4. Django has plenty of competition that drives innovation – web2py, flask, etc.

And same for those other claims. All major languages have various kinds of code analysis tools. Most have healthy communities, etc.

Why not just use shell scripts instead of trying to work around make’s weirdness to make it do something it wasn’t designed for?

If make is available, odds are that a bash-compatible shell is too.

ZFS has a big footprint, so it could be of a problem for integrated solutions, like digital cameras needing to save images to a flash-card without having a lot of hardware power.

Hence what I wrote above:

> Would wish the industry could agree on using something more modern and reliable.

There’s no techical reason why we can’t use NTFS on Macs or APFS on Windows, if the industry was willing work towards that goal together.

Kinda sad that a (by modern standards) slapdash file system like FAT32 is still the lowest common denominator, used for flash drives and all sorts of things. Would wish the industry could agree on using something more modern and reliable.

> Stop breaking my builds.

You don’t have to install the latest version if you don’t want to. If you use a version manager, you can keep using whatever version you want for many years.