keygen-api VS jakt

I don't have an Elixir background, but I absolutely utilize pattern matching in my Ruby code bases:

- https://github.com/keygen-sh/typed_params/blob/4e4982b7d2b26...

- https://github.com/keygen-sh/typed_params/blob/4e4982b7d2b26...

- https://github.com/keygen-sh/keygen-api/blob/master/app/migr...

- https://github.com/keygen-sh/keygen-api/blob/36cd61db143cc1c...

- https://github.com/keygen-sh/typed_params/blob/4e4982b7d2b26...

I love it. I want even more pattern matching too, like with defp: https://bugs.ruby-lang.org/issues/19764.

Honestly, I don't have many resources to provide. I read a lot of policy tests via GitHub search (e.g. path:spec/policies/*/*.rb), but couldn't find anything that looked like what I wanted. I wrote the DSL as-needed in order to fully test my app's authz while migrating from Pundit to ActionPolicy.

It's not the prettiest when you actually look beneath the covers [0], but it does what I wanted -- provides a way to write exhaustive authz tests. Without the DSL, I probably wouldn't have written. The PR for said migration was massive [1], and was a precursor to going open source [2].

[0]: https://github.com/keygen-sh/keygen-api/blob/master/spec/sup...

[1]: https://github.com/keygen-sh/keygen-api/pull/647

[2]: https://github.com/keygen-sh/keygen-api/issues/644

Yes, I can see why you might make this argument. [1]

[1] https://github.com/keygen-sh/keygen-api/blob/master/LICENSE....

And not at all set on WorkOS. It just looked like the easiest way to set up SSO last time I researched the topic. Feel free to comment on the issue with any recommendations.

Since when can you run heroku pg:upgrade to switch database tiers? I was following an upgrade sequence I put together over the years [^0], but I guess Heroku automated this at some point? What would be really funny is if this had been possible all long...

[^0]: https://github.com/keygen-sh/keygen-api/blob/master/.notes/d...

Maybe use keygen-sh?

I run a business called Keygen [^0], and own the @keygen namespace on npm. We’re working on a Node SDK, so this isn’t good to hear. I’ll open up a discussion with them and see what we can do.

[^0]: https://keygen.sh

- org-2.php.pkg.github.com/package

I wonder if that had any impact on their decision.

[0]: https://github.com/keygen-sh/keygen-api/issues/490

SerenityOS is doing exactly that:

https://github.com/SerenityOS/serenity/tree/master/Ladybird

I also like their Jakt programming language:

https://github.com/SerenityOS/jakt

Though I'm more enthusiastic about Redox (doing it in Rust):

https://gitlab.redox-os.org/redox-os/redox/

It's very opinionated and SerenityOS-focused, but the language Jakt ( https://github.com/SerenityOS/jakt ) transpiles to C++, has memory safety and some very neat ideas for readability.

I love Rust, but its model and specifics would make it difficult to learn how to write code in other languages.

For low-level code, I think Carbon may fill that niche in the future. If it doesn't, C++ may be a good candidate once up-to-date books have been written and compilers actually support the modern spec. Classrooms/guides would need to move away from the still-lingering "C++ is C with classes" approach and use the standard library before that can be a reality, but this book[0] by Bjarne Stroustrup himself demonstrates the future C++ _could_ have if all the modern language features become usable.

In business, C++ will still be the domain of ancient clusterfucks compiled by MSVC++ 6 in many areas, similar to how most Java code is still built around Java 8 because that was the most recent stable version for many projects' lifecycle (and Oracle's decision to only ship JRE 8 to consumers doesn't help) and how .NET 4 is still taught in schools because the new and scary dotnet tool doesn't map 1-to-1 with the old way of working. I can't imagine microcontroller toolkits supporting a modern version of _any_ language in the first place.

However, if more people would learn modern C++ (or a replacement, like Carbon), I think this class of programming languages can have the same growth and hype Rust has enjoyed for the past years.

I'm keeping my eye on Carbon and Zig. Google's influence has managed to push Go to the forefront despite its many quirks, and Zig seems to be focused on doing "C, but right" rather than "C++, but right" which so far is looking pretty promising.

It's also fun to see Jakt[1] being developed in real time; I don't think it's a language that will be useful for production software any time soon, but on the other hand it's a language that actually produces binaries reliably (unlike pre-alpha Carbon or pre-release Zig, the latter exposing many problems after switching to a self-hosted compiler).

[0]: https://www.stroustrup.com/tour3.html

[1]: https://github.com/SerenityOS/jakt

About php, I have no problem of rewriting whole game for performance reasons once it is done and popular in low level language like https://github.com/SerenityOS/jakt but I think for now php is good and sufficient.

Jakt, pretty well designed (lots of ideas stolen from ML/Rust), but very immature

I think this thread might be interesting to the people here. The guy eventually started working on his own safe language, Jakt: https://github.com/SerenityOS/jakt