ApiSurface
Fable: F# |> BABEL
ApiSurface | Fable: F# |> BABEL | |
---|---|---|
1 | 60 | |
13 | 2,836 | |
- | 0.7% | |
7.2 | 9.7 | |
17 days ago | 6 days ago | |
F# | F# | |
Apache License 2.0 | 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.
ApiSurface
-
A new F# compiler feature: graph-based type-checking
May I plug https://github.com/G-Research/ApiSurface/ ? It ensures this as part of your testing pipeline, and requires an appropriate minor or major SemVer bump if you alter the API in a non-breaking or breaking way.
Fable: F# |> BABEL
-
Dada, an Experiement by the Creators of Rust
This conversation could be referring to https://fable.io/
Other than that, the question is indeed strange and I agree with your statements.
-
Exploring a foreign F# codebase
NOTE: For larger codebases with more history it is likely that the Program.fs file will have a lot of orchestration and logic as well. given that it is often where everything clashes and starts, for example the Fable Entrypoint is in Entry.fs and it contains a lot of code. The best you can do always is to start at the bottom of the file and work your way up. Remember: Everything at the bottom uses what has already been defined at the top so there are no circular dependencies or random functions/types at the bottom that can trip you off, everything comes from the top!
-
Revisiting WASM for F#
I am a big fan of going with web components + plain (build-less) javascript whenever possible, so it is not surprising that I often favor things like the Fable Compiler, where I can target my F# code directly to javascript and be as close to the native JS experience as possible, both for interop concerns and for ecosystem integration.
-
A new F# compiler feature: graph-based type-checking
Fable compiler - https://fable.io/
The F# community is very friendly (these sub-communities as well), and they have plenty of good issues/opportunities to contribute OSS work to across any skill level.
Phosphor isn't hiring right now, but we expect to begin a search for FE/interface engineers over the next few month. Email [email protected] for anyone interested.
-
Building React Components Using Unions in TypeScript
Naturally I’d recommend using a better language such as ReScript or Elm or PureScript or F#‘s Fable + Elmish, but “React” is the king right now and people perceive TypeScript as “less risky” for jobs/hiring, so here we are.
- Fable: an F# to Dart compiler
-
Dart 3.1 and a retrospective on functional style programming in Dart
Stuff like this: https://github.com/fable-compiler/Fable/issues/1822
It just seems like an incredibly ambitious project that appears to have very little equal but is mainly worked on by a handful of people but no corporate backing. I get the feeling that if you want to use it, you'll either be the only one doing what you're doing or among just a few people. I already use F# and feel this way about the core language itself.
-
Elixir – Why the dot (when calling anonymous functions)?
F# is also part of the OCaml family, has a great to-JS transpiler (https://fable.io/) and F# code can also be used in .NET projects.
- Is it possible to write games like Pac-Man in a functional language?
-
URGENT HELP NEEDED! Should I learn C#, ASP.NET and the new MAUI framework?
I have heard many good things about https://fable.io/ Fable converts F# code to JavaScript. There are currently 407 packages available for interacting with existing JavaScript packages and frameworks.