HN user

kikki

429 karma
Posts7
Comments56
View on HN

Completely off topic but the title made me wonder if there’s any subscription service that cancels you if you don’t use it? Not quite usage based billing - plans that cancel (or pause) without use? I can’t think of any - terrible business model of course

the company doesn't care about community and only cares about profit.

There are plenty of examples of VC funded companies that care about community & don't "only care about profit". Bluesky is a good one (literally a community / social platform). That's such a black & white take it baffles me.

Taking VC is an albatross that means a large portion of devs will never trust you or use your services

A "large portion of devs" (the majority) use so many VC funded services? Probably _most_ services devs use are VC funded. GitHub itself - was VC funded.

You can have an anti-VC opinion but you have to also live in reality.

I own a Tesla (and subscribe to "FSD", >70% of my miles are FSD without issue). As it stands though, Waymo is by every metric objectively better at "autonomous driving".

I would also love to see every car brand have full autonomous driving. It seems like you think you must be in one camp or another, and that one has to "beat" the other - but that's not true. Both can be successful - wouldn't that be a great world?

Your original post was very public under a very well known brand - you have no expectation of privacy after that. People are going to respond to you publicly.

OpenAI O3-Mini 1 year ago

I think trained knowledge is less and less important - as these multi-modal models have the ability to search the web and have much larger context windows.

Oh - my bad - I thought you were a contributor to Lapce (which apparently uses Druid). Iced looks nice too, but it's missing a lot of core features that I think are pretty crucial (e.g. Multi-windows).

How have you been finding Druid? I think it's a difficult start for a lot of people because how often it's changing (and how Xilem may fundamentally change it again in the future). I had a similar issue with iced. Rust GUI is in a weird state right now with no strong options unless you go WebRender or something like Tauri.

This is either a fundamental misunderstanding of React, or you're actually talking about a different library.

React works well for simple, non-interactive components. Complex, interactive components are going to have state. Stateful components don't work so well in React

React components are designed with state in mind. When state changes, components passed that state in the form of props are re-rendered. Don't take my word for it though, from the first paragraph on the reactjs.org website; "React makes it painless to create interactive UIs. Design simple views for each state in your application, and React will efficiently update and render just the right components when your data changes."

At the point all of the benefits of React (preservation of selection, caret position, scroll position etc.) vanish.

I have never heard these spouted as the benefits of React. The main fundamental philosophy of React is that only components that have state changing "react" to changes - in other words, the benefits of React are: no unnecessary re-rendering (hence the virtual DOM).

If you want to update props in a stateful component, the recommendation is to replace the component entirely by changing its key

This part just threw me, if you are doing it this way - you are doing it wrong.

2. You can move anywhere in the country, like from San Francisco to Nashville, and your compensation won't change

This is confusing. If I work in Nashville is my start compensation the same as if I live in San Francisco? Does San Francisco market-rate determine national salary bands - or are they still different based on location? Cost of living is a thing no matter how you cut it.

It doesn't change often, if we do we just have large automated rollout plans - but we've done mass changes enough times there are good procedures around large DB migrations.

There are _many_ databases on each server, last I checked there was around 8 servers (or: "clusters") - and we have it so the traffic is somewhat evenly distributed across each server. There are reasonable capacity limits, and when servers get full we spin up a new one and start accepting new wikis there. I am not in OPS, and they do a lot of work behind the scenes to make this all run smoothly - but from an eng perspective we rarely have issues with this at scale.

Some of this was open source before we unified all of our wiki products, which has a lot of the selection / db logic, at https://github.com/Wikia/app.

Not quite the same but at Fandom (Wikia), every wiki has its own DB (over 300,000 wikis), and they are clustered across a bunch of servers (usually balanced by traffic). It works well - but we don't ever really need to query across databases. There's a bunch of logic around instance/db selection but that's about as complex as it gets.

Look a little deeper. Your "screener" section is an inbox. You can either whitelist or blacklist messages that come into here. In your Gmail inbox, you can also block addresses and never see them again. It is the same interaction - no matter what marketing spin you put on it.

If that's HEY's value proposition, then they're in for a rude awakening. Personally, I think the proposition is simply using something other than Gmail, which is a fine enough reason without needing to put any marketing spin on it. $99 for an alternative though is a difficult ask.

I watched the HEY video and I don't get it - the screener feature is not innovation - it's a block list with a different name. Gmail has this. The way Jason hyped up every feature and then you realise it's something that already exists with a special "product name" (Imbox, really?). I can see why people buy into the marketing speak but look a little deeper.