key

It says this works via the cli but the docker cli works by talking to the socket so don’t you still need socket access? With podman you just need to startup the user-level socket and set a few env vars and testcontainers works fine. I’m maybe missing the “why” it’s important to avoid direct socket access? Is it to avoid configuring SELinux?

Good old autoerotic bondage.

…Affix-iation?

Seems the pitch is just that it supports Apple specific bells and whistles like the emoji bar and beyond that has the stuff other terminals have. I use tilda and use that because it has a critical core feature I haven’t seen in other terminals: it appears full screen over all other windows with a keypress and disappears the same way. Since I use terminal heavily I don’t want to treat it as just another window but as a first class experience which tilda allows. I don’t really get why you’d make yet another terminal without some fundamental core functionality difference like that.

I like yml. Clean to read, easy to use, supports comments.

I noticed that icon in the play store the other day. I assumed it was a scam/copycat app trying to be distinct enough to avoid a takedown or something.

Never asked one. Answered my first one recently.

Frankly AS did a lot of things well

Amazing how many replies to your comment completely miss the point

“software developer says ai will not replace software developers” feels very John Henry

The Pixel 9’s updated design language is giving iPhone from the front

Cringe

That makes no sense. If you join b’ and b’’ into b then the external interface of b is the union of the external interfaces of b’ and b’'. The risk of conflicts between those two interfaces is minimal in the situation they described so no need for namespacing.

I expected the argument to be based on total effort to split then join the internal code compared to the context switching cost of splitting and then splitting again (with an appeal to agile vs waterfall). But this argument feels like they were either dealing with a language/stack with a broken module system that lacks an explicit separation of internal vs exposed or were just joining things strangely.

Expressing a general rule based solely on a specific situation is a disservice (irony intended).

There’s a bug! You can click buttons once after they disappear.

It takes like 5 minutes to beat…

Dad, get out I’m trying to shower!

no other languages out there where you can just write some code in VIM directly on the server through SSH and immediately see your results without any further setup

laughs in coldfusion

For that size and given it’s a pi, maybe just a cheap usb stick

Seems kinda trash tbh. Like the concept I love, I would love a cross-language “by examples” learning resource and snippet repository beyond SO. But looking through there most of the function options are trivial problems. The ones that aren’t one or two lines mostly have broken code that passes very few tests. The weird Z naming of function and variable makes it totally unreadable. The “composition” option is barely comprehendable and beyond that I only see two language options so it can’t even serve as a “rosetta stone”.

I’d usually do the former because by build number I usually mean pipeline or job id in a build server. You could build 4.0.4 and then 3.4.18 and so 4.0.4 could be build number 1026 while 3.4.18 is 1027.

You can also just use a special number to keep your version number unique when doing dev builds so your version number comes through like 3.5.2-48 and some might call the 48 a build number, in which case that would make sense to reset with each version number.

FTS? fuck that

Mastodon and lemmy handle this in slightly different ways. Mastodon (according to the link) replicates media on every instance while lemmy (mostly) only replicates thumbnails. That means a popular post doesn’t cause load for one server on mastodon but does on lemmy. But Mastodon has a higher aggregate cost due to all the replicated data, which is what the linked proposal solves by making it sublinear.

If the torrent is instance to instance I don’t see any real benefit (and instance to client is infeasible). On Mastodon side you still have data duplication driving storage costs and bandwidth usage regardless of whether it’s delivered via direct http or torrent. On the lemmy side it wouldn’t gain much (asymmetric load is based on subscription count and so not very bursty) but would add a lot of non-determinism and complexity to the already fragile federation process.

Conventional solutions like cache/CDN/Object Storage or switching to a shared hosting solution (decoupled from instances like your link proposes) seems like a more feasible way to address things.