包阅导读总结
1. 关键词：JavaScript、变化、ECMAScript、专业化、大规模
2. 总结：本文探讨了 JavaScript 临近 30 周年，语言发生了诸多变化。包括名称、规模、框架、编译、类型安全等方面，如今规模庞大致开发者需专业化，标准名称为 ECMAScript。
3. 主要内容：
– JavaScript 变化
– 名称：不再单纯叫 JavaScript，标准名称为 ECMAScript
– 规模：极其庞大，开发者难以精通所有部分，被迫在服务器端或浏览器端开发中专业化
– 框架：全是关于框架
– 同构性：具有同构性
– 新增：许多新的运算符、JSON 广泛应用、有各种构建和构建工具、JIT 编译、注重类型安全、庞大的库生态系统、其他语言可交叉编译为 JavaScript
– 专业化
– 服务器端和同构代码的发展使 JavaScript 规模更大
– 开发者难以了解浏览器和服务器端开发的所有特性，常见的是专注于某一端的 JavaScript 框架开发
思维导图：
文章来源：infoworld.com
作者：InfoWorld
发布时间：2024/8/5 9:00
语言：英文
总字数：1521字
预计阅读时间：7分钟
评分：85分
标签：JavaScript,ECMAScript,Node.js,TypeScript,JSON
以下为原文内容
本内容来源于用户推荐转载，旨在分享知识与观点，如有侵权请联系删除 联系邮箱 media@ilingban.com
With JavaScript’s 30th anniversary on the horizon, now seems like a good time to take stock of how much the language has changed. Here are 11 ways the JavaScript we use today is completely different from the language its inventors and early adopters could have imagined.
11 ways JavaScript is not what it used to be
- It’s not called JavaScript anymore
- It’s so massive that developers have to specialize
- It’s all about the frameworks
- It’s isomorphic
- Many new operators
- JSON is everywhere
- Builds and build tools
- JIT compilation
- Type safety
- The vast library ecosystem
- Other languages cross-compile to JavaScript
It’s not called JavaScript anymore
In the beginning, everyone called it JavaScript. Today, most developers still use that name. Officially, though, the people who create standards use the name ECMAScript. Some even spell out the official version number of the normative language specification, which goes up to 14. ECMAScript may not roll off the tongue or conjure memories of warm coffee, but it successfully differentiates JavaScript from Java. That way, JavaScript’s developers don’t have to worry about Java trademarks, logos, or any other form of trade dress. Well, except for the fact that ECMA International, the keepers of the specification, like to put that little registered trademark symbol next to the name: ECMAScript®.
It’s so massive that developers have to specialize
JavaScript today is so immense that it’s impossible for anyone, even developers who use it every day, to know every part of it. The arrival of server-side options and isomorphic code attracted so much new energy and development that one person can hardly know all the idiosyncrasies of writing code for the browser or the server—let alone both. Developers are forced to specialize in one of these two areas, even though they could, in theory, write code that runs across them. It’s pretty common for developers to spell out that they work on browser-based JavaScript frameworks, server-side JavaScript, or even database-side JavaScript. Hey, it’s a big world out there.
