TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Google's proposal to split the JavaScript standard

5 点作者 ksbrooksjr7 个月前

2 条评论

CharlieDigital7 个月前
No comment on the proposal, but this:<p><pre><code> &gt; JavaScript might finally be accessible to newcomers and fun once more! </code></pre> I don&#x27;t think JavaScript has become less accessible. One can still write Vanilla JS without bundlers and compilers. It&#x27;s still the same JS as it always was. Small HTML+JS projects I wrote in the early 2000&#x27;s still work today. I think the ecosystem today is even richer and better than it was &quot;back in the day&quot;.<p>In the last few years, I&#x27;ve also worked with many folks that transitioned into dev from non-CS, non-engineering backgrounds with React and JS being their entry point (you may argue that React != JS).<p>But a realization I&#x27;m having recently is that one day in the not so distant future, we&#x27;ll think of JS like we think of assembly: just a low level target that some higher level instruction compiles to. That higher level instruction is natural language and the compiler is LLMs.
jauntywundrkind7 个月前
Not really a Google proposal, and that just makes me way more terrified this bullshit load of crap might happen!<p>&gt; <i>Shu-yu Guo, Google Matthew Gaudet, Yulia Startsev, Mozilla Keith Miller, Michael Saboff. Apple Peter Hoddie, Moddable Ross Kirsling, Sony</i><p>Gods fucking forbid, holy hell. There are a <i>lot</i> of people who have tried and worked to de-tool JavaScript, to return it to a usable natural language directly authored and used on the web.<p>We are so close, with such heavy optimization to h3 and cross-request header and body compression. We are finally near being able to just use js.<p>And once again the industrial monsters come by and propose making the easy &amp; natural flatly impossible, making what developers k ow inaccessible &amp; insufficient for the machines &amp; web.<p>Disgusting. And the arguments suck. Suck egg. No, performance won&#x27;t be better if we transpile. No, security won&#x27;t be better if transpilers do the job instead of the runtime. Assuming there are transpilers in the way destroys the possibility that the runtime can get faster with new features, if they are transpiled out! Putting transpilers in the way expands the scope of security concerns &amp; checking!<p>I dislike this so so much.