kemal VS full-stack-svelte-prototype

Compare kemal vs full-stack-svelte-prototype and see what are their differences.

Our great sponsors
  • OPS - Build and Run Open Source Unikernels
  • SonarQube - Static code analysis for 29 languages.
  • Scout APM - Less time debugging, more time building
kemal full-stack-svelte-prototype
8 1
3,245 9
0.5% -
5.0 2.7
about 1 month ago 4 months ago
Crystal JavaScript
MIT License -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

kemal

Posts with mentions or reviews of kemal. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-12-14.

full-stack-svelte-prototype

Posts with mentions or reviews of full-stack-svelte-prototype. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-22.
  • Ask HN: Simplest stack to build web apps in 2021?
    17 projects | news.ycombinator.com | 22 Nov 2021
    > They all look complicated and require lots of configs and plumbing to get started.

    I felt the same way so I made my own full-stack "framework" just for me centered around the Svelte component library which I love:

    https://github.com/Glench/full-stack-svelte-prototype/

    Been using it in production and really really happy with it. Obviously kind of stinks to not have community support but so far it hasn't been a huge issue.

    It basically sets up all the crap that I don't want to have to think about while keeping a tight coupling between the front-end and back-end (which is how I develop) — clear separation of code that runs on the server vs the client (with code splitting and CSS generation), rendering pages on server and hydrating client components, communicating between the server and client, re-rendering components when new data arrives. It really fits my needs well.

What are some alternatives?

When comparing kemal and full-stack-svelte-prototype you can also consider the following projects:

amber - A Crystal web framework that makes building applications fast, simple, and enjoyable. Get started with quick prototyping, less bugs, and blazing fast performance.

lucky - A full-featured Crystal web framework that catches bugs for you, runs incredibly fast, and helps you write code that lasts.

amethyst - Amethyst is a Rails inspired web-framework for Crystal language

grip - The microframework for writing powerful web applications.

raze - Modular, light web framework for Crystal

kemalyst

fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production

mustafa - Mustafa is Simple and Fast MVC Framework for Crystal

fastapi-fullstack-boilerplate - A full stack boilerplate for FastAPI

Meteor JS - Meteor, the JavaScript App Platform

chocolate - Simple web framework and template engine

Flask - The Python micro framework for building web applications.