proposal-type-annotations
Elm
Our great sponsors
proposal-type-annotations | Elm | |
---|---|---|
101 | 198 | |
4,081 | 7,446 | |
2.1% | 0.5% | |
4.7 | 5.4 | |
about 1 month ago | about 1 month ago | |
JavaScript | Haskell | |
- | BSD 3-clause "New" or "Revised" 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.
proposal-type-annotations
-
Bun 1.1
That proposal is not fully compatible with Typescript: https://github.com/tc39/proposal-type-annotations?tab=readme...
-
Go 1.22 Release Notes
They held a meeting a few months ago so it's alive but probably still years away.
https://github.com/tc39/proposal-type-annotations/issues/184
-
[AskJS] Kicking a dead horse - TS vs JS
I particularly like this thread in the TC39 types proposal. TypeScript IS a development trojan horse and locks you into the Microsoft Way of being a JS developer.
-
HTML First – Six principles for building simple, maintainable, web software
Edit: There is a proposal to extend JavaScript with type annotations, which would allow ("a reasonably large subset") of TypeScript to run directly in the browser. Yay!
-
Building React Components Using Unions in TypeScript
More importantly, TypeScript typically commits to build things into itself when the proposal in JavaScript reaches Stage 3. The pattern matching proposal in JavaScript is Stage 1, but depends on many other proposals as well that may or may not need to be at Stage 3 as well for it to work. This particular proposal is interested on pattern matching on JavaScript Objects and other primitives, just like Python does with it’s native primitives. These are also dynamic types which helps in some areas, but makes it harder than others. Additionally, the JavaScript type annotations proposal needs to possibly account for this. So it’s going to be awhile. Like many years.
-
Show HN: Conway's Game of Life in TypeScript's type system
this is exactly what I want from the _Types as Comments_ proposal[0] as I think it's the only way that types can feasibly become part of the language. It's hard to imagine how all of the concepts TS introduces via special syntax can be covered otherwise.
-
TypeScript Without Transpilation
JSDoc can get you pretty far, but it can be clumsy sometimes. There’s a [TC39 proposal](https://github.com/tc39/proposal-type-annotations) to allow types to live in JS code and be treated as comments (similar with Python types today)
- Do you think typescript will ever have native support on brosers? Or we will have only the JS type annotations?
-
TypeScript Book
Honestly the TC39 is the best case scenario. https://tc39.es/proposal-type-annotations/
Forget runtime type validation, TS is really for preventing bugs at development time as well as IDE integration.
-
Node.js codebase is still entirely in Javascript and not in Typescript and node team does not even officially provide node TS types
As for 2: here it is :) https://github.com/tc39/proposal-type-annotations
Elm
-
Ludic: New framework for Python with seamless Htmx support
Elm [1] is based on a similar idea. Build your app from pure functions that return HTML tags.
-
Learning Elm by porting a medium-sized web front end from React (2019)
elm is a lovely lang. it would be nice to have modern APIs on it.
here's the project for new eyes:
-
Can you make your own JavaScript by implementing ECMAScript standard?
You also wouldn't really be creating your own new programing language. You would be creating something that can run JavaScript by following JavaScript standards and syntax. You might be able to add some non-standard features of your own on top of those standards, or include your own standard library of helpers or utilities, but you can't completely make a new or alternative language and then load it in the browser (or at least not by reimplementing ECMAScript standards... you actually can make your own language that runs within any Javascript enviroment, if you provide an interpreter or compiler that transforms it into valid JS. Some people have done something like this, eg Elm: https://elm-lang.org/).
- Course using F#: Write your own tiny programming system(s)
-
Building React Components Using Unions in TypeScript
I get it. However, the whole point of using Unions to narrow your types, ensure only a set of possible scenarios can occur, and only access data of a particular union when it’s safe to do so. That’s some of what pattern matching can provide, and 100% of what using switch statements in TypeScript with their Discriminated Unions can provide. Yes, it’s not 100% exhaustive, but TypeScript is not soundly typed, and even Elm which is still has the same issue TypeScript does: You’re running in JavaScript where anything is possible. So it’s good enough to build with and much better than what you had.
-
How to render a basic calendar UI in Elm
The beauty of a language like Elm (and other lambda-calculus / functional programming inspired languages) is that there's very little transformation involved in going from an idea to code. And that seems to have a big impact on getting things done.
- Como desenvolvi um backend web em Clojure
-
Is it possible to write games like Pac-Man in a functional language?
I think the most fun and approachable way for beginners to build games with functional programming is with Elm [1].
See a few (small, demo) games built by the community in [2] .
Notice Elm has abandoned the FRP approach in favor of Model-View-Update [3].
- Qual a linguagem que vocês mais gostam de programar?
What are some alternatives?
rescript-compiler - The compiler for ReScript.
haskelm - Haskell to Elm translation using Template Haskell. Contains both a library and executable.
purescript - A strongly-typed language that compiles to JavaScript
yew - Rust / Wasm framework for creating reliable and efficient web applications
idris - A Dependently Typed Functional Programming Language
reflex - Interactive programs without callbacks or side-effects. Functional Reactive Programming (FRP) uses composable events and time-varying values to describe interactive systems as pure functions. Just like other pure functional code, functional reactive code is easier to get right on the first try, maintain, and reuse.
haskell-names - Haskell suite library for name resolution
language-thrift - Haskell parser for the Thrift IDL format.
Vue.js - This is the repo for Vue 2. For Vue 3, go to https://github.com/vuejs/core
Svelte - Cybernetically enhanced web apps
lens-toml-parser - Lenses for toml-parser
Cycle.js - A functional and reactive JavaScript framework for predictable code