> Andrew Clark’s vision of using more compiler magic to solve for React’s shortcomings is indeed a very Facebook-esque approach to solving problems with performance and suitability

and

> Much of the innovation in the UI space is now happening around the edges of the React ecosystem: Solid.js, Preact.js, Svelte.js, Vue.js, Astro.js, Qwik.js, Marko.js

- Solid.js requires *babel-preset-solid* [1]

- Selvte has a compiler

- Astro components are custom `.astro` files

- Qwik.js ships an optimizing compiler [2]

- Vue has `@vue/compiler-sfc` [3]

React is fine, stable and easy to upgrade

[1] https://www.solidjs.com/guides/getting-started

[2] https://qwik.dev/docs/advanced/optimizer/

[3] https://vuejs.org/guide/scaling-up/tooling#lower-level-packa...

I have been using Sublime Text for about 8 years now, I have tried multiple different editors in the mean time including VS Code, Atom, Fleet and I always went back to Sublime Text.

After years of using ST for free, I finally bought a license about two years ago when ST 4 came out, I am also a paid user of Sublime Merge, which is the best git client I have tried.

I ride BMX, road bikes and Mountain Bikes. I've tried a VanMoof two years ago and the build quality was terrible. You couldn't pay me to ride one.

I bought the BlackBerry Classic a while ago and I also own the Key 2.

The BB Classic is everything I want in a smartphone, the build quality is great, the keyboard is amazing in and BB OS is really intuitive and fluid to use.

Such a shame that every smartphone nowadays is just a rectangle with a screen and nothing else...

I want something like ReQL[1] but as a language itself

[1] https://rethinkdb.com/docs/sql-to-reql/javascript/

> I might make an exception for RethinkDB since I loved it so dearly.

Don't get my hopes up... I haven't used RethinkDB in ages and have fully moved to Postgres though

You should definitely stick with Postgres -- you made the right call.

But also...

https://www.rethinkdb.cloud

Don't know who is behind it -- a company named MostlyTyped (not sure if this has old RDB engineers in it), but warms my heart that the repo is still seeing commits and usage.

You could combine styled-components/emotion with something like open-props[0]. You get all the power that comes with CSS and a set of variables to help you create a consistent design. That's how I manage my styling.

[0] https://open-props.style

Ooo, that is very interesting. I will have to give that a shot, thanks for sharing!

I've been looking for someone to mention open-props and I really enjoy using it.

Yeah, you would have to raise the one-time payment constantly in order to keep up with your own recurring costs, the more users you have the greater your costs will be.

You can also charge people their net present LTV upfront. For most forums, that's something like $10 worth of ads, which is why several popular forums worked well with a one-time $10 "pro" fee. You don't need recurring revenue from people to get their entire LTV, and you don't need an endowment to make that model sustainable. You need to make them pay you in whatever form maximizes your net present value (NPV).

Twitter, Facebook, and Google have used ads to collect revenue from their users in the past. SaaS apps and services today use recurring subscriptions, which is nice because it lets you match up your inflows to your outflows. Old desktop software, which had high recurring costs too, used single payments (although they also charged for updates). Modern desktop software tends to use subscription fees.

Companies need to make their revenue models match what customers expect in order to get payment. That means that you should be selling your SaaS as a subscription or a metered API even if you (hypothetically) do not have recurring costs. It also means that Twitter might have to stay with a $0/month fee and collect its revenue in the form of ads and "direct payments for services."

For Twitter, "influencers" might pay as much as $1000 for a "verified influencer" label on their profile despite that many of them are upset at $20/month, particularly if you make it annoying for them (so they feel that they are actually spending their money on getting "verified" and the verification will be hard to fake). Maybe you can get $100/year as a "renewal fee" on those labels, too. If you offered the rest of us a $50 "not a bot" green checkmark that takes a few custom photos and an ID, you will probably get plenty of those too.

It's all psychology. Fixed fees and recurring fees can have the same NPV. The game is maximizing that NPV.

I used to work at Starbucks for about a year and a half and it all depends how busy it is. Unless it's busy, those random conversations with customers where the best part of the job, at least for me.