Colloidal

Why build another CLI editor?
What motivated us to build Edit was the need for a default CLI text editor in 64-bit versions of Windows. 32-bit versions of Windows ship with the MS-DOS editor, but 64-bit versions do not have a CLI editor installed inbox. From there, we narrowed down our options…
Many of you are probably familiar with the “How do I exit vim?” meme. While it is relatively simple to learn the magic exit incantation, it’s certainly not a coincidence that this often turns up as a stumbling block for new and old programmers.
Because we wanted to avoid this for a built-in default editor, we decided that we wanted a modeless editor for Windows (versus a modal editor where new users would have to remember different modes of operation and how to switch between them). This unfortunately limited our choices to a list of editors that either had no first-party support for Windows or were too big to bundle them with every version of the OS. As a result, Edit was born.

TL;DR: We tried nothing and were all out of options.

Simulink was the fun part of Matlab.

Absolutely, hell to the nah.

Agreed. Any list without Bowie is just objectively wrong. It's like cheating, with 7 artists that only count as one.

Not all gases. And some gases can be absorbed through the skin, completely invalidating this method. Yay!

I believe it was already useless because of polio.

Fuck me sideways. What a world.

That looks like telephony though, which is a lot less dangerous.

Appwrite and Supabase are both very promising open source "serverless" solutions.

If you're dumb enough to don nazi paraphernalia, you deserve what you get.

Damn you, Ea-Nassir!!

Deduct your vacation expenses from your IR tax filing with this one weird trick!

Sam O'Nella was awesome, but his current release schedule leaves much to be desired.