L1
es1995
| L1 | es1995 | |
|---|---|---|
| 6 | 10 | |
| 186 | 79 | |
| - | - | |
| 0.0 | 0.0 | |
| over 5 years ago | about 3 years ago | |
| JavaScript | JavaScript | |
| MIT License | MIT License |
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.
L1
-
Statement-terminator-less languages
L1 does not have statement separator. These are identical:
-
Do we really need async/await keywords?
In L1 https://github.com/mlajtos/L1 is async only — every value is an RxJS observable. You can think of observable as an async iterator, or promise that can resolve multiple times. Assignemnt to variable acts as resolving a promise with that value. On assignemnt, every dependant variables are recomputed. This is called “functional reactive programming”. It is a bit more than you asked for, but I got to L1 when I asked myself what if there was no sync/async distinction, but I may have overthought it. :)
-
Function parameter as a tuple
Thanks! I think we share a few aesthetic ideals :) I really like your work on L1 and New Kind of Paper, and just noticed ES1995 – if only it was true…
-
ShapeRank: Rank Polymorphism Meets Reactive - Gilad Bracha
ShapeRank got me really excited when I first heard about it. I stumbled upon combining arrays and observables in my L1 project, but I never really got it working the way I wanted. Gilad is more than capable, so I am really curious how he progressed.
-
Does this Exist?
I did this in L1. Every value is an Observable (RxJS) and operators/function calls are just creating new nodes in the Observable graph. Observables is a generalization of Futures/Promises for multiple values.
-
Unifying “objects” and “scopes”?
I did this in L1: https://github.com/mlajtos/L1
es1995
- Design Principles Behind Smalltalk
-
No Lodash
> The API matters, and readability matters.
Exactly, lodash should be part of the language. https://github.com/mlajtos/es1995
-
[AskJS] Is JavaScript missing some built-in methods?
Yes, https://github.com/mlajtos/es1995
-
SmooshGate
> It made the decision to extend prototypes. In hindsight, a huge mistake.
I think it was a mistake at the time, but I still believe prototypal inheritance is pretty great idea. And JS desperately needs standard library, which IMO should extend built-in prototypes, so the language would be more coherent. ES1995 [0] was a funny take on this direction, but people (mainly non-JS people) would like to seriously use it. Go figure.
[0]: https://github.com/mlajtos/es1995
- ES1995: Javascript that could have been
-
Turboprop: JS Arrays as Property Accessors!?!
(I was trying out some old school way with ES1995. I might rewrite it to TS one day.)
-
[AskJS] TIL StackOverflow monkeypatches the String prototype across its various sites.
ES1995 agrees.
-
Function parameter as a tuple
Thanks! I think we share a few aesthetic ideals :) I really like your work on L1 and New Kind of Paper, and just noticed ES1995 – if only it was true…
- ES1995 – The Missing JavaScript Polyfill
- ES1995 – The Missing JS Polyfill
What are some alternatives?
type-system-j - adds an optional type system to J language
proposal-set-methods - Proposal for new Set methods in JS
Ally - Pronounced L-I, Ally is a programming language with semi-optional types.
proposal-array-grouping - A proposal to make grouping of array items easier
ngs - Next Generation Shell (NGS)
banned - Banned from a site or organization? Account suspended? Censored? Why?
tour
underscore - JavaScript's utility _ belt
proposal-iterator-helpers - Methods for working with iterators in ECMAScript
proposal-iterator.range - A proposal for ECMAScript to add a built-in Iterator.range()
javascript-algorithms - 📝 Algorithms and data structures implemented in JavaScript with explanations and links to further readings