b33j0r

The best approach has been to host a tokio server, and then make a traditional os-native user interface like a full-stack chump.

That’s crazy. It’s still better than the UX’s that game engine designers think work. Sure bro, show me your File Open/Save Dialog and tree view. Show me your text editor (nicely done, zed)

Available components must win. I’ve often been a critic of open weights and open architectures that give very few normal people access. What’s the point of releasing the plans for a nuclear reactor if no one can have the fuel?

It was not fair. It was how I felt trying to build on it. I love the content that was produced, but it was all very experimental and garden shedded from a decision-making angle.

To answer directly, I would credit the PSF and python community with having the best structure that has outlasted my weirdest expectations.

Love/hate with this one. How was I supposed to follow this? I tried, and few things were publicly visible for nearly two years. I last checked in march and it looked like no progress had been made.

That makes me very suspicious of wasiv3. Funny enough, I already implemented a bunch of the promises (pun not intended) and think that freestanding wasm with custom integrations is the more likely future.

The promise of wasi components has not been fulfilled. The market wants to hotload and link artifacts dynamically. The wasi project requires insider wizardry to use it that way: the offering has been statically linking components before you ship. Defeating 99% of the use cases.

I do not like that this has been worked on in the shadows.

If you are talking about a city where this makes sense like Phoenix, the public transportation is very poor. It can take 90 minutes to cover the distance you could drive in 20.

They have a light rail, but it only goes between downtown and a few suburbs. Your other option is several bus transfers.

If you’re thinking of cities like New York or London, public transport is more practical in many cases.

JetBrains’ AI offering peaked last year when Junie was briefly better than Codex. Now it’s a wash.

Honestly all of this drives me back towards nvim or notepad sometimes.

I have had a jetbrains subscription since pycharm came out, and the killer feature was always the visual debugger. Seems nearly quaint now.

What specific things do you like about zed?

Most handle this by having release channels. You would `brew set-channel stable/edge`.

It annoyed me this week because I only had a few minutes to try elixir 1.20 after the announcement, and brew lagged behind. You can install erl and elixir by other means (I prefer to run my own toolchains) but it wasn’t worth doing in that moment.

Brew has or used to have a source option for some recipes and that basicallllly solves it too, if you squint.

Do not use this, I recommend ziglings if anything besides what Loris would say: you have to read code.

The builtins don’t even compile in these examples. This is 2 years out of date at least.

Okay, it’s conscious. But can it run doom? I rest my case.

I had the opposite experience. I saw college kids who didn’t know where the F5 key was on the first day write smart matlab and python programs by the midterms.

I don’t think I’m exceptional at all. I was always behind and that probably reflected pretty poorly on me. But all it took to teach was preparing interesting examples and then spending time with subgroups and individuals.

I bet a lot of people think I’m catastrophically wrong, probably just got lucky.

Ah. A common (and understandable) misconception. LSD-OS doesn’t enhance anything in the UX, it just removes the filters that prevent you from seeing reality, man.

Some confuse this with LDS-OS, which makes the user weirdly and unquestionably `nice` by only accepting inputs from protected mode.

I am a low-level zig guy right now too. I have been around for a long time, and it’s funny to see arenas come back into vogue as a solution to nearly everything.

Arenas are great for avoiding allocations per tick/request/frame/layer. No symmetric free() to bracket lifetimes! They have a purpose, and we always knew that.

But by definition, your program is over-allocating as a tradeoff. Makes a ton of sense in certain use cases. However, we didn’t invent garbage collection and borrow-checking and realloc() just to publish papers ;)

Half of my time programming zig is spent considering allocation strategies. That’s a feature. “Where are the bytes?”

You point to a better timeline. Sometimes—when desperately alone—I imagine.

If only the guy who was destined to close a disk operating system deal with IBM hadn’t been goofing around with his plane that fateful day.

We would all be using lisp machines, running smalltalk on microkernels that put the HURD to shame. Just imagine: instead of backslashes and drive letters, we’d have parens. Endless, syntactically-valid parens.

Or CP/M, probably that. But can it run doom?