guide.elm-lang.org VS Preact

If you look at the repo for that guide (https://github.com/evancz/guide.elm-lang.org), the description and README clearly state that this is his book on learning Elm, so for me it makes complete sense that it is in the I-form. Maybe the fact that it's linked from the official Elm page without any mention of that causes a feeling of disconnect for you.

An Introduction to Elm (HTML)

I am continually perplexed how poor the official documentation is for Elm (https://guide.elm-lang.org). I love the language, I really enjoy working with it, but where does one go to see the complete API? In particular right now I'm trying to find more on setting various events and accessibility attributes in forms, and this is all I see on the official docs: https://guide.elm-lang.org/architecture/forms.html. Not even a label example on a form page? How is this considered good documentation for a language that has been around for a decade? Is there some secret handshake I need to learn to get access to more in-depth documentation of the language?

I think a good first step would be getting familiar with functional programming in general. I recommend working through the Elm Guide, which will get you acquainted with functional programming idioms and working with immutable data. Then, move on to an introductory Haskell resources, such as Write Yourself a Scheme in 48 Hours. After that, hit up CodeWars and start solving puzzles in Haskell.

I think The Elm Guide does a very good job.

Check out Elm. Page 4 of the intro guide I linked offers something close, which you could build upon to create what you want there.

My advice is to follow the elm official guide. Anyway, any doubt you may have, ping me (gabber) on Elm official slack or write to #beginners channel!

This guide will help you learn and migrate to Elm with assumption you already know the basics of React. The Elm guide is great and will give you a thorough understanding of everything you need to know, in a good order.

Elm Introduction: https://guide.elm-lang.org/

The official Elm guide

In this post, we get to know more about Preact, one of this year's trending libraries. And we'll compare it to React to see which one suits better for our projects.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Those who want to develop a library that can be used by any other reactive framework. I often see SignalLike type that tries to subtype it.

https://github.com/preactjs/preact/blob/757746a915d186a90954...

The official Preact documentation.

At the very bottom of the image, there are 3 blocks that I chose to call application components. If you are building a cross-framework library, these can be built with whatever tools you want! Only catch is, all the tools you use to build it, will be needed by everyone consuming it. So choose wisely, and be mindful of how many kilobytes of third party code you will need in order to ship. In Schedule-X, I chose to use Preact. You will probably be fine with most lightweight virtual DOM libraries, and just like with frameworks there are a few to pick from.

>> React is not traditionally used for making games, but that's part of the fun and the challenge. R

> MS Flight Simulator cockpits are built with MSFS Avionics Framework which is React-like and MIT licensed:

https://github.com/microsoft/msfs-avionics-mirror/tree/main/...

preactjs may or may not be faster: https://preactjs.com/

Million.js is faster than preact, and lists a number of references under Acknowledgements: https://github.com/aidenybai/million#acknowledgments

https://million.dev/docs :

> We use a novel approach to the virtual DOM called the block virtual DOM. You can read more on what the block virtual DOM is with Virtual DOM: Back in Block and how we make it happen in React with Behind the block().*

React API reference > Components > Profiler:

DEV is a Rails monolith, which uses Preact in the front-end using islands architecture. The reason why I mention all this is that it's not a full-stack JavaScript application, and there is no state management library like Redux or Zustand in use. The data store, for the most part on the front end, is all data attributes.