Samual

I'm interested in what tree-shakeable methods could look like

GitHub - samualtnorman/solid-syntax-highlight-text-editor: Syntax highlighting text editor in Solid.js Syntax highlighting text editor in Solid.js. Contribute to samualtnorman/solid-syntax-highlight-text-editor development by creating an account on GitHub.

source code: github.com/samualtnorma...

example of something cool you can make with it: samualtnorman.github.io/solid-syntax...

why are you being belligerent? I don't think he can just "get over it", "get over it" in what sense?

I know you mean *as a library* but why do you think this?

the nice thing about using a ponyfill is that when you inevitably make a breaking change and update the Node version requirements, you can easily later update your code from the ponyflll to just using the bulitins. you don't need to migrate from some library that had its own specific API to builtins

hm I'm not sure about that, what's your reasoning? even though we do this in the browser, my reasoning we don't do this in Node.js is because if my package says it supports Node.js ^20, it should actually support Node.js ^20 without any asterisks

ponyfills don't modify any builtins. that's what separates them from polyfills. they're just libraries that happen to implement the interface of a proposal or builtin

how about ponyfills?

why not just this?
let postfix = { ...article_postfix, a_head: "a head" }

I'd really like a language that fills a similar role to WASM text format but has a much frendlier syntax than S-expressions. maybe it could be slightly higher level

what does TPAC stand for?

I am!

At @viteconf.org visiting the @voidzero.dev booth!

it's the classic "Doctor who did this thing" not "Doctor Who did this thing"

I personally prefer UnoCSS over Tailwind

Blue Eye Samurai

I'm not a reply guy. if you don't want strangers replying to your posts, limit your replies to people you follow. sorry I misinterpreted your post and jumped to conclusions and sorry I was condescending about it

sorry it's not my intention to be condescending

what was the correct way I was supposed to interpret
> Remember when people implemented whole ass React apps just to be like "look, we can fade between fake changing the URL of the page"

…API has been baseline since 2015 so the specific thing you are talking about is not really representative of React apps or any SPAs

I didn't say that for fun. what I meant to say is that I think you are being reductive. people don't make SPAs for an animation between pages. people make SPAs because it leads to a better user experience. obviously a bad implementation of an SPA will lead to a bad user experience but the history…

animation is not the reason SPAs exist

oh that's cool, what are the requirements? Nix and Rust?

what does being a teammate entail?

is*
something*

I hate that you can't edit posts

in the case where `key` ins a literal type, it could narrow `m` to somethink like `(typeof m) & MapHas<"someKey">` which `.get()` could detect and not return `| undefined`. this is a limited usecase though

I'm curious, WASM obviously doesn't have a concept of strings so what does the interface look like? would this work with other languages compiled to WASM?

very cool

you can do that in real life too