ruby.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
If you are interested in the Ruby programming language, come join us! Tell us about yourself when signing up. If you just want to join Mastodon, another server will be a better place for you.

Administered by:

Server stats:

1.1K
active users

#rc

0 posts0 participants0 posts today

The year was 2005. I had an RC obsession and a lot of money to burn. This is a Traxxas e-Maxx, probably one of the first fitted with $600 worth of LiPo batteries and a 24vdc power system. I used a Battlebots ESC. This thing was stupid for its day. I still have it. #rc #remotecontrol

Replied in thread

@argv_minus_one @quixoticgeek @hector @cstross

It remains as simple. #s6, perp, runit, nosh, and even daemontools have simple chaining tools for the attributes and suchlike, and the original daemontools was doing restart on failure and logging, with tools for reporting service status, over a decade before systemd was invented, and before even upstart was.

A lot of the arguments about how great service units are are based solely upon van Smoorenburg #rc as a comparand, which is a fallacy.

No, RC Rush isn't discounted in the Steam Spring sale BUT if you have a VR headset and you like RC cars, then it's totally worth full price!! Even more so if you like supporting small indie developers like me. Check out the reviews from lots of people who paid full price! They love it! And so do I, but I'm bias of course. Look for yourself. Lots of trucks, lots of levels and lots of PC VR racing fun! store.steampowered.com/app/165 #NonSale #NotOnSale #SteamSale #VR #RC #RCRush #indiegame #indiedev

store.steampowered.comRC Rush on SteamRC Rush is an exciting arcade racing game featuring radio controlled trucks. Unlock trucks in grand prix cups, win races in campaign mode to unlock campaign events, compete in head to head battles to unlock even more trucks and level up your way to becoming the ultimate RC champion!

Was stuck the past week(s) in my #lisp implementation in #zig on #closures, as they provide an real challange with their capturing properties. Espc bc I didn't wanted to resort to using things like arbitary "rules" to restrict the language only for closure to work, or already implementing a tracing #garbagecollector for this.

I rather choose to use #ARC (Atomically Reference counting) for this, which comes with a few problems. And as I found nobody that has solved this problem, I've come up with a solution to it myself: 'Switchable references with strongchain elemination'. A bit bulky name, and the technique is still in it's beginning, but when implemented in rust the compiler dosnt complain and valgrind dosn't detects any leaks.

I've written a fairly big blogpost about it too, including not only the whole explanation how it works but also alternatives I've considered. Check it out if you're interested!

Now I only need to translate it over to zig, but hopefully that dosnt take so long x3

blog.lapyst.devRollinglisp 001 - Of closures, mutability and switchable references - Mai Lapyst's Blog