counterfeit-monkey VS Fable: F# |> BABEL

Counterfeit Monkey by Emily Short. https://github.com/i7/counterfeit-monkey/releases

If you don't want to install a parser on your computer, you can play it online by putting the link to the .gblorb file into https://iplayif.com/ I.e. https://iplayif.com/?story=https%3A%2F%2Fgithub.com%2Fi7%2Fc...

Modern games are generally going to be more approachable than old ones. Tastes have changed considerably. In the days when you couldn't pull up a walkthrough in a few seconds, taking days to think of the next step was part of the fun, and just getting permanently stuck at some point was fairly common. Also, letting the player keep going even after they have done something to make the game unwinnable is now considered very uncool. Navigation is much less tedious these days as well, fast travel for example, although the exact mechanics depend on the game.

And that's not mentioning the amount of CPU and RAM available, not only for the game's runtime, but also for tools like I7 (which was used to write Counterfeit Monkey).

For an quicker introduction to modern "interactive fiction", as it's called these days, check out competition entries. https://intfiction.org/c/competitions/7 These are generally written in a shorter amount of time and the results are quicker to play through.

Various old skool text adventures:

If you are already experienced with them then "Counterfeit Monkey" takes it to the next level with a great twist based on anagram-like magic:

> Anglophone Atlantis has been an independent nation since an April day in 1822, when a well-aimed shot from their depluralizing cannon reduced the British colonizing fleet to one ship.

> Since then, Atlantis has been the world's greatest center for linguistic manipulation, designing letter inserters, word synthesizers, the diminutive affixer, and a host of other tools for converting one thing to another. Inventors worldwide pay heavily for that technology, which is where a smuggler and industrial espionage agent such as yourself can really clean up.

> Unfortunately, the Bureau of Orthography has taken a serious interest in your activities lately. Your face has been recorded and your cover is blown.

> Your remaining assets: about eight more hours of a national holiday that's spreading the police thin; the most inconvenient damn disguise you've ever worn in your life; and one full-alphabet letter remover.

> Good luck getting off the island.

https://ifdb.org/viewgame?id=aearuuxv83plclpl

https://github.com/i7/counterfeit-monkey

If you're new to the genre then "Lost Pig" is a good place to start, though technically it's licence (Creative Commons Attribution-NonCommercial-NoDerivs 3.0) is not open source.

Why not write your code in F# and compile it to TypeScript using Fable [1]?

This way you can use native language features for discriminated unions, functional pipelines, and exhaustive pattern matching to model your domain instead of shoe-horning such functionality into a non-ML language!

Model your domain in F#, consume it in Python or C# backends and TypeScript frontends. The downside is needing to know all of these languages and run times but I think I'd rather know F# and the quirks with interacting with TypeScript than a library like Effect!

[1] https://fable.io

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.