Recently I had to do an update to the underlying environment a codebase ran on. This was a somewhat involved upgrade and took a longer period of time than most of our work usually does. I did it in a separate worktree, so I didn’t have to constantly rejuggle the installed dependencies in the project, and could work on two features relatively concurrently

It also provides some utility for comparing the two versions. Nothing you couldn’t do other ways, but still useful

And in elixir/erlang we’re spoiled with loads of options, from ETS to mnesia

Apple has done this many times before. Over even more frivolous patents (i.e. a glossy black rectangle)

They made their bed, now they have to lie in it

I’ve only ever worked in one codebase that didn’t need feature flags, and even then we could have used them.

Graphite is ok, but honestly it’s a solution in search of a problem

Maybe if you have a massive pr, splitting it up like this works, but that’s really a planning failure. Stories should be smaller, and if you need to keep them separate for a long time, use feature branches

Can they build factories to brake too?

I use foam for vscode. Works great, is codium compatible, and is open source

Search input elements still don't have a native "clear" button

JFC that's been a thing in webkit for nearly 2 decades

This is actually built into vsc

An ad hoc sorting system for a grid of tiles on an enterprise app

Instead of sorting across row wise, it sorted columnar. So it was

A E I M
B F J N
C G K O
D H L P

Instead of

A B C D
E F G H
I J K L
M N O P

This was a requirement from the CEO. Since we used this project (dogfooding) we stuck a secret search box/command palette in, which you could hit . and then type the name of the thing you wanted and click it

Throw them into the ocean, same as all car batteries

Subaru Solana or whatever it's called. I bought an ascent earlier this year, but it basically came down to splitting hairs when I went with it over the Solana. Absolute blast to test drive that thing, and I'd love to take it down to Moab or similar places.

Probably going to wind up leasing one next year, so I don't have to worry about battery decline down the road

JetBrains users kind of live in their own weird bubble. Of the ones I’ve worked with, a decent number didn’t even know how to use git, they just relied on the built in vcs tools

Check out Elixir’s Ecto. You basically do write SQL for querying, it’s just lightly wrapped in a functional approach.

Not if they have a way to strip watermarks too, as has happened with every other system like this

Python belongs in docker for exactly thus reason

In theory yes, but it becomes a problem of ergonomics. The transpiled library feels like a transpiled library, it doesn’t match the conventions of Nim/Zig. The best ports/wrappers/whatever typically use the C lib for all the heavy lifting and unique things, and build their own interface, that matches conventions of the calling language

Its a neat language, very simple. Has a somewhat simple approach to codegen at compile time, which is both a boon and a curse; you can do a lot with it, and not get too deep into footgun territory, but once you hit the limits of what you can do, you’re pretty much stuck there.

The syntax and other features are very nice, and it makes rather small binaries. I’d say its comparable to Nim in this area.

Sadly, it also suffers the same problems Nim suffers: dearth of libraries.

In some places they are.

In Utah, for example, there’s a system called Utopia. They ran fiber all over the place, to the home in most locations. The fiber itself is an Ethernet network owned by Utopia. ISPs then just provide service over said Ethernet network. You can have multiple ISPs at the same time, and they don’t actually own the last-mile, or much else

If you can’t list em, you shouldn’t be able to charge for em