jksmith

Barely related, I decided to move on. Linux has been weaponized for self-promotion. So I'm happy just working with Beastie these days.

I use the Franz Allegro toolchain exclusively.

Now that I'm out of the corporate tyranny and have my own company, I use lisp for everything. There's certain satisfaction in writing config files and persisting data directly in s-expressions. Any json requirements are triggered by exports to foreign systems.

MSFT won't sign non-disclosures, but they have policies regarding not using your data to train their models. Just trust them if you want to use azure -except for that rogue employee part I guess.

I personally don't know anything about LispWorks except for the name. My pref for Franz is the commercial quality and the toolchain. If you have forgotten your graph fundamentals, Allegro Graph will make you want to get back into it. Very powerful tool for proofs and modeling the world.

Franz Allegro toolchain.

Use python or whatever to build the llm, use lisp to explore and infer from the edges of what the llm has to offer. I don't do anything but lisp these days. Been waiting my whole career to be at this point. I'll never "write" a line of C# again. Just my taste and pref.

It was something like screen: array[1..80,1..25] of byte absolute $B800:0000; So, just use all the extended ascii to assign chars to cells to draw boxes for screens, buttons, tables, whatever. Instant update.

Vasellating. TurboVision was awesome, but it was pushing the boundary of TUI, which in my mind was great for moving hard copy to computer entered use case. To wit, hard copy on your right side, you transfer data to app without looking at screen, but just looking at hard copy, remembering when/where to hit return key, maybe tab for prior field, stuff like that.

But hey, if the screen is drawn 24 x 80 with extended ascii, it's TUI. And man, loved the "absolute" keyword in turbo pascal. Instant screen writes when writing to a 2 dimensional array.

1. Attack surface for agents is tantamount to a virus. 2. Any way for an agent to touch something is a potential compromised vector. 3. The mitigation is controlling the blast radius. 4. Sandboxing capability will have to be baked into architecture. 5. Mitigation includes measuring cost of blast radius. 6. All agent orchestration will likely require an andon cord.

Windows is a horse that is becoming less and less rideable. Be great to get this to build on ReactOS as just a hobby or side effort.

So is theft. Depends on who has the most guns.

You're not getting what I'm saying. Before this technology, the concept of property rights could not be defended, depending on the attacker. This tech allows that, even if it is just for one use case.

Did you read the paper? There exists a technology that has purely enforceable property rights. What is that actually worth? I don't know.

Yeah yeah, I've read the arguments about liquidity issues, shutting down the rails, making it illegal to trade, etc. but that's beside the point and depends on a thousand future variables to play out. So I don't know if btc will make it or not, but I do know property rights mean everything to humans. They literally determine whether not one is a slave (I am my own property). So just the ability to have a technology enables pure property rights to a world where nobody really has enforceable property rights over anything seems pretty interesting to me.

How many degrees of separation is this from adult regulation? Want to provide age information to a site so you can look at porn without any guarantee that information won't be used for additional profit? That's a real thing in the US.

Government assumes zero expected trust reciprocation because they don't have to provide trust reciprocation and can do what they want, and government is comprised of co-opted humans.

Err on the side of sovereign freedom. Arguing about banning this or regulating that is all second principle stuff, and nanny states all strike me as the tail-end of civilization.