Fable: F# |> BABEL VS collapseos

This conversation could be referring to https://fable.io/

Other than that, the question is indeed strange and I agree with your statements.

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!

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.

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.

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.

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.

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.

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.

Something like this is probably a lot more realistic than (as fast) "integrated circuits at home" : http://collapseos.org/

http://collapseos.org/

I know the point of it isn't to run on new hardware, but this would be a way to learn it on a stable platform without having to worry about dealing with constant problems from old hardware before trying to implement it on said.

There is something called Collapse OS I read about here on HN:

http://collapseos.org/

I myself am a collector of old devices, having raised three kids plus being a web dev. Hate throwing them away too I was just think about this today could I extract the CPUs or RAM or something to reuse rather than destory for the metals. I'd like to learn more hardware but no time.

Some hope for Colapse OS [1] perhaps?

[1] http://collapseos.org

http://collapseos.org/

Here is a quick guide to the science for those with the brain worms:

Maybe start with sufficient support for a simple OS that allows you to edit and compile programs. Something like FreeDOS or CollapseOs. Once you have that working you can extend it.

During collapse we'll all be using Dusk OS and post collapse we'll be using cobbled together rugged computers running on Collapse OS. I imagine at that point we can probably put the sub name to a vote. Maybe "r/ordinarylife".

Not Linux....but you could just install Kolibri OS for a very light desktop or consider CollapseOS and DuskOS....think Dusk should run bare metal on now and won't be too bloated, but there's always CollapseOS if you prefer to keep things light