todomvc
Koa
todomvc | Koa | |
---|---|---|
60 | 71 | |
28,485 | 34,860 | |
0.1% | 0.3% | |
7.5 | 6.0 | |
19 days ago | 4 days ago | |
JavaScript | JavaScript | |
GNU General Public License v3.0 or later | MIT 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.
todomvc
-
Unison Cloud
The odd thing is unison started purely as a language. Now there's a platform.
I often find the best way to understand complex things is to dig all the way back to when they were being thought up. In this case there's a blog post from 2017 that I still find useful when thinking about Unison:
https://pchiusano.github.io/2017-01-20/why-not-haskell.html
Key quote:
Composability is destroyed at program boundaries, therefore extend these boundaries outward, until all the computational resources of civilization are joined in a single planetary-scale computer
(With the open sourcing of the language I doubt it will be one computer anymore, but it's an interesting window into the original idea)
Personally I find there's a lot to this. It's interesting that we're really, really good at composing code within a program. I can map, filter, loop and do whatever I want to nested data structures with complete type safety to my heart's content. My editor's autocompleting, docs are showing up on hover, it's easy to test, all's well.
But as soon as I want cron involved, and maybe a little state-- this is all wrecked. Also deployment gets more annoying as they talk about a lot.
So I think Unison always had to have a platform to support bringing this stuff into the language, even though they built the language first.
I'd love to hear some opinions from outside Unison about how they like using this language, tooling and hosting.
I'd like to hear this too.
Also, it would be great if there was something like https://eugenkiss.github.io/7guis/ or https://todomvc.com/ for platforms that we could use to compare Unison, AWS, etc etc. Or is there already a 7GUIs for platforms that I don't know about?
-
Hooking-up a headless CMS to React apps
git clone --depth=1 https://github.com/tastejs/todomvc.git
- TodoMVC: Helping you select an MV* framework
-
Is Software Engineering Real Engineering?
The problem with this question is that, if it's not engineering, what is it? A better question is motivated by studying the history of chemistry and its progenitor, alchemy. That is: is software development alchemy or chemistry?
Software development alchemy. Just like alchemy, software dev is not standardized, everyone has their own idiosyncratic naming systems, classifications and rules-of-thumb. Like alchemists, software engineers are often jealous of their proprietary knowledge. Just like alchemists, they admired, feared and loathed for having secret knowledge. And just like alchemists, you have to be exceedingly brilliant to work in such a chaotic field and get anything done.
What changed alchemy into chemistry, and what is the analog to that in software? Arguably the change started with notion of conservation of mass and energy, and the development of the periodic table (thanks to Lavoisier and Mendeleev, respectively). As for what that analog is for software, first we need a characterization of the field. With alchemy and chemistry both, it's essentially mixing stuff together, heating and cooling it, and seeing what happens. But what is it for software?
Software engineering is often mistaken for computer science. Computer science is a tiny subset of software engineering. In practice, almost all of computer science is encapsulated in a few, tiny standard libraries - the places where bubble-sorts and hash maps live. (This mistake is consistent, and leads to "leet code" style interview questions which are irrelevant to actual work). I'd characterize software engineering as the set of solutions to a boundary value problem[0] described as "a set of interacting screens with behaviors pleasing to humans". The current solutions to this problem have been idiosyncratically shaped by resource constraints that rapidly relaxed over time[1], and characterized by elements discovered at random by necessity: e.g. kernels, processes, files, procedures, terminals, etc. In this analysis "language" functions as a kind of "coordinate system" as in physics[2][3], within which each of these elements are described, and within which elements are combined to make new elements, which eventually yield a solution to the boundary problem (which is termed "application").
I don't particularly know what the standardization of software engineering will look like, but I'm certain that this analysis, or something similar to it, is the first steps in the right direction. Personally, I look forward to the day we can shed the considerable weight of our alchemical origins.
0 - https://en.wikipedia.org/wiki/Boundary_value_problem
1 - https://en.wikipedia.org/wiki/Moore's_law
2 - https://en.wikipedia.org/wiki/Coordinate_system
3 - https://www.rosettacode.org/wiki/Rosetta_Code - the same problem is solved in many languages. For applications: https://todomvc.com/
-
Ask HN: What is the point of Front end Framework?
Compare the source code at https://todomvc.com/ to see what various frameworks bring to the table. VanillaJS is generally 2-3x as much code since you have to implement the MVC logic yourself.
- Todo MVC – Helping you select a JavaScript MV* framework
-
Scala PlayFramework and Angular JS - too much effort in terms of duplication and mixing concetps
There is an example (not mine) of AnjularJS controllers, how much JS I have to write:https://github.com/tastejs/todomvc/tree/gh-pages/architecture-examples/angularjs/js
- Lesson 13 : Flutter | Clean Architecture | ToDo Model
-
What is the best way to learn angular besides angular documentation? Any resources? Books?
Learn by doing. You could recreate the TodoMVC app.
-
How easy is ruby to learn from zero experience coding
How easy or hard to build Shopify without zero coding experience? Shopify is a big thing =) So that would be hard to build with zero coding experience. Start with a todo list, micro blog, or something small in scope that interests you. https://todomvc.com/ is interesting since it is the identical app, written in many different ways, different languages and frameworks - and you can use them as reference to see how others have built something.
Koa
-
Hono vs. H3 vs. HatTip vs. Elysia - modern server(less) replacements for Express
Since "Express.js is an old framework that has not evolved for a long time. It's not a good choice for new projects since it can easily lead to security issues and memory leaks." -- H3. Which is also the case for Koa.
-
Instrumenting AWS Lambda functions with OpenTelemetry SDKs
In this example, we're using the serverless framework to quickly set up the Lambda function along with an API gateway for the entry point. The lambda function is a simple Koa REST API with a few functional endpoints.
-
Server-side Rendering (SSR) From Scratch with React
The initial step is to create our entry point, from where the page will be rendered. In this case, we will use the koa framework.
-
The Ascent of Node.js: How a runtime changed the Web
Koa.js: By the team behind Express, Koa.js utilized async/await for middleware, resulting in cleaner and more readable code.
-
Stop using express.js
Koa
-
Node.js Developers: The Key Players in Building Fast and Scalable Web Applications
Koa.js: https://koajs.com/
-
Node JS Microservice Frameworks for Developing Scalable Web Apps.
Koa -Next Generation Node Microservice Framework
-
What is your ideal setup for new project for solo developers
Backend is more tricky. - RESTful APIs I prefer Koajs - For a RPC/microsevice, I have only used gRPC - For a CLI, yargs and inquirer
-
Why I selected Elixir and Phoenix as my main stack
There are lot of different frameworks out there. If you learn one, there is no guarantee that the next job you find will use the same. For example if you learn Express and the next one used Koa or Nest.
-
10 Node.js Frameworks Every Developer Should Know
Koa.js is a minimal and flexible Node.js web application infrastructure, which provides a robust set of features for web and mobile applications. It is an open-source framework developed and maintained by the creators of Express.js, the most popular web framework for Node.js.
What are some alternatives?
jotai - 👻 Primitive and flexible state management for React
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
futurecoder - 100% free and interactive Python course for beginners
Next.js - The React Framework
angular-spotify - Spotify client built with Angular 15, Nx Workspace, ngrx, TailwindCSS and ng-zorro
fastify - Fast and low overhead web framework, for Node.js
concise-encoding - The secure data format for a modern world
Express - Fast, unopinionated, minimalist web framework for node.
awayto - Awayto is a curated development platform, producing great value with minimal investment. With all the ways there are to reach a solution, it's important to understand the landscape of tools to use.
loopback-next - LoopBack makes it easy to build modern API applications that require complex integrations.
realworld - "The mother of all demo apps" — Exemplary fullstack Medium.com clone powered by React, Angular, Node, Django, and many more
feathers - The API and real-time application framework