Thro4l31

4 ms·

1. 1.▲
   by Thro4l31 2y ago

   The problems come with maintaining the translated code bases: 1. A code base written in C and a team of C engineers that have a good mental model of the code base to be able to maintain it. 2. An automatically translated Rust code base. Pot
2. 2.▲
   by Thro4l31 2y ago

   I don't think people will migrate to Go, as they most likely chose Node (or Deno) because of full-stack Typescript or Javascript. People who need the great performance of Go are probably already using it. For a Rust, Typescript, C#, Ko
3. 3.▲
   by Thro4l31 2y ago

   Deno (with Typescript of course) is my "smaller Rust". Whenever I don't need the performance and efficiency of Rust, I fall back to Deno. The development speed is much higher while the result is reasonable fast and safe. - Ty
4. 4.▲
   by Thro4l31 2y ago

   I think this all is true. No idea why the downvotes.
5. 5.▲
   by Thro4l31 2y ago

   Of course React can handle complex and large scenarios. And those scenarios aren't even large. It's good that you created that proof. Still, Svelte is much easier while more performant, even if that extra performance is most often
6. 6.▲
   by Thro4l31 2y ago

   > I really am disappointed svelte5 is turning into react-ish framework. This is very wrong. Read the announcement and the docs: https://svelte.dev/blog/svelte-5-release-candidate https://svelte-5-preview.