HN user

Inviz

187 karma
Posts3
Comments167
View on HN

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?

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

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.

In these 15 years, HN was a website that shaped me and my worldview. It's a social circle that inspires me and broadens my perspective.

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?

hmm... where to start?

  - Variables cascade and cause restyle of whole sub-tree.
  - Attributes often are already on the html element, e.g. title, aria, data attributes, so dont need inline styles
  - Not mixing data with presentation
Just to name a few

I contacted their sales team before, cerebras started at $1500 a month at that time, and the limits were soooooo small. Did it get better?

Edit: Looks like it did. They both introduced pay as you go, and have prepaid limits too at $1500. I wonder if they have any limitations on parallel execution for pay as you go...

I wonder if people who are claiming its not the case ever tried to use promises in hardcore ways like this, chaining 10s of thousands of calls. You often hit some bullshit, i.e. Promise.race is a big cause of issues.

Even if you are doing `then().then()`, something _else_ in the code base could retain the promise somehow and then your whole chain isn't GCable!

For example https://github.com/rxaviers/async-pool library that implements concurrency for async iterators (and uses promise.race) subtly creates GC pressure which you dont see until you make a whole lot of calls and suddenly its slow

yeah but it creates closure as well, which typically references some objects that isn't easy to GC. So if you have long-living promise with some data captured in closure, it will not be cleared. So doing then().then().then() may not release objects referenced in callbacks that resolved time ago.

Couldnt make it to show suggestions in vscode/cursor. I would like to use the tool, but i'd expect it to work consistently across all widgets in the system (i.e. like superwhisper). Is there a technical limitation here or my misconfiguration of things?

Is there some youtube channel covering some interesting stories from MUDs? From dev, player POV and everything in between. Craving for some emergent storytelling of MUDs to listen to while falling asleep

I think the fact that it supports colored glass, and it has 2 variants, and it promotes dimming layer - says that current implementation is probably not the end of the story