papers-we-love
elm-architecture-tutorial
Our great sponsors
papers-we-love | elm-architecture-tutorial | |
---|---|---|
69 | 38 | |
82,511 | 4,157 | |
1.9% | - | |
5.4 | 0.0 | |
6 months ago | about 4 years ago | |
Shell | Elm | |
- | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
papers-we-love
-
The Top 10 GitHub Repositories Making Waves 🌊📊
Github | Website
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.
- What led you to use Linux as your daily driver?
-
We have used too many levels of abstractions and now the future looks bleak
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.
-
John McCarthy’s collection of numerical facts for use in elisp programs
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...
-
Python: Just Write SQL
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...
-
Ask HN: Incremental View Maintenance for SQLite?
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
-
I think Zig is hard but worth it
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...)
-
Functional relational programming model in Clojure(Script)
This idea was raised years before Martin Fowler blogged about it: https://github.com/papers-we-love/papers-we-love/blob/main/d...
-
Which is the most interesting Computer Science research paper that you have read?
FTR Papers We Love is a curated list of papers the community loves. Also contains a bunch of other sources for papers worth reading.
elm-architecture-tutorial
-
Is there any alternative other than JavaScript to deal with web frontend?
Elm is a different approach that compiles into JavaScript. In the extreme case, you have Emscripten which will compile many language into JavaScript but will feel really clumsy compared to using JavaScript in a lot of cases.
-
Learning functional oncepts - Which Language?
https://guide.elm-lang.org/ for a high level guide, and an unstyled button example https://elm-lang.org/examples/buttons.
-
Elm for React developers
I hope this tiny guide was helpful, and that you learned something new today. If you want to learn more about Elm, you should check out the official guide or say hello in the Elm Slack #beginners channel
-
The best language tutorials that you have seen?
https://guide.elm-lang.org/ is always a solid example for me
-
Why I decided to learn (and teach) Clojure
After going through the whole Introductory Guide to the Elm Language and reading the Elm in Action book, I already felt quite comfortable developing webapps in this paradigm. I liked Elm so much that I started a project to teach programming to beginners using this language and made the first classes available on the website elm.dev.br (in Brazilian Portuguese).
- Por que Elm é uma linguagem tão deliciosa?
- Statically-typed functional programming, Elm, Conway's Game of Life, and Emergence
-
Learn functional programming with Advent of Code! ☃️
The Elm guide
-
No side effects/change state.
I'd be happy to jump on a discord call to see if we can't get a fun hello world going locally. There's a live one here you can check out that just renders 'hello world', and they've got a great guide (sorta like the Rust Book).
-
Which functional programming language should I learn?
If you know Web development already, Elm might be the easiest approach. The Elm guide will have you work on functional snippets of code very quickly. The syntax is almost the same as Haskell, it's also pure, it just comes with far less bells and whistles as far as advanced features go. But you'll be able to have a real working web app in no time and the Elm architecture will basically force you to make it functional (whereas you can bend Haskell to program something imperative, with mutable state all over the place, etc…). Elm also has some of the most helpful compiler error messages and a time-traveling debugger, both great features when you're learning. (well, the time-traveling debugger is a great feature, period)
What are some alternatives?
Crafting Interpreters - Repository for the book "Crafting Interpreters"
Flowgorithm-macOS - Flowgorithm for Mac OS
clojure-style-guide - A community coding style guide for the Clojure programming language
git-internals-pdf - PDF on Git Internals
salsa - A generic framework for on-demand, incrementalized computation. Inspired by adapton, glimmer, and rustc's query system.
Elm - Compiler for Elm, a functional language for reliable webapps.
flux - Application Architecture for Building User Interfaces
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
Kalman-and-Bayesian-Filters-in-Python - Kalman Filter book using Jupyter Notebook. Focuses on building intuition and experience, not formal proofs. Includes Kalman filters,extended Kalman filters, unscented Kalman filters, particle filters, and more. All exercises include solutions.
react-bits - ✨ React patterns, techniques, tips and tricks ✨
moodycamel - A fast multi-producer, multi-consumer lock-free concurrent queue for C++11
android_guides - Extensive Open-Source Guides for Android Developers