I don't think this is what really matters at the end, since whatever is the implementation the goal should be to provide a library that people actually like to use.

This one gets the SEO, so I hope you're successful @raythurnevoid.

For years, I’ve shared with friends and clients what I call the bunny theory of code. The theory is that code multiplies when you’re not looking, not unlike bunnies that tend to multiply when you’re not looking.

About the argument against it, "{@const will make code less consistent ": I think the same is true now, since people can come up with very different ways of dealing with the "computed value inside each loop/if function" problem. Some extract components, some use functions, some will prepare the array differently beforehand.

it also allows for more divergence in how people write there code and where they put their logic, making different svelte codebases potentially even more different due to fewer constraints. This last point is actually something I really value, I read a lot of Svelte code by a lot of different people and broadly speaking things look the same and are in the same places.

The administration and its allies fear that the more people gravitate toward the successful, free-market self-insurance approach, the worse their government-engineered health “reform” will look. We’re already seeing the beginning of this trend.

It's amazing what new can do for clarity. This is exactly what I meant, but couldn't figure out how to phrase at the time.

glancing, glimpsing, scanning, surveying, and other forms of casual or disinterested looking, staring