<story><title>I don&apos;t care how you web dev; I just need more better web apps</title><url>https://www.baldurbjarnason.com/2022/more-better-web-apps/</url></story><parent_chain><item><author>croes</author><text>I disagree. 
Web devs aren&amp;#x27;t discussing characters and plots but instead argue which typewriter to use.&lt;p&gt;Better tools don&amp;#x27;t make better apps just like word processors don&amp;#x27;t make better books.
The best web dev tools are worthless if the UX is bad.</text></item><item><author>omarhaneef</author><text>The author complains that developers argue about their tools and methods, insist on their favorite techniques, but produce (more) worse apps. Particularly for the amount of time and effort expended on developing the apps.&lt;p&gt;The thing is: the debates aren’t naive. They’re exactly trying to workout the details.&lt;p&gt;When someone says, hey forget postgresql and just use SQLite, and someone else says good luck if you hit n rows, and someone says it can easily handle n+m rows with x memory …&lt;p&gt;Well they’re trying to solve the problem of (more) better apps with their limited resources. That’s essentially the problem of development.&lt;p&gt;Asking people to solve development without discussing the tools and methods is to misunderstand the nature of the discussion.&lt;p&gt;It’s like telling authors to get on and write better novels and not waste time with their opinions on character and plot.</text></item></parent_chain><comment><author>taeric</author><text>Web devs are typically arguing which produced assembly is better.  Granted, we have come a long way, as the typical react site gave up on terse html a long time ago.&lt;p&gt;But, consider, dream weaver and early design tools were ridiculously advanced compared to what most of us are creating in web sites.  Flash tooling was a whole other level.</text></comment>
<story><title>I don&apos;t care how you web dev; I just need more better web apps</title><url>https://www.baldurbjarnason.com/2022/more-better-web-apps/</url></story><parent_chain><item><author>croes</author><text>I disagree. 
Web devs aren&amp;#x27;t discussing characters and plots but instead argue which typewriter to use.&lt;p&gt;Better tools don&amp;#x27;t make better apps just like word processors don&amp;#x27;t make better books.
The best web dev tools are worthless if the UX is bad.</text></item><item><author>omarhaneef</author><text>The author complains that developers argue about their tools and methods, insist on their favorite techniques, but produce (more) worse apps. Particularly for the amount of time and effort expended on developing the apps.&lt;p&gt;The thing is: the debates aren’t naive. They’re exactly trying to workout the details.&lt;p&gt;When someone says, hey forget postgresql and just use SQLite, and someone else says good luck if you hit n rows, and someone says it can easily handle n+m rows with x memory …&lt;p&gt;Well they’re trying to solve the problem of (more) better apps with their limited resources. That’s essentially the problem of development.&lt;p&gt;Asking people to solve development without discussing the tools and methods is to misunderstand the nature of the discussion.&lt;p&gt;It’s like telling authors to get on and write better novels and not waste time with their opinions on character and plot.</text></item></parent_chain><comment><author>ketzo</author><text>This is assuming that software quality is purely a function of the software engineer’s mind and creative ability, almost like art or writing.&lt;p&gt;Many - most? - software devs know multiple ways they could make their apps higher quality, but they just don’t have the time or ability right now, or they have other priorities, or so on.&lt;p&gt;Better tools can, and do, enable engineers to simply do &lt;i&gt;more&lt;/i&gt; than they otherwise could, and sometimes “more” actually does mean “better.”</text></comment>