core VS React

elm is a lovely lang. it would be nice to have modern APIs on it.

here's the project for new eyes:

https://github.com/elm/core

https://elm-lang.org/

In Basics.elm we have:

The package docs for all the functions we learned today

However I notice that the developed of elm/core has died down (last commit was 4 years ago) and I feel that it's fading into obscurity.

https://elmprogramming.com/

There isn't that much good learning material. It is important to get comfortable with the official docs. Especially the standard library that you find here: https://package.elm-lang.org/packages/elm/core/latest/

Looking at the default branch of core, you can already see this in more than just "for the compiler".

For a minimal but useful set of functionality, I would love to see a better set than elm/core. In essence, basic types (Int, Float, String, Bool) and ways to combine these: Tuples, Records, ADT. Since they are also used so frequently, List, Map/Dict, Set and Option/Maybe implementations should also be included. In terms of functions, basic Math and a sensible set of operations for each of the included types. Again, elm/core is a good example.

Once all that handwritten C code was solid, I needed to make sure the C generated from Elm was working properly. I found the source for the core library's unit tests and decided to port them into my project and add some of my own tests. You can run the tests in WebAssembly in your browser too. (Funnily enough, one of the biggest challenges was getting the Elm Test framework itself to run! The framework is more complex than the tests themselves. I still need to come back to the fuzzer tests!)

ReactJS React js. CSS. JSX. Function Components in React.

JavaScript Standard Style is less opinionated about JSX formatting and largely leaves JSX as-is. In a React project, you should integrate with React-specific linting rules for ESLint. The generally accepted configurations are eslint-plugin-react and eslint-plugin-react-hooks, enforcing some best practices of writing React code.

We are continuing to add new project templates for various types of projects, and we've recently created one for the infamous combination of React with Vite tooling.

Go to https://react.dev/?uwu=true for a surprise.

You can use any frontend framework you want — react-based tooling, however, has a natural advantage as it models everything as a function of state, which can map 1:1 with the concept in Burr. In the demo app we use react, react-query, and tailwind, but we’ll be skipping over this largely (it is not central to the purpose of the post).

Oddly, no info on changelog: https://github.com/facebook/react/blob/main/CHANGELOG.md

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.

Cheryl Murphy is not only a dedicated full-stack web developer skilled in technologies like React, Next.js, and NestJs but also a community-driven professional who recently took on the role of volunteer project team lead at Web Dev Path. With a dual Bachelor's degree in Computing and Chemical Engineering from Monash University, Cheryl’s journey in tech is marked by a passion for building accessible solutions and a commitment to fostering community within tech.

Basic knowledge of ReactJs