guide.elm-lang.org VS papers-we-love

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

Papers We Love (PWL) is a community built around reading, discussing and learning more about academic computer science papers. This repository serves as a directory of some of the best papers the community can find, bringing together documents scattered across the web. You can also visit the Papers We Love site for more info.

You might find the paper Out of the Tar Pit interesting if you haven't already read it: https://github.com/papers-we-love/papers-we-love/blob/main/d...

The ideas and approaches you talk about evoked some of the concepts from that paper for me. It talks a lot about separating accidental complexity and infrastructure so you can focus only on what is essential to define your solutions.

Sure he was expecting a practical language and was designing one. Lisp was from day zero a project to implement a real programming language for a computer.

Earlier he experimented with IPL and also list processing programming on Fortran. The plan was to implement a Lisp compiler. At first the Lisp code McCarthy was experimenting with, was manually translated to machine code.

Then came up the idea to use EVAL as a base for an interpreter, which was implemented by manually translating the Lisp code to machine language. Around 1962 then a compiler followed.

https://github.com/papers-we-love/papers-we-love/blob/main/c...

I'm in a 4th camp: we should be writing our applications against a relational data model and _not_ marshaling query results into and out of Objects at all.

Elaborations on this approach:

- https://github.com/papers-we-love/papers-we-love/blob/main/d...

- https://riffle.systems/essays/prelude/

The short ask: Anyone know of any projects that bring incremental view maintenance to SQLite?

The why:

Applications are usually read heavy. It is a sad state of affairs that, for these kinds of apps, we don't put more work on the write path to allow reads to benefit.

Would the whole No-SQL movement ever even have been a thing if relational databases had great support for materialized views that updated incrementally? I'd like to think not.

And more context:

I'm working to push the state of "functional relational programming" [1], [2] further forward. Materialized views with incremental updates are key to this. Bringing them to SQLite so they can be leveraged one the frontend would solve this whole quagmire of "state management libraries." I've been solving the data-sync problem in SQLite (https://vlcn.io/) and this piece is one of the next logical steps.

If nobody knows of an existing solution, would love to collaborate with someone on creating it.

[1] - https://github.com/papers-we-love/papers-we-love/blob/main/design/out-of-the-tar-pit.pdf

Here is a great Repo on GitHub named paers-we-love. You will surely find some great papers there and also some good other resources. Hope this helps.

However, f and g are interchangeable anywhere else (this is not actually true because their addresses can be obtained and compared; showing that a C-like language retains its referential transparency despite the existence of so-called l-values was the point of what I think is the first paper to introduce the notion referential transparency to the study of programming languages: https://github.com/papers-we-love/papers-we-love/blob/main/l...)