Inviz

8 か月前議論

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

Inviz

8 か月前議論

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.

Inviz

8 か月前議論

Hello Jon! This is Yarik. Cool to see you doing all this machine learning work these days.

Inviz

8 か月前議論

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?

Inviz

8 か月前議論

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

Inviz

8 か月前議論

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.

Inviz

8 か月前議論

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.

Inviz

8 か月前議論

What's wrong with GROUP BY 1,2,3?

Inviz

10 か月前議論

Please consider it a feature request

Inviz

10 か月前議論

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?

Inviz

10 か月前議論

yes but you can put it on nested objects. Each type: object can have its own propertyOrdering, so you control whole tree

Inviz

10 か月前議論

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

Inviz

10 か月前議論

nested field have their own propertyOrdering

Inviz

10 か月前議論

gemini api has propertyOrdering field for that

Inviz

11 か月前議論

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

Inviz

12 か月前議論

I wish this had youtube video mixing support. This is something i cant find in other software.

Inviz

昨年議論

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...

Inviz

昨年議論

Cursor lifted "Start a new chat" limitation on gemini and i'm actually now enjoying keeping longer sessions within one window, becuase it's still very reasonable at recall, but doesnt need to restate everything each time

Inviz

昨年議論

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

Inviz

昨年議論

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.

投稿

Archimedes – Your Investment Coach

Show HN: Mobile game and bite-size lessons teaching investment literacy

Show HN: Become a better investor by playing a game with short lessons

コメント