-
Hey is there a #Hackerspace #Erfa in #Braunschweig?
-
the other thing I don’t really love is the big prelude, #jakt has.
By default you can access a lot of things from the standard library, like the File object, which allows file IO.
While it might be great for discoverability while writing, it compromises jakt first goal: readability.
When opening a jakt file, one can not immediately see what the content roughly does. Compared to languages like go or rust with a small prelude and imports, one can see at the top of the file what’s going on.
-
#jakt seems to be such a nice language. Reference counted, modern, memory safe and explicit, but there are two things I don’t really like. Why do throwing functions propagate errors automatically?
Okay, yes, the LSP indicates a throwing function with putting a try overlay in front of it, but this doesn’t prevent overlocking it in daily software dev or not having a LSP.
I’d rather be a but more explicit and have the compiler to require a “try” keyword in-front of a throwing function call.
🧵 -
Okay, but why can’t we have a #Swift or #Jakt like language, which compiles to natives code, enforces error handling, uses errors as values, has no inheritance, but interfaces like go, removes Null and uses Atomic Reference Counting?
Swift comes close, but has classes and a really bad cross platform story and jakt looks good but still has inheritance, because it is designed for building browsers.
Currently jakt bubbles errors automatically, which I‘m not a fan of. Imo it’s to easy to miss one
-
#TIL that you don’t need an #auth library like #Laravel’s fortify. Just host an AuthN provider and implement #oidc or #ldap.
If you ship a desktop app, you don’t need #AuthN because the user is authenticated through their login into their computer.
If you ship to a business, they will have an LDAP or OIDC server or will host one when needed.
If you ship an app with online account, you can just host #Keycloak or #Authentic or pay #auth0.
More below: