proposal-hashbang
ecma262
proposal-hashbang | ecma262 | |
---|---|---|
8 | 22 | |
133 | 14,751 | |
- | 0.4% | |
0.0 | 9.0 | |
almost 2 years ago | 1 day ago | |
HTML | HTML | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
proposal-hashbang
-
Javascript, the GOAT of programming languages that will take over the world in 2024
Before ECMAScript 2023 (ES14), executing a JavaScript file directly from the command line required manually specifying the interpreter path in the first line of the module. This process could vary depending on the operating system and Node.js installation.ES14 standardizes the use of hashbangs (#!) in JavaScript modules, enabling direct execution without the need for explicit interpreter invocation. The hashbang syntax is a simple convention that indicates the interpreter to be used for executing a module. It consists of a shebang (#!) followed by the path to the interpreter and optionally any arguments. For a JavaScript file, the hashbang line typically includes the path to the Node.js executable.
- What's new in ES2023?
-
ES2023 features list!
https://github.com/tc39/proposal-hashbang has some details.
-
JavaScript's New Features: Exploring the Latest Additions to the Language
Hashbang Grammar
- ES2023 candidate source code + spec
-
Updates from the 91st TC39 meeting
Hashbang Grammar: match de-facto usage in some CLI JS hosts that allow for #! Shebangs / Hashbang.
-
cmru is a command runner that allows you to describe commands with javascript.
But if you just wanted to execute it directly then you could use a shebang because everything after the bang is interpreted and not the bang its self. Most js engines allow this in some form. Here is a proposal to standardize it. https://github.com/tc39/proposal-hashbang
- Released Google/zx – tons of DX improvements and more
ecma262
- TC39: Add Object.groupBy and Map.groupBy
-
The "well-known" Symbols in JavaScript
These aren't valid JavaScript (@@iterator would throw an error). They are actually internal Symbols used in JavaScript. They are used to implement features like iteration, instanceOf, and such internally. They actually might get removed or changed
-
📦🔓Closures in JavaScript decoded
Note that in previous editions, the ECMAScript® Language Specification used the term "lexical environment" before it decided to rename it to "Environment Record" so you might encounter this term in other definitions and tutorials.
- Document.all Willful Violation
- ES2023 Candidate source code + specification
- ES2023 candidate source code + spec
-
The Evolution of JavaScript
For a new specification to be written, you need two things, a_ technical committee_, and a standard. The standard specification for JavaScript is called ECMA-262, and the technical committee is Technical Committee-39(TC39).
- Why Async/Await Is More Than Just Syntactic Sugar
-
Show HN: We are trying to (finally) get tail-calls into the WebAssembly standard
4. Proposed something else [ https://github.com/tc39/proposal-ptc-syntax ]
While apple is against Syntactic tail calls, they’re mainly just opposed to versions of it that would remove/unrequire the tail-call optimisation they already do: https://github.com/tc39/ecma262/issues/535
For the version of it that is backwards compatible, they wouldn’t need to do anything other than recognise it as valid syntax. Their main concern is that it "could add confusion with very little benefit."
-
What happened to proper tail calls in JavaScript? (2021)
The spec for STC has a critique of PTC:
- performance
- developer tools
- Error.stack
- cross-realm tail calls
- developer intent
See: https://github.com/tc39/proposal-ptc-syntax#issues-with-ptc
Apple's 2016 response as to why they won't implement STC is here: https://github.com/tc39/ecma262/issues/535
- STC is part of the spec and will take too long to change.
- Now that they've implemented support for PTC, they don't want to regress web pages that rely on it.
- They don't want to discourage vendors from implementing PTC by agreeing to STC.
- They don't want to introduce confusion.
Some of these arguments about confusion and delays seem wrong hindsight, since on every point things would have been better if they'd just agreed to the compromise of STC.
- It would have been part of the spec years ago
- STC would have had a clear way for web pages to know when tail calls could be relied on (and PTC would have been optional)
- Other vendors didn't implement PTC in any case, despite no agreement on STC
- There's even more confusion as things are now
What are some alternatives?
sh - Python process launching
proposal-pattern-matching - Pattern matching syntax for ECMAScript
proposal-symbols-as-weakmap-keys - Permit Symbols as keys in WeakMaps, entries in WeakSets and WeakRefs, and registered in FinalizationRegistries
spec - WebAssembly specification, reference interpreter, and test suite.
clii - Easily build a cli app.
proposal-ptc-syntax - Discussion and specification for an explicit syntactic opt-in for Tail Calls.
proposal-array-find-from-last - Proposal for Array.prototype.findLast and Array.prototype.findLastIndex.
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
proposal-object-pick-or-omit - Ergonomic Dynamic Object Restructuring. [Moved to: https://github.com/tc39/proposal-object-pick-or-omit]
io-ts - Runtime type system for IO decoding/encoding
uwm-masters-thesis - My thesis for my Master's in Computer Science degree from the University of Wisconsin - Milwaukee.
telegraf - Modern Telegram Bot Framework for Node.js