eyelidlessness

6 ms·

1.
by eyelidlessness 3mo ago
I worked on a project a couple years back that would have benefited greatly from this approach. I look forward to giving it a spin when I have an opportunity. I’m curious how much is React-specific, or rendering-specific for that matter. Co
2.
by eyelidlessness 3mo ago
I generally agree. But FWIW it does feel fairly idiomatic in terms of code written with Effect/API design in the Effect ecosystem. (Disclaimer: my Effect usage so far has been mostly casual, this observation is based on following the p
3.
by eyelidlessness 3mo ago
Thanks! From what you say here and what I see in the docs, it looks like everything is much simpler and more robust than when I was exploring the space. I’m happy to see that, and thrilled it’s mature enough now to support use cases like nu
4.
by eyelidlessness 3mo ago
I’m surprised to see this using a `--require` hook (rather than `--import`). Maybe something’s changed significantly since I was looking into building some similar functionality… but it makes me wonder about nuances in nub’s ESM support. (W
5.
by eyelidlessness 3mo ago
A trivial counter example to the intuition one might have that compilers likely produce deterministic output. It’s directly responsive to the exchange between Aoi and Numa above, wherein Aoi expresses exactly that intuition. Of course, thos
6.
by eyelidlessness 3mo ago
I’m not sure kindness is the best framing. At least, not in terms of being nice to any particular person who might commit unwanted files by mistake. It’s one of several tools a project can use to ensure quality, alongside eg linters and for
7.
by eyelidlessness 4mo ago
Well before the LLM explosion I would often preface my answers with some form of praise for the question. It depends a lot on audience of course, but it’s amazing how many people tend to perceive direct answers to their questions as negativ
8.
by eyelidlessness 6mo ago
I agree. And I think this also distills down to Rob Pike’s rule 5, or something quite like it. If your design prioritizes modeling the domain’s data, shaping algorithms around that model, it’s usually trivial to determine how likely some “d
9.
by eyelidlessness 6mo ago
It’s a muscle you can exercise, and doing so helps you learn what to focus on so it’ll be successful. IME a very successful approach is to focus on interfaces, especially at critical boundaries (critical for your use case first, then critic
10.
by eyelidlessness 8mo ago
The point of a type system isn’t ever that you don’t have to check the things that make a value represent the type you intend to assign it. The point is to encode precisely the things that you need to be true for that assignment to succee
11.
by eyelidlessness 8mo ago
> But let’s dissect that last suggestion; suppose I do modify the type to encode that. Suddenly pretty much every field more or less just because Maybe/Optional. Once everything is Optional, you don’t really have a “type” anymore, y
12.
by eyelidlessness 8mo ago
It’s not a hack, but you may find more documentation for the equivalent preload values expressed as a <link> tag. There is (near) parity between that and the HTTP Link header. The values used in the article should work in HTML as well
13.
by eyelidlessness 9mo ago
Disclaimer: I’m a strong advocate for static typing. I absolutely see the connection. One of the advantages of static typing is that it makes a lot of refactoring trivial (or much more than it would be otherwise). One of the side effects of
14.
by eyelidlessness 10mo ago
It’s quite common, although I probably see it used more frequently to invoke other (non-shell) scripting languages.
15.
by eyelidlessness 10mo ago
You might want that, I might too. But it’s outside the constraints set by the post/author. They want to establish immutable semantics with unmodified TypeScript, which doesn’t have any effect on the semantics of assignment or built in
16.
by eyelidlessness 10mo ago
Marko’s compiler is designed for partial hydration (by default, without any special developer effort), which performs quite well. IIRC they were also looking at implementing “resumability” (term coined by Qwik, for an approach that sidestep
17.
by eyelidlessness 11mo ago
This is a fantastic way to put it, thank you for adding it!
18.
by eyelidlessness 11mo ago
I don’t agree with your characterization that anyone is “pretending”. The whole point of abstraction is convenience of reasoning. No one is fooling themselves or anyone else, nor trying to. It’s a conscious choice, for clear purposes. That’
19.
by eyelidlessness 11mo ago
But there isn’t anything hilarious about that. It’s a clear-minded and deliberate approach to reconciling principle with pragmatic utility. We can debate whether it’s the best approach, but it isn’t like… logically inconsistent, surprisin
20.
by eyelidlessness 11mo ago
> Sometimes they even fail to even realise that it's what they are doing. Because that’s not what they’re doing. They’re isolating state in a systemic, predictable way.
21.
by eyelidlessness 11mo ago
To some extent you’ve answered this yourself: TypeScript (and/or linting) is the way to be warned about this. Aside from the points in sibling comment (also correct), adding these kinds of runtime checks would have performance implic
22.
by eyelidlessness 11mo ago
This is a matter of choice, not something with an objectively correct answer. Every possible answer has trade offs. I think consistency with the underlying standard defining NaN probably has better tradeoffs in general, and more specific an
23.
by eyelidlessness 11mo ago
It’s not even safe if you’re 100% sure the types are compatible, unless you’re also 100% sure nothing will change that fact. The reason it’s unsafe is because it suppresses the type error permanently, even if whatever factors led to your ce
24.
by eyelidlessness 11mo ago
Thank you for clarifying. (I think?) I think what confused me is the passive language: "everything gets converted" sounds (to me) like the runtime or some aspect of language semantics is converting everything, rather than develope
25.
by eyelidlessness 11mo ago
Right, but I’m not clear on what gets converted to an array. Do you mean more or less what I said in my previous comment? That it requires you (your code, or calling code in general) to perform that conversion excessively?
26.
by eyelidlessness 11mo ago
> everything gets converted to an array at the drop of a hat Can you name an example? IME the opposite is a more common complaint: needing to explicitly convert values to arrays from many common APIs which return eg iterables/iterat
27.
by eyelidlessness 1y ago
Context: until fairly recently, I worked an implementation of XForms (as the project creator, and leading most of the architecture/design). Prior to that, I inherited maintenance of another implementation, which utilized XSLT[1] as a c
28.
by eyelidlessness 1y ago
Because HTML attributes are inherently stringly typed . Where CSS can propagate types, it’s because the CSS parser and object model are involved. For that to work with attr() would almost certainly involve extending that machinery into all
29.
by eyelidlessness 1y ago
I read it as describing their preferred mental model for declaring a result set , which is different from describing their preferred behavior to produce it. This seems clear to me in wording and context; it’s also broadly consistent with h
30.
by eyelidlessness 1y ago
Only personal anecdata, but I’ve observed that I’m far less accident prone since I was diagnosed and have had consistent treatment. I noticed it without prompt, and it never occurred to me before that there would be any correlation. I’ve al

More ›