have you seen the code of next.js? its completely impenetrable, and the packages have legacy versions of the same files coexisting, it's like huge hairball
If I am to provide a summary of why layout shouldnt be linear constraints, is that it can't faithfully represent content overflowing onto multiple lines. I.e. it's inherently one dimensional. I.e. you can't really have a layout that adaprts to the screen size without creating a lot of separate breakpoints. This is a big limitation, that for example flexbox doesnt have. When I left Grid i immediately went and reproduced a lot of stuff we've been doing in (new then) flexbox layout engine, and i was like: Oh my god, this is so much more powerful.
Is there a consensus about "Dont do it" negative prompts vs "Do it this way" positive prompts? So it's negative when there's a hard line, and positive when it's being nudged towards something?
is there a modern operational transformation implementation that would work in P2P environment? i've had my own, but it had some convergence issues in complex fuzzied scenarios, couldnt fix before my enthusiasm ran out. I still feel like OT is more elegant and easier to integrate than CRDT. But i'm not finding good lightweight implementations.
When an OT ends up working in a P2P environment, you basically end up with a CRDT. I would say that all CRDTs are OTs (which can be ID-based or positional-based), while not all OTs are CRDTs.
Well, OT has its CAP-like theorem, which says that you can make some sacrifices to get some qualities. Excluding time component from the OT and removing the "first edit wins" rules, allows for very flexible OTs with deterministic tie breakers (i.e. when two people are writing a word in one place, sort words alphanumerically to brea the tie). But in order for this to work for P2P environments, the list of actions can't be collapsed/optimized until all parties rebased their changes against all other parties. In centralized systems, peers can throw away the log of ops that happened before the server's last acknowledged state
I want to ditch stream-json so hard (needs polyfills in browser, cumbersome to use), but I need only one feature: invoke callback by path (e.g. `user.posts` need to invoke for each post in array) only for complete objects. Is this something that json river can support?
jsonriver's invariants do give you enough info to notice which values are and aren't complete. They also mean that you can mutate the objects and arrays it returns to drop data that you don't care about.
There might be room for some helper functions in something like a 'jsonriver/helpers.js' module. I'll poke around at it.
I have a mildly psychotic friend who think that he uncovered the secrets to everything with AI. Quantum theory and Jungian archetypes, together with 4 dimensions - great mix
Let's say the "Secrets of the Universe" broadly consists of Graph of 100 "abstract" interconnected concepts. The concepts have to be abstract because it is describing everything. It has to be limited in number because we cannot be endlessly chasing the definitions till we reach the levels of atoms. Is it possible to get glimpse of that Graph just toying with abstract ideas. The exact nodes / concepts used in the graph maybe different (depending on field) but the structure will be isomorphic. It has to be discoverable in any field since we started with the assumption that the Graph is "Secret of the Universe" so it should apply to any subset as well and should be discoverable from that subset. This is like analytic functions where knowing its derivatives in a small enough interval can lead us to the exact function.
reply