Rasmus Schultz
@mindplay.dk
Passionate web-developer since 1998 using various languages, databases and tools.
man, I totally get where you're coming from. it must be so hard running OSS projects now.
the balance is way off already.
writing used to take 10-100x the effort of reading & understanding.
a PR now might "look real", even if no real effort went into it, even if it's not worth your time at all. 🙄
the balance is way off already.
writing used to take 10-100x the effort of reading & understanding.
a PR now might "look real", even if no real effort went into it, even if it's not worth your time at all. 🙄
December 5, 2025 at 5:17 AM
man, I totally get where you're coming from. it must be so hard running OSS projects now.
the balance is way off already.
writing used to take 10-100x the effort of reading & understanding.
a PR now might "look real", even if no real effort went into it, even if it's not worth your time at all. 🙄
the balance is way off already.
writing used to take 10-100x the effort of reading & understanding.
a PR now might "look real", even if no real effort went into it, even if it's not worth your time at all. 🙄
of course this is just how web components work, so no shade on Lit 🙂
but most other frameworks use a model where you can atomically update (and validate etc) multiple properties in a single call
you can't have that with web components. (or you could, but they wouldn't really be web components...)
but most other frameworks use a model where you can atomically update (and validate etc) multiple properties in a single call
you can't have that with web components. (or you could, but they wouldn't really be web components...)
November 28, 2025 at 9:50 PM
of course this is just how web components work, so no shade on Lit 🙂
but most other frameworks use a model where you can atomically update (and validate etc) multiple properties in a single call
you can't have that with web components. (or you could, but they wouldn't really be web components...)
but most other frameworks use a model where you can atomically update (and validate etc) multiple properties in a single call
you can't have that with web components. (or you could, but they wouldn't really be web components...)
yeah it's pretty much what I expected
so you wouldn't deal with invariants (like in my example) before it updates
so you either have to allow (and handle) invalid states, or throw exceptions during rendering (no useful stack trace) or leave elements in an undefined state
so you wouldn't deal with invariants (like in my example) before it updates
so you either have to allow (and handle) invalid states, or throw exceptions during rendering (no useful stack trace) or leave elements in an undefined state
November 28, 2025 at 9:50 PM
yeah it's pretty much what I expected
so you wouldn't deal with invariants (like in my example) before it updates
so you either have to allow (and handle) invalid states, or throw exceptions during rendering (no useful stack trace) or leave elements in an undefined state
so you wouldn't deal with invariants (like in my example) before it updates
so you either have to allow (and handle) invalid states, or throw exceptions during rendering (no useful stack trace) or leave elements in an undefined state
I don't know how you're reading my post? but yes, this is what I'm saying, almost any major app will be built with a framework, such as Lit. so I guess we agree? 🤷♂️😄
November 28, 2025 at 9:25 PM
I don't know how you're reading my post? but yes, this is what I'm saying, almost any major app will be built with a framework, such as Lit. so I guess we agree? 🤷♂️😄
do you know how/if Lit deals with this issue?
x.com/mindplaydk/s...
I assume it must have either a non standard method to make atomic updates? or a means of deferring the actual DOM updates as a microtask?
either kind of breaks the DOM contract 😌
x.com/mindplaydk/s...
I assume it must have either a non standard method to make atomic updates? or a means of deferring the actual DOM updates as a microtask?
either kind of breaks the DOM contract 😌
Rasmus Schultz on X: "@Rich_Harris @JivaLabs The biggest fundamental problem for me is updates can be made only to a single prop/attribute at a time. So going from: <number-input value="5" max="5"> To: <number-input value="10" max="10"> If value is set first, it'll be invalid until max is set." / X
@Rich_Harris @JivaLabs The biggest fundamental problem for me is updates can be made only to a single prop/attribute at a time. So going from: <number-input value="5" max="5"> To: <number-input value="10" max="10"> If value is set first, it'll be invalid until max is set.
x.com
November 28, 2025 at 6:26 AM
do you know how/if Lit deals with this issue?
x.com/mindplaydk/s...
I assume it must have either a non standard method to make atomic updates? or a means of deferring the actual DOM updates as a microtask?
either kind of breaks the DOM contract 😌
x.com/mindplaydk/s...
I assume it must have either a non standard method to make atomic updates? or a means of deferring the actual DOM updates as a microtask?
either kind of breaks the DOM contract 😌
scope and complexity about the same as Preact, which I would also consider a framework
I'd say Lit is a framework for building web components
we can quip over the definition of "framework", to me it mostly means that it prescribes how you build things
libraries do not prescribe, they just provide
I'd say Lit is a framework for building web components
we can quip over the definition of "framework", to me it mostly means that it prescribes how you build things
libraries do not prescribe, they just provide
November 27, 2025 at 3:29 PM
scope and complexity about the same as Preact, which I would also consider a framework
I'd say Lit is a framework for building web components
we can quip over the definition of "framework", to me it mostly means that it prescribes how you build things
libraries do not prescribe, they just provide
I'd say Lit is a framework for building web components
we can quip over the definition of "framework", to me it mostly means that it prescribes how you build things
libraries do not prescribe, they just provide
you'll get a fair warning when they locate your servers 🤪
November 27, 2025 at 6:28 AM
you'll get a fair warning when they locate your servers 🤪
"with Lit", yeah - unless you're looking to punish yourself, you're not building anything serious without a framework 😅
November 27, 2025 at 6:17 AM
"with Lit", yeah - unless you're looking to punish yourself, you're not building anything serious without a framework 😅
with React it is different: afaik no proposed standard would offer any alternative?
November 26, 2025 at 9:05 PM
with React it is different: afaik no proposed standard would offer any alternative?
ooh, time to book some "banner ads" 🤫
November 26, 2025 at 9:00 PM
ooh, time to book some "banner ads" 🤫
@kevinpowell.co hey Kevin, here's the CSS challenge you were looking for 😄
November 26, 2025 at 7:28 AM
@kevinpowell.co hey Kevin, here's the CSS challenge you were looking for 😄
you can't say vibe coding anymore, it's offensive now
they want you to call them context engineers or some bull shit now, even if they never looked at a line of code
anything with "engineer" in it is preferred, and actual developers who do actual work are losers who are going to get "left behind"
they want you to call them context engineers or some bull shit now, even if they never looked at a line of code
anything with "engineer" in it is preferred, and actual developers who do actual work are losers who are going to get "left behind"
November 25, 2025 at 5:55 PM
you can't say vibe coding anymore, it's offensive now
they want you to call them context engineers or some bull shit now, even if they never looked at a line of code
anything with "engineer" in it is preferred, and actual developers who do actual work are losers who are going to get "left behind"
they want you to call them context engineers or some bull shit now, even if they never looked at a line of code
anything with "engineer" in it is preferred, and actual developers who do actual work are losers who are going to get "left behind"
it could just be me that doesn't 🤷♂️😄
November 24, 2025 at 8:02 PM
it could just be me that doesn't 🤷♂️😄
a couple of my coworkers have tried it out already, in sheer desperation
the TS language service is killllling my computer slowly
our code base is bigggg 😄
the TS language service is killllling my computer slowly
our code base is bigggg 😄
November 24, 2025 at 6:01 AM
a couple of my coworkers have tried it out already, in sheer desperation
the TS language service is killllling my computer slowly
our code base is bigggg 😄
the TS language service is killllling my computer slowly
our code base is bigggg 😄
superellipses and squircles both trigger me like crazy
I can't even say what it is exactly - both of those shapes just annoy me and make me think "what? why??"
they're just "wrong" somehow
I wouldn't use that shape for anything 🤷♂️
I know it's probably just me but 🙈😂
I can't even say what it is exactly - both of those shapes just annoy me and make me think "what? why??"
they're just "wrong" somehow
I wouldn't use that shape for anything 🤷♂️
I know it's probably just me but 🙈😂
November 24, 2025 at 5:59 AM
superellipses and squircles both trigger me like crazy
I can't even say what it is exactly - both of those shapes just annoy me and make me think "what? why??"
they're just "wrong" somehow
I wouldn't use that shape for anything 🤷♂️
I know it's probably just me but 🙈😂
I can't even say what it is exactly - both of those shapes just annoy me and make me think "what? why??"
they're just "wrong" somehow
I wouldn't use that shape for anything 🤷♂️
I know it's probably just me but 🙈😂
you're reaching
comments look like comments, so it's easy to understand they're comments
this will look like actual syntax, which will confuse new developers
apparently "code" that is just "there" but does nothing - essentially forcing JS devs to learn Typescript
comments look like comments, so it's easy to understand they're comments
this will look like actual syntax, which will confuse new developers
apparently "code" that is just "there" but does nothing - essentially forcing JS devs to learn Typescript
November 21, 2025 at 9:19 PM
you're reaching
comments look like comments, so it's easy to understand they're comments
this will look like actual syntax, which will confuse new developers
apparently "code" that is just "there" but does nothing - essentially forcing JS devs to learn Typescript
comments look like comments, so it's easy to understand they're comments
this will look like actual syntax, which will confuse new developers
apparently "code" that is just "there" but does nothing - essentially forcing JS devs to learn Typescript
this + good debugger & test runner
VS Code is still behind in many of these, esp. goto & refactoring, but it's free and "good enough" 🙂
VS Code is still behind in many of these, esp. goto & refactoring, but it's free and "good enough" 🙂
November 21, 2025 at 9:09 PM
this + good debugger & test runner
VS Code is still behind in many of these, esp. goto & refactoring, but it's free and "good enough" 🙂
VS Code is still behind in many of these, esp. goto & refactoring, but it's free and "good enough" 🙂
it's not personal
but please
stop, examine, and challenge the assumptions about what this standard will achieve
every argument is so easy to dispute
JS has no other "mock" features like this, and it will cause so many real problems 😔
but please
stop, examine, and challenge the assumptions about what this standard will achieve
every argument is so easy to dispute
JS has no other "mock" features like this, and it will cause so many real problems 😔
November 17, 2025 at 7:41 PM
it's not personal
but please
stop, examine, and challenge the assumptions about what this standard will achieve
every argument is so easy to dispute
JS has no other "mock" features like this, and it will cause so many real problems 😔
but please
stop, examine, and challenge the assumptions about what this standard will achieve
every argument is so easy to dispute
JS has no other "mock" features like this, and it will cause so many real problems 😔
so this enable people who already deploy trash to deploy marginally less trash
wow yeah
great
you really are struggling to come up with arguments, aren't you?
why are you working so hard to try to *make* this into a good idea 🤷♂️
wow yeah
great
you really are struggling to come up with arguments, aren't you?
why are you working so hard to try to *make* this into a good idea 🤷♂️
November 17, 2025 at 7:12 AM
so this enable people who already deploy trash to deploy marginally less trash
wow yeah
great
you really are struggling to come up with arguments, aren't you?
why are you working so hard to try to *make* this into a good idea 🤷♂️
wow yeah
great
you really are struggling to come up with arguments, aren't you?
why are you working so hard to try to *make* this into a good idea 🤷♂️
in Node, where you don't need to load an image or a CSS file or use JSX
but sure, it'll work in Node
and as you noted, already does
but
sure.....
but sure, it'll work in Node
and as you noted, already does
but
sure.....
November 17, 2025 at 7:09 AM
in Node, where you don't need to load an image or a CSS file or use JSX
but sure, it'll work in Node
and as you noted, already does
but
sure.....
but sure, it'll work in Node
and as you noted, already does
but
sure.....
you're assuming any competing type system would also be fully elided with no runtime implications
their syntax would not be supported, it would be ignored - just as TS syntax would be ignored
there's really nothing useful or interesting about that
Hegel was a thing - JS/TS users didn't even care
their syntax would not be supported, it would be ignored - just as TS syntax would be ignored
there's really nothing useful or interesting about that
Hegel was a thing - JS/TS users didn't even care
November 17, 2025 at 7:07 AM
you're assuming any competing type system would also be fully elided with no runtime implications
their syntax would not be supported, it would be ignored - just as TS syntax would be ignored
there's really nothing useful or interesting about that
Hegel was a thing - JS/TS users didn't even care
their syntax would not be supported, it would be ignored - just as TS syntax would be ignored
there's really nothing useful or interesting about that
Hegel was a thing - JS/TS users didn't even care
compatible with what?
the proposed standard isn't even fully compatible with TS 🤷♂️
the proposed standard isn't even fully compatible with TS 🤷♂️
November 17, 2025 at 7:02 AM
compatible with what?
the proposed standard isn't even fully compatible with TS 🤷♂️
the proposed standard isn't even fully compatible with TS 🤷♂️
I'll say it again:
loaders.
JSX.
you're simply not going to get what you imagine
you'll use this feature once or twice, find it annoying because it's not like your dev env - your code won't actually work and you'll revert back to tools that work
no one is going to actually use this 😌
loaders.
JSX.
you're simply not going to get what you imagine
you'll use this feature once or twice, find it annoying because it's not like your dev env - your code won't actually work and you'll revert back to tools that work
no one is going to actually use this 😌
November 13, 2025 at 8:59 AM
I'll say it again:
loaders.
JSX.
you're simply not going to get what you imagine
you'll use this feature once or twice, find it annoying because it's not like your dev env - your code won't actually work and you'll revert back to tools that work
no one is going to actually use this 😌
loaders.
JSX.
you're simply not going to get what you imagine
you'll use this feature once or twice, find it annoying because it's not like your dev env - your code won't actually work and you'll revert back to tools that work
no one is going to actually use this 😌
okay, but a browser or dev tools extension could do that
that is not a reason to burden end users with downloading types
no one benefits from that
this is a developers-only feature
it belongs in developer related tooling and does not need to impact the language spec or production runtime
that is not a reason to burden end users with downloading types
no one benefits from that
this is a developers-only feature
it belongs in developer related tooling and does not need to impact the language spec or production runtime
November 13, 2025 at 8:54 AM
okay, but a browser or dev tools extension could do that
that is not a reason to burden end users with downloading types
no one benefits from that
this is a developers-only feature
it belongs in developer related tooling and does not need to impact the language spec or production runtime
that is not a reason to burden end users with downloading types
no one benefits from that
this is a developers-only feature
it belongs in developer related tooling and does not need to impact the language spec or production runtime
write it where??
if you're using tools (which you are unless you're DHH) you're already doing that. already solved.
the only difference is now you can ship types to end users.
which you absolutely shouldn't do.
if you're using tools (which you are unless you're DHH) you're already doing that. already solved.
the only difference is now you can ship types to end users.
which you absolutely shouldn't do.
November 13, 2025 at 7:17 AM
write it where??
if you're using tools (which you are unless you're DHH) you're already doing that. already solved.
the only difference is now you can ship types to end users.
which you absolutely shouldn't do.
if you're using tools (which you are unless you're DHH) you're already doing that. already solved.
the only difference is now you can ship types to end users.
which you absolutely shouldn't do.