<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: _ta_2231234</title><link>https://news.ycombinator.com/user?id=_ta_2231234</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 05 Jun 2026 03:04:33 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=_ta_2231234" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by _ta_2231234 in "Rich Harris joins Vercel to work on Svelte full time"]]></title><description><![CDATA[
<p>This is unfortunate for your team, but most of your conclusions are not adequate.<p>1. Actually, Svelte has much less "magic" involved than React. Sveltes abstractions are not leaky. The reactivity might be more difficult to understand. But the rules are well defined. They are strange - no doubt - but not leaky. When looking at the generated code it's actually much more obvious what is going on than what React is doing. React on the other hand has some leaky abstractions. The biggest one is the effort you have to put into to make it efficient (memoization). Also, hooks.<p>2. Two way data binding is not a constant source of bugs. Then every team using Vue, Svelte, Angular, React with MobX would have those troubles. I've done 8 years frontend dev in a large company using React and Angular (and recently Vue 3) with different teams. The bugs come from people not technology. I've seen no other correlation there.<p>Granted, React has the largest ecosystem of all of them, but what do you actually need?. In that regard, Vue hits the sweet spot.</p>
]]></description><pubDate>Fri, 12 Nov 2021 08:52:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=29197421</link><dc:creator>_ta_2231234</dc:creator><comments>https://news.ycombinator.com/item?id=29197421</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29197421</guid></item></channel></rss>