sxiao

Yeah, Svelte is pure gold.

@dang, second reply and apologies, now I know what you mean, I edited some part away which you probably meant and which is still in quotes of others' comments. Sorry, I'll try to improve and thanks for the hint!

Can't follow you, what do you mean/where did I cross into personal attacks? I highly appreciate Rich but the elephant in the room had to be addressed, especially on HN.

I wonder that I am the only one that questions his move and that you also approach me instead of welcoming a healthy debate. Whatever, I guess you just do your job.

Btw, when does HN get proper pagination and a darkmode?

Do I get shadowbanned now for asking too many questions?

Good point and I agree about Rich but I rather trust healthy markets and competition more than people.

won't be joining any existing company

Good news and the most underrated and overseen comment in this thread. Nice man!

This is so HN, in an Svelte thread memories from Ember (sharing your sentiments though).

Not sure if this topic is worth our time to debate. There are millions of ways of subtly controlling/influencing entities. And it's much easier if you pay money, ESOP and pay even more money if future goals and exits come alive.

The governance of Svelte isn't changing

This is the standard narrative when OSS contributors got hired but ok, I'd write the same.

But then just tell us what was the motivation of Vercel's shareholders and CEO to acquire Rich for such a high price (he is the compensation and ESOP you pay absolutely worth) but what's your gain? "Just supporting Rich and helping the project grow" or just buying him out of the market?

Ben, please don't surprise us and tell that you are the next one on Vercel's payroll.

Why is this 'awesome news' for us devs, the market and competition if one vendor now controls all modern SSR frameworks plus significant parts of the tool chain (swc)?

Am I the only one?

Next just bought its biggest upcoming competitor—SvelteKit. Next is the best that React has to offer but it still has flaws. Svelte and SvelteKit are so awesome you cannot believe it before you've built something bigger and so much ahead of the entire React ecosystem. We migrated a huge/complex React app in a month and the difference is night and day (performance/bundle size/dev productivity). React was great but it's time to move on.

I'm disappointed by Rich. Instead of thinking bigger, raising money (it would have been so easy, Rich, instead of doing proud conference talk after talk why didn't you talk to a VC??)—he just cashed out (sky-high compensation and ESOP). Not a rant and to give you some background, one major reason we went with SvelteKit was not to rely on the Next team. And now, I am again with them...

Now we have a monopoly of rare, modern SSR frameworks.

The left out porkbun's mail service for $24.00/year, still more expensive than their solution but not much.

Agreed. It took me half a day and I came not remotely to the UX and performance of coc.vim. Most incl. the nvim team are not aware that eg. tsserver is the fastest and most responsive code formatter for TS (yes, it goes beyond the LSP spec but that's how it is, also for historical reasons). Prettier does not come close.

Maybe they've never tried or deliberately ignore coc.vim for whatever reason. coc.vim works almost out of the box, has the fastest and most pragmatic maintainer who helps anyone and tsserver makes it as good and as fast as VS Code. Instead of just cloning coc.vim's tsserver implementation—or why do they no contribute to coc.vim??—roll their own inferior solution, years later. It's not that nvim's LSP implementation is at its beginning and we can expect more is coming, no the maintainers just do not know or ignore the status quo. Feels very much like Bram a decade ago.

Maybe it's time that we see a third fork—coc.vim.

So many memories. From a time far away. Before I got my first Macbook. When computer were honest. When the underlying OS was ugly and nobody cared if apps used their own style.

Do Surface Laptops have a healthy battery charging feature? E.g., does charging stop at a specific threshold like 60% with Lenovos?

A type system can do way more than the simple things from your first code block. This is misleading in terms of what a powerful type systems can do.

Re your second code block: This can be typed with literal types, no need for tests at compile time.