eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

214
active users

#Zig

0 posts0 participants0 posts today

#ReleaseMonday — New version (v0.27.0) of thi.ng/genart-api, a platform-independent extensible API for browser-based computational/algorithmic/generative art projects:

This version features an overhaul of the platform provided PRNG (pseudo-random number generator) handling and makes it easier to create multiple PRNGs for artworks which require/desire them...

Related section in the README:
github.com/thi-ng/genart-api/b

Also, just as a reminder, the project has:

- no external dependencies
- adapters for 3 art platforms (EditArt, fxhash, Layer)
- 6 example projects
- testing/dev sandbox with two parameter editors
- WebAssembly bindings & demo (currently for #Zig only)

Happy coding! :)

thi.ng/genart-apithi.ng/genart-api

pretty stoked having pushed a huge update to github.com/stef/klutshnik

it is now all based on liboprf.

rewrote the server in #zig, the python client has also been completely rewritten. threw out the macaroons and the opaque-storage back-end, this simplified and made the whole thing a bit more secure also.

still some work left before this can go into production, but this is a big leap already. pheeew.

this work is funded by #nlnet / #ngi0

GitHubGitHub - stef/klutshnik: data-at-rest encryption KMS server and clientdata-at-rest encryption KMS server and client. Contribute to stef/klutshnik development by creating an account on GitHub.

hesitating between writing the klutshnik.info server in c or in #zig. i'd prefer zig as it seems to shut up people about memory safety, but then the core would still be liboprf which is written in c already. and it would make deployment more difficult, since #zig is not packaged in debian and other major distros. so i guess using zig would only be 4 cosmetic/populist reasons, and at the same time it would limit deployment. what should i do (no rust/go are not options)

klutshnik.infoProject Klutshnikctrlc.hu

Hey I'm still looking for work.
I've applied to a lot of places in my area and I'm getting nothing.

I'm a programmer at heart, but I've also been looking for regular entry-level jobs because there haven't been any coding positions open at my level as far as I could tell.

If you can offer me a job, it might save my butt. And if you can't offer me a job, could you at least share this post?

I live 30 minutes away from Bellevue if that helps.

Ooooooooooooh.

#Zig files are, themselves, structs.

This is awesome, and explains some of my confusion around namespacing and stuff.

Also: custom formatters for structs? So nice. Love the member accessing syntax.

Hot damn I haven't been this excited about a language in a few years.

@bortzmeyer Zig is one of three languages I have my eye on!

- #Zig - Procedural and easier to read than C.
- #Haskell - Functional in the extreme.
- #Rakulang - Can be functional, can be procedural, can be OO. Fantastic grammar / #regex model.

I think they complement each other. Every Haskell guy I have introduced to Raku has loved it. I've known a few people who use Zig when they don't feel like being purely functional.

Dear LazyWeb: is there a C/C++, #Rust or #Zig equivalent of #SciPy’s `stats` module for statistical analysis? Namely:
• a collection of common PDFs (probability density functions);
• MLE (maximum likelihood estimation) for these common distributions;
• KDE (kernel density estimation).

SciPy’s API is a pleasure to work with. Anything that comes close but usable from C/C++/Rust/Zig would make my life so much easier. Boosts appreciated for visibility.