429 karma · joined August 14, 2013
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 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?
Why do you need to overtake it? Playnite is open source, you could contribute to it to make it better.
Edit: Latest "post" (xeet?) https://mobile.x.com/heyandras/status/1901894087604916396 I could find about revenue
> 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.
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.
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.
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.