Have to love the party-invite example on the Pony language website! Does a great job showing off.
Have to love the party-invite example on the Pony language website! Does a great job showing off.
#Ponylang gets a templating engine
This looks like it's pretty neat.
https://www.ponylang.io/blog/2026/03/pony-gets-a-template-engine/#where-this-is-all-going
Pony is an open-source, object-oriented, actor-model, capabilities-secure, high-performance programming language
Is Lemmy "competitive" with Discourse/Zulip in features? I would love to participate in various forums (Haiku OS, for sure; others too, like Pony which is on Zulip), but am loath to create log-ins on each. Is the Discourse way of not going for federation important for discussion forums?
#Lemmy #HaikuOS #Discourse #PonyLang #Zulip
CC @pulkomandy @mmu_man @begasus
I'm in the process of (procrastinating on) porting some code on the #ESP32 from Arduino IDE to #platformio. My current implementation occasionally crashes, and I'm not sure my rewrite won't.
I just remembered, some years ago I touched #ponylang, which has this interesting concept of capabilities built into the language: all of the OS-level functions like networking, filesystem and so on require a special parameter called a "capability" (which comes in various flavours), optimized away by the compiler, which guarantees that the function can, transitively, only be called by code which holds the appropriate capability.
If that existed on my platform and was extended conceptually to things like FreeRTOS, I would be confident I could safely call some 3rd party or even my own code from some handler, because i knew it couldn't allocate memory or sleep or do thread things.
One of the other things, I don't really like in #PonyLang, is its magic, seen in:
– "Structural subtyping": There's no explicit connection between the interface and its use (what could possibly go wrong?)
– "use": When importing something, here, also, is no explicit connection, what is used from that import (no "use 'a'; env.out.print a.b" or "use b from 'a'; env.out.print b")
I wish, this advice from #PonyLang would be applied to #webExtension/ #browserExtension stores, as well as #browserPermissions, and similar stuff