ChanServ changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things Sandstorm and Cap'n Proto. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev | Channel logs available at https://libera.irclog.whitequark.org/sandstorm
yarmo has quit [Quit: yarmo]
yarmo has joined #sandstorm
tian2992 has quit [Read error: Connection reset by peer]
tian2992 has joined #sandstorm
tian2992 has quit [Ping timeout: 248 seconds]
tian2992 has joined #sandstorm
yarmo has quit [Read error: Connection reset by peer]
yarmo has joined #sandstorm
ptman[m] has joined #sandstorm
<ptman[m]> Hi! How is sandstorm on arm64? https://paul.totterman.name/posts/free-clouds/
<ocdtrekkie> Hey Paul ! Sandstorm currently isn't available for ARM processors. It is something that may eventually happen someday, but not just requires we build the platform to support it, but build each and every app for multiple processor architectures as well.
<ptman[m]> do you have customized images? or can you just use upstream images? many of those are already available on arm64
<ptman[m]> for rpi etc.
<ocdtrekkie> Sandstorm is significantly different than the average container platform, apps have to be explicitly designed for or packaged for it.
<ptman[m]> ok
<ocdtrekkie> Generally my recommendation for hardware is like a small form factor enterprise desktop being resold off-lease. Often a good sixth or seventh generation Intel machine in a very compact package can be found for not much more than a Raspberry Pi, with relatively similar power efficiency.
<TimMc> ptman[m]: I run Sandstorm on a salvaged laptop a neighbor was throwing out. It's well over 10 years old. Runs fine.
strugee has quit [Quit: ZNC - http://znc.in]
strugee has joined #sandstorm
strugee has quit [Quit: ZNC - http://znc.in]
strugee_ has joined #sandstorm
<jonesv> I hate to sound like I'm begging for help, but... is there someone here who would feel like skimming through https://github.com/capnproto/capnproto/pull/1460 and see if it can be easily recognized that most of the code is easy boilerplate that looks like the normal streams?
<jonesv> I'm taking the opportunity now because the PR has been open for almost a year, and kentonv actually just reacted on it an hour ago. I am trying to see if someone he trusts would be willing to get more context about it, to decide if this is a complicated PR or not? My intuition is that it is mostly boilerplate and a couple simple changes, but then again I wrote the PR...
<jonesv> Most of the PR is very similar to https://github.com/capnproto/capnproto/pull/825. The "realtime" parts are actually simpler, and there is just a difference in the protocol which amounts to keeping a list of ids, again super simple
<jonesv> Really for most of the lines, if you see "RealtimeSomething", you can look 5 lines above and you'll see an equivalent "StreamSomething", so that's boilerplate.
<jonesv> I would even be happy to take out the actual code in some kind of external document and explain it. It's really just a list and a couple `if` statements.
drkokandy has quit [Ping timeout: 248 seconds]
drkokandy has joined #sandstorm