Joda-Beans
ponyc
Our great sponsors
Joda-Beans | ponyc | |
---|---|---|
2 | 61 | |
141 | 5,590 | |
0.7% | 0.6% | |
6.2 | 9.3 | |
8 days ago | 27 days ago | |
Java | C | |
Apache License 2.0 | 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.
Joda-Beans
-
Don’t call it a comeback: Why Java is still champ
That means I don't forget about fields (as can happen if you're just doing `person.setX()` all the time). It's easy to see what is what when reading it. I can delete fields I don't want to initialize at the time. Yes, maybe immutable objects are the One True Way, but C# lets me choose (I can label properties with an initializer `init` rather than a setter `set` and then they're immutable).
Kotlin offers stuff like this too because it's really useful toward creating code that's easy to create and maintain. Go also lets you initialize structs in a similar fashion.
Java has come back to us a decade or more late with records. They're not bad, but they're only offering one thing. They don't cover what C#, Kotlin, Go, and other languages have offered for so long.
The annoying thing about Java is that it doesn't feel pragmatic a lot of the time. It feels like the language hates stealing ideas from others. It's Java: people steal ideas from Java, not the other way around. People do crazy things just to get POJOs including Immutables (http://immutables.github.io), AutoValue (https://github.com/google/auto/), Lombok (https://projectlombok.org), Joda Beans (https://www.joda.org/joda-beans/), and maybe more. They generate lots of code at compile time or do funky runtime stuff.
It just feels like Java misses the pragmatic stuff and still kinda doesn't want to handle that. I feel a bit silly harping on things like POJOs and setting data on a new object, but that's a big part of day-to-day stuff and it definitely pushes users away from Java towards languages that seem "better" simply because they don't have Java's oddly strong attachment to not offering simple value objects. Yes, again, records do something - but it feels like Java ignored how people are using Kotlin, Go, C#, and more and didn't go for something that would have been as widely applicable and pragmatic as it could have been.
Java has a lot of great stuff like great GCs (yes), lots of cool research, great performance, and Project Loom is really exciting. I just wish the language would lean a little more practical.
-
With the recent changes to Discord's branding, here's a proposition for a new tagline for C#. Thoughts?
I know I've been talking about properties a bunch, but let's look at Java. Java Beans are terrible - so terrible that the community has a number of workarounds. Immutables (https://immutables.github.io) lets you generate builders, Lombok (https://projectlombok.org) has their annotations that do runtime and IDE magic, there's Joda-Beans (https://www.joda.org/joda-beans/), there's the new Java Records if you want immutable-only and non-compatibility with lots of libraries, there are people using Kotlin for their data classes and Java for other things... Properties are this simple thing that lets C# work with the whole getter/setter pattern without being horribly annoying - there's just this weird { get; set; } thing that I can ignore because I don't care.
ponyc
-
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.
-
Virtual Threads Arrive in JDK 21, Ushering a New Era of Concurrency
The love child of Erlang and Rust exists already: Pony.
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.
-
Why Turborepo is migrating from Go to Rust – Vercel
Until next shiny thing. Like Zig, or Pony. They have a very good points about migrating, but that is not one of them.
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.
- Carl Hewitt has died [pdf]
-
Pony Programming Language
There are a few, but you are right that they could be more accessible: https://github.com/ponylang/ponyc/tree/main/examples
(I had the same problem)
-
Safely writing code that isn't thread-safe: An under-appreciated Rust feature
Are you sure that the project is dead? I see movement in the main repository and the last release dates to 9 days ago: https://github.com/ponylang/ponyc/releases/tag/0.52.1
What are some alternatives?
javawriter - A Java API for generating .java source files.
FreeBuilder - Automatic generation of the Builder pattern for Java
gleam - ⭐️ A friendly language for building type-safe, scalable systems!
Halide - a language for fast, portable data-parallel computation
prolog-to-minizinc - A Prolog-to-MiniZinc translator
SDMLib
Phoenix - wxPython's Project Phoenix. A new implementation of wxPython, better, stronger, faster than he was before.
NetworkParser - Framework for serialization to Json, XML, Byte and Excel, therefore an oviparous wool milk sow J
tab-rs - The intuitive, config-driven terminal multiplexer designed for software & systems engineers
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).
mrustc - Alternative rust compiler (re-implementation)
Celluloid - Actor-based concurrent object framework for Ruby