ponyc
Akka.net
ponyc | Akka.net | |
---|---|---|
61 | 20 | |
5,602 | 4,618 | |
0.2% | 0.5% | |
9.2 | 9.3 | |
7 days ago | 8 days ago | |
C | C# | |
BSD 2-clause "Simplified" License | GNU General Public License v3.0 or later |
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.
ponyc
- Old Version
-
The problem with general purpose programming languages
For example, the actor's model is not used by a lot of languages, Pony (https://www.ponylang.io/) and Elixir are the only ones that I know, but they address the concurrency problem quite well, while it's a pain to deal with in other languages at large scale.
-
Found a language in development called Vale which claims to be the safest AOT compiled language in the World (Claims to beSafer than Rust)
And that last point is critical. If the language flatly can't represent some concepts it uses, they have to be implemented somewhere else. I had a similar discussion with a proponent for Pony once- the language itself is 100% safe, and fully dependent on C for its runtime and data structures. One of Rust's core strengths is being able to express unsafe concepts, meaning the unsafe code can expose a safe interface that accurately describes its requirements rather than an opaque C ABI. Vale doesn't seem to do that.
-
The Rust I wanted had no future
"Exterior iteration. Iteration used to be by stack / non-escaping coroutines, which we also called "interior" iteration, as opposed to "exterior" iteration by pointer-like things that live in variables you advance. Such coroutines are now finally supported by LLVM (they weren't at the time) and are actually a fairly old and reliable mechanism for a linking-friendly, not-having-to-inline-tons-of-library-code abstraction for iteration. They're in, like, BLISS and Modula-2 and such. Really normal thing to have, early Rust had them, and they got ripped out for a bunch of reasons that, again, mostly just form "an argument I lost" rather than anything I disagree with today. I wish Rust still had them. Maybe someday it will!"
I remember that one. The change was shortly after I started fooling with Rust and was major. Major as in it broke all the code that I'd written to that point.
"Async/await. I wanted a standard green-thread runtime with growable stacks -- essentially just "coroutines that escape, when you need them too"."
I remember that one, too; it was one of the things that drew me to the language---I was imagining something more like Pony (https://www.ponylang.io/).
"The Rust I Wanted probably had no future, or at least not one anywhere near as good as The Rust We Got."
Almost certainly true. But The Rust We Got is A Better C++, which was never appealing to me because I never liked C++ anyway.
-
How long until Rust becomes mandatory, and use of any other language opens the developer up to Reckless Endangerment charges
Pony or bust.
-
Universal parameter passing semantics
If you have a value in mutable storage, and want to treat it as an immutable parameter without copying it first, you will need to provide some way to guarantee that it won't be mutated while being treated as immutable! There doesn't seem to be a definitive best way to do that (although the likes of Pony make a try at it).
-
Virtual Threads Arrive in JDK 21, Ushering a New Era of Concurrency
The love child of Erlang and Rust exists already: Pony.
https://www.ponylang.io
It really is the best of both languages... unfortunately, the main supporter of Pony seems to have stopped using it in favour of Rust though :D.
But if that's really what you want, Pony is your language. It definitely deserves more love.
- Programming language rule
-
Why Turborepo is migrating from Go to Rust – Vercel
You can actually try to have a magic language which "does not ignore decades of PL research" but you are likely to get either something broken or a project that is likely not going to release in our lifetime.
-
Show HN: Ractor – a Rust-based actor framework with clusters and supervisors
Never a bad time to plug Pony lang[1] - a safety-oriented actor-model language. In addition to the numerous safety guarantees, you also get a beautiful syntax and automatic memory management. Really a great language that often gets overshadowed by Rust's hype-turfing.
[1]: https://www.ponylang.io/
Akka.net
-
What is the fastest producer consumer model in C#
akka.net actors. Actors all the way! https://getakka.net
- .NET - iskustva s akka.net?
-
MassTransit with MSMQ vs RabbitMQ
If it's the former you may want to take a look at something like the actor model akka.net with persistent actors (https://getakka.net/articles/persistence/architecture.html). No need of an external message broker or mass transit (which is a wrapper over different message brokers). You could use sqllite for persisting the actors state to recover in case of a restart.
-
For .NET 6+, is there value in using NHibernate with Sprint.net or should I stick with EF Core and the usual supporting libraries?
Spring and Hibernate are the goto libraries in Java land and I suspect that's the primary motivation for your colleague's recommendations. It's quite easy to bulldoze someone less experienced with your ideas so be careful of that. I'd avoid both. They aren't bad libraries at all but they have a 'legacy' feel and it will make your application less future proof. Would a distributed system be viable? If so then I'd recommend Akka, there'a .NET port of it that's well supported and maintained.
-
Learning resource for seniors
Is akka a good alternative?
- Carl Hewitt has died [pdf]
-
Using functional extensions in production C# code?
However, I've found that sometimes, they are a little -too- functional. I'm a bit more preferential to Akka.Net's implementation of Option and Try, if only because they have good 'escape hatches' where you interrogate them in a more procedural manner.
-
Microsoft RulesEngine. Feedback from those that have used it in enterprise environments
This project is also what ultimately led to the creation of Akka.NET - I wrote an overview on how our application was built here: https://aaronstannard.com/markedup-akkadotnet/
-
Questions about network programming with C#
You may also want to take a look at queues (e.g. RabbitMQ) or even something like Akka.NET or Microsoft Orleans.
-
What does the .NET ecosystem offer in terms of distributed data processing frameworks?
From the title I immediately thought AKKA.NET or Orleans
What are some alternatives?
gleam - ⭐️ A friendly language for building type-safe, scalable systems!
protoactor-dotnet - Proto Actor - Ultra fast distributed actors for Go, C# and Java/Kotlin
Halide - a language for fast, portable data-parallel computation
Orleankka - Functional API for Microsoft Orleans http://orleanscontrib.github.io/Orleankka
prolog-to-minizinc - A Prolog-to-MiniZinc translator
Orleans - Cloud Native application framework for .NET
Phoenix - wxPython's Project Phoenix. A new implementation of wxPython, better, stronger, faster than he was before.
.NET port of LMAX Disruptor - Port of LMAX Disruptor to .NET
tab-rs - The intuitive, config-driven terminal multiplexer designed for software & systems engineers
.NEXT Raft
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
MBrace - MBrace Core Libraries & Runtime Foundations