PiLuD

I can't think of a language ecosystem where modules / imports, or build / dependencies, or

when I move a file to another directory, it is not always the case that everything that needs to

ask and ye shall receive https://copilot.microsoft.com/shares/DoVsWfraTQ9TtMJRFCCRN

Yup. That's why I like my Kopi. The async syntax is gone. Things can still be synchronous inside

Good watch, with several depths. Thanks! On Thursday, January 1, 2026 at 12:23:10 AM UTC-8 raould

The idea is nice, but needs to be part of the language. As a library on top of an imperative language

I definitely prefer the loop outside of the element as in modern Angular or React: <ul> @for (

For example, real world existing html/(s)css/js is often nigh impossible to update in the small. Eg a

async stuff like anything in ui like you might do in angular with rxjs 2d walls of (mostly) ascii

https://github.com/raould/t2lang/

On Wed, Jan 7, 2026, 6:13 PM Raoul Duke <rao...@gmail.com> wrote: if type checking is just

if i cannot out-of-the-box query the statically typed code base to eg find all instances of

we are supposedly making components that can be wired up to make something. but the wires are

if your environment isn't like a Bret Victor or Smalltalk super multi-staged meta interactive

Your language can be pretty great, but if the tooling sucks then it sucks. I think tooling actually

i feel like this is punch card advice, and fails wrt asynchronicity. the tyranny of call-return seems

advancing tuple spaces, it seems? https://news.ycombinator.com/item?id=18349514

how to fully leverage AI djinn to do your software development bidding. https://github.com/

https://news.ycombinator.com/item?id=43606027 On Fri, Jan 2, 2026 at 12:02 Raoul Duke <raould@

if it breaks it's not funny or, as simple as possible but not simpler. (which is a paraphrasing

https://www.hillelwayne.com/post/alloy-facts/ i have yet to use anything like Alloy ot TLA+ etc. but

also: "Problem finding is more important than problem solving." er, then why aren't ia

i wish ai tooling could at least help keep track of everything important that is not tracked

What if PLT was actually trying to address real-world development issues? What are some important

Observer Observable get set var val Source Sink (actually not as bad i feel, but still not great) for

I do feel that UI is pretty much the most torturous litmus test of any software (and hardware)

it is truly awful how many apis grow from positional caller-unnamed arguments, to struct/dict/bag.

interview question / plt language litmus test / we all fall down: in a ui with plenty of asynchronous

rxjs has streams that might never end but it doesn't apparently have enough typing to statically

RxJS or anything like that which tries to shoehorn a graph into 2d walls of linear ascii text are