http_server
Vale
Our great sponsors
http_server | Vale | |
---|---|---|
5 | 64 | |
29 | 1,672 | |
- | 2.5% | |
8.5 | 6.8 | |
8 days ago | about 2 months ago | |
Pony | Scala | |
BSD 2-clause "Simplified" License | Apache License 2.0 |
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.
https://ponylang.zulipchat.com/
Vale
-
Vala Programming Language
Not to be confused with Vale[0].
[0] https://vale.dev/
-
Is Something Bugging You?
The article says they created a deterministic hypervisor that runs all pseudorandom behavior from a starting seed to enable perfect re-playability.
But that's all we know so far. I'm assuming there'll be some sort of fuzz testing, and static analysis or some defining actions that your software can perform.
Honestly it sounds a lot like it has a lot of crossover with what the Vale language is trying to solve: https://vale.dev/, but focused on trying to get existing software to that state instead of creating a new language to make new software already be at that state by default.
- Odin Programming Language
-
D Programming Language
Why go through all the trouble when you can do this: https://www.hylo-lang.org/ and not spend a second thinking of lifetimes? No, copies will not be issued unless necessary.
Or why not keep exploring this idea as well? More research-oriented than the first one right now, though, so take it with a grain of salt: https://vale.dev/
- The Vale Programming Language
-
Flawless – Durable execution engine for Rust
Another relevant language might be Vale (https://vale.dev), which is aiming for "perfect replayability": https://verdagon.dev/blog/perfect-replayability-prototyped
-
Two Stories for "What Is CHERI?"
Interesting. Very low level though and C(++) centric. She there any thoughts on combining the hardware and OS features with rust or https://vale.dev ?
- Berry is a ultra-lightweight dynamically typed embedded scripting language
-
I've heard that "Rust's borrow checker is necessary to ensure memory safety without a GC" usually also implying it's the only way, but I've done the same without the borrow checker. Am I just clueless/confused?
Use a runtime memory management solution that's cheaper than garbage collection (see Vale)
-
Vale.sh – A Linter for Prose
This seems like a tool I'll be using, and this is an almost meaningless criticism, but why the name?
There's already the Vale programming language (https://vale.dev/), but moreover, I don't get the meaning of "vale". You could call it something like Englint which actually hints its purpose.
What are some alternatives?
C-headers
v - Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. Supports automatic C => V translation. https://vlang.io
zig_comptime_lisp
Odin - Odin Programming Language
exotracker-cpp
Beef - Beef Programming Language
jennet - A simple HTTP web framework written in Pony
awesome-low-level-programming-languages - A curated list of low level programming languages (i.e. suitable for OS and game programming)
pony-protobuf - Pony implementation / compiler of Google protocol buffers
carbon-lang - Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)
hare-color - Color package for Hare (harelang.org)
awesome-programming-languages - The list of an awesome programming languages that you might be interested in