macOS is finally getting some serious competition with an open platform!

You plug it into a socket.

Plugging a power-supply into a normal outlet like this is legal in many places, and illegal in many others.

Check local code before proceeding!

That's step one, next is your friends.

Let's go!

This battery uses a safer type of lithium chemistry that is less prone to overheating, though no large battery is risk-free. Water is used by firefighters to cool battery fires (they can reignite tho).

Install it outdoors or in a detached garage, away from anything flammable. Never in a bedroom, hallway, or escape route.

There are newer batteries tech that can't inflame.

I got really excited when Farid showed me this!

He has fixed the oldest and most upvoted issue on devenv: https://github.com/cachix/devenv/issues/16

Basic example in devenv:

  { multiverse, ... }: {
    packages = [
      multiverse.cmake."3.16.5"
      multiverse.bun."0.7.0"
    ];
  }

Docs: https://devenv.sh/pinning/#pinning-an-individual-package-ver...

Because people who do good work get attacked left and right and noone steps up.

No it isn't.

Your local .env should NOT be shared, but should also be assumed to be leaked at any given time. Security should be done using a secrets manager through the cloud platform that's being used, e.g. AWS'secrets manager (or ssm param store too i guess)

Pasting it into chatgpt should not be a problem.

It also doesn't belong in git repos, but a much bigger issue is what process led to it. It's pretty standard to ignore it in a .gitignore, I'd be very surprised if modern agents made that mistake. And even if they did, agents should call tools that scaffold deterministically so that this isn't a problem.

I genuinely don't even know what we're talking about anymore, .env files are just values (it even says so in the article). People are making it way more complicated than it needs to be for no discernable reason other than an insane amount of laziness.

fnox is mostly a copy of secretspec (and it's good to have one!), so you'll find the same kind of support in both. I wish instead we'd collaborate with Jeff, but oh well.

The difference is that we're providing an interface for applications to build with, with 8 SDKs available so you can have first-class support for secrets whatever you're bulding. I do hope fnox copies that too!

You keep saying that but I disagree strongly. Having looked at both fnox and secretspec, there are some obvious similarities because they're both in the same space, interacting with many of the same tools, and there are only so many ways to declaratively state "set the FOO variable with the 'my_secret_key' value out of the Bar provider".

Those inherent similarities aside, I don't see it. They don't seem to have a lot in common as far as design or implementation or configuration.

Don't take the black pill <3