Penguin of great renown.
The penguin revolution is nigh, only the feathered and the tuxedoed will be spared.
Except for seagulls, they can get fucked.

@pngwn.at
Penguin of great renown.
The penguin revolution is nigh, only the feathered and the tuxedoed will be spared.
Except for seagulls, they can get fucked.
Do iiiiiiiiiiit
People that use @pi.dev as their harness..we want to ship a Svelte plugin for it but since it doesn't natively support subagents, which option do you prefer? a. We don't ship subagents for `pi` b. We expose a tool that spawns a new pi instance c. We assume you have `pi-subagents` and configure that
Don’t undersell yourself!!
@paolo.ricciuti.me for tirelessly innovating and maintaining svelte ai tools, spearheading svelte custom renderers, and hosting weekly events for the svelte community.
We do not deserve Paolo.
I also don’t necessarily agree that the abstraction is that leaky, I think the underlying model arguably matches the semantics. Arguing that all abstractions that match the underlying DS are leaky, kind of assumes all DS disagree with the semantics. I’m not sure that is the case here.
Yeah. I think 3 states is fine tbh and there are valid arguments against it. One is boring old familiarity. People are to tri-state theme toggles.
i love him. you can wake him up if he goes to sleep!
Long overdue, but I finally have an internet home.
I don’t know if the little green box was a psychology play by the @npmx.dev folks but either way it 100% works on me.
I think this a real great discussion and I think the core argument is probably correct. What I do think would be helpful is communicating that flipping dark -> light in system light mode is a return to system. Something that communicates dark -> back/ reset to light.
I found my original demo from back when twinkleplop was just a baby
You can do the highlight api thing with twinkleplop too! If you want to ofc.
feel free to ping me a link and i can take a look whenever!
ITS REAL!!
all fixed! will release again shortly. Thanks!
Yeah. There are a few reclassifier bugs like this. Now the release is oit and performance is good, I’ll be focusing on new languages and correctness. There are some areas where I’m just not sure though. Eg classes vs types, built ins vs types. Is it just about type position? Etc.
I have PRs switched off for the time being but if you tell me your GitHub handle I’ll see if I can add you!
I don’t think any syntax differences are due to performance. Either I couldn’t decide / went for simplicity(should storage kinds have their own token? When is it a type vs a built in?) or they just aren’t implemented (regex is its own language and I forgot). File an issue if you’d like to discuss!
Let me know if you see any issues with the output! I have many tests but I’m sure there are things I’ve missed. Would also love to add an official angular grammar, so I would love to take a look at that.
Just released a new twinkleplop version with some significant performance improvements across both tokenisation and rendering!
I finally had time to go back and explore a few other ideas. I was also slightly annoyed that I wasn't faster on all sizes.