MelHamnavoe<p>I suspect that <a href="https://phpc.social/tags/Theo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Theo</span></a> is correct and <a href="https://phpc.social/tags/LLM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LLM</span></a> word calculators will end up happiest & most productive in the ‘heavy’ framework space, <a href="https://phpc.social/tags/next" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>next</span></a>, <a href="https://phpc.social/tags/nuxt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nuxt</span></a>, <a href="https://phpc.social/tags/vue" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vue</span></a>, <a href="https://phpc.social/tags/react" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>react</span></a>, <a href="https://phpc.social/tags/laravel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>laravel</span></a> etc. That shouldn’t mean that ‘light’ frameworks like <a href="https://phpc.social/tags/solid" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>solid</span></a>, <a href="https://phpc.social/tags/astro" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>astro</span></a>, <a href="https://phpc.social/tags/slimphp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>slimphp</span></a> <a href="https://phpc.social/tags/tempest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tempest</span></a> have no future. The toolset decision has many factors, they shouldn’t be reduced to just one <a href="https://phpc.social/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> based one.</p>