* That was meant to say "AI UI design disease". I find them to default to overtexting
434 karma · joined May 11, 2017
Small UI feedback: the WORD LOOKUP sheet has UI design disease, i.e. imo too much text. I'd drop "WORD LOOKUP" and "CURRENTLY SAVING". Also behind the latter the current word is repeated (it's already the title of the sheet), so I'd drop that too.
Not seeing a reason to switch atm tbh
I'm working on a similar idea, it's been a while since I published about it but open to input and collabs!
- no more silo-ing, moat BS, by design - they are working on vouching which is becoming more important in the age of AI PRs
It is quite common for national TLDs (like .de, .jp or .cn) to be managed by not-for-profit entities, under contract with their respective governments... which might also not be great wrt censorship.
There is also the general issue of equal access, where shorter, more memorable domains get more expensive and hodling domain names is only disincentivized for people without enough funds. I would very much like to see an alternative system to domain names, probably something more in the web of trust space.
Cross-language libraries don't seem to be super common for this. The recovering-sense-from-text tools I named all use different parsers in their respective languages.
Again, reading (and yes, technically that's also parsing) from an AST from a data-exchange formatted file is mags simpler. And for parsing these schemes there are battle-tested cross-language solutions, e.g. protobuf.
I'm also not saying we can have all these good things, but they are not free, and the costs are more spread out and thus less obviously noticeable than the ones projectional code imposes.
And there are abilities we lose completely by making text the source of truth, like a reliable version control for "this function moved to a new file".
All of your examples work better for code with structural knowledge:
- grep: symbol search (I use it about 100x as often as a text grep) or https://github.com/ast-grep/ast-grep
- diff: https://semanticdiff.com (and others), i.e.: hide noisy syntax only changes, attempt to capture moved code. I say attempt, because with projectional programming we could have a more expressive notion of code being moved
- sed: https://npmjs.com/package/@codemod/cli
- version control: I'd look towards languages like Unison to see what funky things we could do here, especially for libraries. A general example: no conflicts due to non-semantic changes (re-orderings, irrelevant whitespaces, etc.)
On the other hand: Companies pay for Microsoft's offerings and they support the Israeli military in their genocidal campaign in Gaza, I think getting to a moral zero on that is significantly harder.
For effects you still will have to understand the mental model (which I'd argue is inherent in the domain and not incidental to the tech).
From reading Nue's docs on Interactivity, it seems to opt-out of the discussion by going back to good old manual UI refreshs. I personally would not choose that, too many pre-React debugging nights spent on chasing state<->UI desynchronization bugs.
TBC in React and its offspring, you can still model business logic outside of components, we just learned that most UI development is better served by keeping UI and its state closer.
When seeing issues like this one pop up with React in the title, one should really have a good think whether this is solved principally different in other fws OR, and this should be the null hypothesis, is React in the title because it is more widely used than all the others combined
I am excited for what comes after it, until then I'll use Tailwind (reluctantly)