http_server
jennet
Our great sponsors
http_server | jennet | |
---|---|---|
5 | 1 | |
28 | 88 | |
- | - | |
8.1 | 0.0 | |
17 days ago | about 2 years ago | |
Pony | Pony | |
BSD 2-clause "Simplified" License | BSD 2-clause "Simplified" 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.
http_server
- ponylang/http_server: Pony library for building HTTP server applications.
-
Announcing the Hare programming language
I use pony https://ponylang.io/ as a language - it's an Actor based language with GC where every actor has its own memory and is responsible for its own GC.
The main feature is its ability to safely share or move data around between actors in a way that is data-race and deadlock free. Pony doesn't use locks anyways :-)
A high level as to how it achieves this:
-
Green Threads vs Async/Await, ergonomics-wise, toward thread-safety
And it's not just the mathematics. The non-type-theoretic paradigm-upending let-it-crash-to-keep-code-correct resilience for which Erlang/Elixir is famous was one of the biggest eye-openers for me in my programming career (which began in 1972 when I was 12). Also, the simple behaviour and very high performance results of contemporary Actorish implementations, especially Akka.io and the in-some-ways-more-impressive ponylang.io and related ORCA GC ("concurrent and parallel garbage collector for actor programs ... does not require any STW steps, or synchronization mechanisms ... zero-copy message passing and sharing of mutable data ... data race free ... [no] read/write barriers"), are eye-catching affirmations of the Actor model's approach.
-
Mutability vs Immutability vs Renaming vs other ideas
Being an unabashed Ponylang fanboy, I'd say that mutability is a separate question from the "actual" type. I'm simplifying a lot here, but generally in Pony you'd express this in a couple of different ways depending on whether you want the binding itself to be immutable or whether you only care about the instance itself:
-
Pony – High Performance Safe Actor Programming
There's an http server and a small "sinatra" like web framework.
- https://github.com/ponylang/http_server
- https://github.com/theodus/jennet
Someone might have done SQLite for Pony, but I'm not aware of it. Writing network protocol stuff in Pony is usually pretty easy and the C-FFI is usually pretty easy which generally makes writing database connectivity (for at least happy path basics) fairly easy. (Add lots of caveats here).
If you'd like to talk more in-depth, swing by the Zulip and myself and other folks from the community can help out with answers.
jennet
What are some alternatives?
C-headers
Iodine - iodine - HTTP / WebSockets Server for Ruby with Pub/Sub support
exotracker-cpp
BeetleX - high performance dotnet core socket tcp communication components, support TLS, HTTP, HTTPS, WebSocket, RPC, Redis protocols, custom protocols and 1M connections problem solution
zig_comptime_lisp
ponyc - Pony is an open-source, actor-model, capabilities-secure, high performance programming language
hare-color - Color package for Hare (harelang.org)
Suave.IO - Suave is a simple web development F# library providing a lightweight web server and a set of combinators to manipulate route flow and task composition.
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
pony-protobuf - Pony implementation / compiler of Google protocol buffers
rust - Empowering everyone to build reliable and efficient software.
msgpack - Pure Pony implementation of the MessagePack serialization format. msgpack.org[Pony]