gleam
Shapeless
Our great sponsors
gleam | Shapeless | |
---|---|---|
92 | 13 | |
13,924 | 3,362 | |
58.7% | - | |
9.9 | 7.5 | |
5 days ago | 8 days ago | |
Rust | Scala | |
Apache License 2.0 | 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.
gleam
- Cranelift code generation comes to Rust
-
Inko Programming Language
I had been only following this language with some interest, I guess this was born in gitlab not sure if the creator(s) still work there. This is what I'd have wanted golang to be (albeit with GC when you do not have clear lifetimes).
But how would you differentiate yourself from https://gleam.run which can leverage the OTP, I'd be more interested if we can adapt Gleam to graalvm isolates so we can leverage the JVM ecosystem.
-
Switching to Elixir
I don't think the implementation itself is at fault, but yes, I do think that the design of dialyzer makes it an (at times) faulty type checker. The unfortunate reality of a type checker that fails sometimes is that it makes it mostly useless because you can never trust that it'll do the job.
To be clear, I've had it fail in a function where I've literally specced that very function to return a `binary` but I'm returning an `integer` in one of the cases. This is a very shallow context but it can still fail. Now add more functions, maybe one more `case`.
I think an entire rethink of type checking on the BEAM had to be done and that's why eqWalizer[0] was created and why Elixir is looking to add an actual sound, well-developed type checker. Gleam[1] I would assume is just a Hindley-Milner system so that's completely solid. `purerl`[2] is just PureScript for the BEAM so that's also Hindley-Milner, meaning it's solid. `purerl` has some performance issues caused by it compiling down to closures everywhere but if you can pay that cost it's actually pretty fantastic. With that said my bet for the best statically typed experience right now on the BEAM would be `gleam`.
- Gleam
- Unpacking Elixir: Resilience
-
Erlang/OTP 26.1 Released
If you don’t like the syntax highly recommend giving https://gleam.run a try
-
Elixir for Cynical Curmudgeons
If you're a fan of the ecosystem, but not of dynamic types, there are statically typed languages on BEAM, eg Gleam (https://gleam.run/)
-
Async rust – are we doing it all wrong?
Keep an eye on gleam lang if you’re not already. It’s a language with an ML inspired type system (like rust) that compiles to erlang. It is likely too nascent to be used in production (in terms of tooling, ecosystem, stability, etc).
- I hereby officially announce the Elixir type system effort is into development
Shapeless
-
Question regarding Recursive datatypes and cats typeclasses (Haskell to Scala)
Scala 2-only: * Shapeless (there is Shapeless for Scala 3 but less often needed as basic things are in Scala 3)
-
Fp libraries that target scala 3 exclusively?
I know that libraries like Scodec and shapeless were rewritten practically from scratch for Scala 3, taking advantage of the next syntax and internals, as well as protoquill - a Scala 3 implementation of Quill.
-
Delphi 11 Alexandria Has Been Released
please show me something like this: https://akka.io/ or this: https://zio.dev/ or this: https://github.com/milessabin/shapeless
-
6 Years of Professional Clojure
That largely depends on the type system. Languages like Haskell and Scala which have much more powerful type systems than C/Java/Go/etc absolutely do allow you to do those sorts of things. It is a bit harder to wrap your head around to be sure and there are some rough edges, but once you get the hang of it you can get the benefits of static typing with the flexibility of dynamic typing. See https://github.com/milessabin/shapeless or a project that I've been working on a lot lately https://github.com/zio/zio-schema.
-
Scala3: Does it provide a simplified way of doing n-term generic parameters?
Just use cats and use the apply syntax .mapN for this. Seriously. There isn't a way to do it without generating source code that I can see in the api. Scala 3's HList Tuples aren't like Shapeless 2's HLists and I can't figure out a way in the api to reduce the tuple members down from (A, B, C, D) into an E, generically, yet with Scala 3 poly functions, unlike what you could do in Shapeless 2 with HList
-
Scala: A Love Story
Scala has sparked a huge ecosystem of very high quality libraries (Cats, Scalaz, shapeless, to name but a few). I think a major reason for this is that Scala attracts developers who value the advantages of the JVM, but are fed up with the limitations of the Java programming language and understand the benefits of an expressive type system and functional programming.
-
Jam 0.0.4 got Scala 3 support
I also investigated shapeless3 macroses: https://github.com/milessabin/shapeless/tree/shapeless-3/modules, but they are more about derivation than reflection. And probably that is all I found.
-
Why Learn Haskell?
I'm not sure where is the line between extensive and basic knowledge. Here is my more detailed exposure:
In commercial context:
* Of strongly typed ones only Scala (with [shapeless]). Can reluctantly throw in Kotlin as well for it's amazing structured concurrency.
In non-commercial context:
* Went through a few chapters of [Software Foundations] doing Coq proofs.
* Worked through most of the [Types and Programming Languages] (writing typecheckers in Ocaml)
* 3 services in Haskell (1 on Scotty, 2 on Servant). Loved persistent+esqueleto for the ORM layer, disliked Opaleye.
* 2 projects in PureScript (1 with Halogen, 1 with React bindings).
* 1 project in ReasonML (Ocaml).
-
> I am afraid there is no way back for me
I see where you are coming from. In my case I can alternate between "I want all invariants properly expressed and checked" and "I just want to ship that barely-working piece of junk and iterate on it". I learned to adjust depending on organization needs. IMO, for many orgs, especially startups/scaleups, the latter is often the more fitting way. With that in mind, I'm willing to trade the guiding hand of great type systems for other productivity aspects (amazing runtime and cohesive web framework in Elixir's case).
[shapeless]: https://github.com/milessabin/shapeless
[Software Foundations]: https://softwarefoundations.cis.upenn.edu/
[Types and Programming Languages]: https://www.cis.upenn.edu/~bcpierce/tapl/
What are some alternatives?
cats - Lightweight, modular, and extensible library for functional programming.
are-we-fast-yet - Are We Fast Yet? Comparing Language Implementations with Objects, Closures, and Arrays
magnolia - Easy, fast, transparent generic derivation of typeclass instances
Monocle - Optics library for Scala
Scalaz - Principled Functional Programming in Scala
web3.js - Collection of comprehensive TypeScript libraries for Interaction with the Ethereum JSON RPC API and utility functions.
Chimney - Scala library for boilerplate-free, type-safe data transformations
scala-newtype - NewTypes for Scala with no runtime overhead
Rustler - Safe Rust bridge for creating Erlang NIF functions
scala.meta - Library to read, analyze, transform and generate Scala programs
ponyc - Pony is an open-source, actor-model, capabilities-secure, high performance programming language
nx - Multi-dimensional arrays (tensors) and numerical definitions for Elixir