Lionel_Debroux_ has quit [Ping timeout: 276 seconds]
rafaelmartins has quit [Remote host closed the connection]
rafaelmartins has joined #sandstorm
bemasc has quit [Read error: Connection reset by peer]
bemasc has joined #sandstorm
admine_ has joined #sandstorm
admine__ has quit [Ping timeout: 250 seconds]
admine__ has joined #sandstorm
admine_ has quit [Ping timeout: 250 seconds]
heanpie has joined #sandstorm
heanpie has quit [Client Quit]
jemc has joined #sandstorm
admine_ has joined #sandstorm
admine__ has quit [Ping timeout: 244 seconds]
admine__ has joined #sandstorm
admine_ has quit [Ping timeout: 260 seconds]
jemc has quit [Ping timeout: 265 seconds]
admine_ has joined #sandstorm
admine__ has quit [Ping timeout: 240 seconds]
frigginglorious has quit [Quit: frigginglorious]
frigginglorious has joined #sandstorm
frigginglorious has quit [Client Quit]
Telesight has joined #sandstorm
lukexj has quit [Ping timeout: 240 seconds]
lukexj has joined #sandstorm
lukexj has left #sandstorm ["Leaving"]
nolski has quit [Ping timeout: 240 seconds]
nolski has joined #sandstorm
<mrdomino>
dwrensha: works except i'm missing the key for spk pack, which is what you'd probably expect
<dwrensha>
nice
<dwrensha>
`spk keygen` makes a new one
<mrdomino>
i'm half-tempted to run some benchmarks on boot time across various languages and frameworks. this doesn't seem to be something anyone has cared about that much, and sandstorm makes it more relevant than it was before.
<mrdomino>
oh cool, collections can contain themselves
<zarvox>
Wanna put on your capnproto-rust hat, jump in, and indicate that it's not abandoned, that we're seeing growing usage, and that Sandstorm.io uses it extensively in production? :D
<dwrensha>
yeah, I should do that
<zarvox>
I'd ask kentonv, but he's still (rightly) vacationing
jemc has joined #sandstorm
<jparyani>
GauntletWizard: awesome!
sydney_untangle has joined #sandstorm
sydney_untangle has quit [Read error: Connection reset by peer]
sydney_untangle has joined #sandstorm
guiniol has left #sandstorm [#sandstorm]
kxra has quit [Ping timeout: 258 seconds]
kxra has joined #sandstorm
Telesight has quit [Remote host closed the connection]
<asheesh>
Cap'n Proto probably seems abandoned because we don't do releases.
<asheesh>
IMHO we should probably stop pretending we can ever do the work required to test/fix on Windows, and then we can release capnproto every week along with Sandstorm.
<asheesh>
We should also use appveyor in capnproto.
<maurer>
asheesh: On a personal note as a user of capnproto outside sandstorm, while I'd prefer to see more releases of capnproto, I would also really prefer slightly rarer "truly stable" releases of capnproto
<digitalcircuit>
Though I've not investigated capnproto's requirements, AppVeyor's worked pretty well for Quassel IRC (C++/Qt), and AppVeyor recently rolled out faster build machines, too.
<maurer>
asheesh: I think that a release channel mechanism makes a lot of sense for Sandstorm, since it is primarily a user-facing product
<maurer>
asheesh: As a primarily dev-facing product, I feel like the capnproto release strategy might benefit from a different approach
<maurer>
asheesh: (that said, it would be cool to get a new release out so it's not just "guess a git revision and hope it's good)
<asheesh>
Yeah; maybe it makes sense to mark those as "beta" releases or something?
<asheesh>
Or "auto releases"
<maurer>
asheesh: Fine by me, I just want something as a dev where I can be on latest stable for longer than it takes me to make a serious change to my own project :P
<asheesh>
The downside is that if you do that, then you'll never support the new capnproto features that Sandstorm apps need.
<asheesh>
FWIW my personal perspective here is, "How do I make https://docs.sandstorm.io/en/latest/developing/ as reliable as possible for Sandstorm app authors?" which happens to require that those apps use fairly recent capnproto, more recent than v0.5.3.
<asheesh>
Yours might be "Cap'n Proto 0.5.3 is great, and everyone stop telling me to integrate new upstream releases, I'm fine" (-:
<maurer>
asheesh: So, for that I think what would make more sense would be a sort of dual release setup
<maurer>
asheesh: where you cut a "release" of capnproto every time you cut a new release of sandstorm, but also have a tru stable version
<maurer>
And no, I don't think "Cap'n Proto 0.5.3 is great, I don't want to upgrade ever"
<asheesh>
OK (-:
<maurer>
I'm trying to think of a similar example
<maurer>
but the use case I'm considering here is for people who want to use a capnproto rpc layer but are not using it to write sandstorm components
<maurer>
You could even do something like
<maurer>
v0.5.3-sandstorm39
<maurer>
v0.5.3-sandstorm40
<maurer>
...
<maurer>
v0.5.4
<asheesh>
Hmm, interesting!
<asheesh>
v0.5.3-sandstorm180
<asheesh>
(then the sandstorm version number gets embedded in there)
<maurer>
and so the -sandstorm releases are believed good, but are not necessarily going to have the full documentation scan/fuzzing done to a major release
<maurer>
yeah
<maurer>
also means that for a givne revision of sandstorm, you know which release of capnp it was tested against
<maurer>
In any case, didn't mean to throw a tantrum, just some input (would also love my canonicalization to hit capnproto stable :P)
<asheesh>
: D
<asheesh>
No prob at all; the input is super useful.
<asheesh>
I need to AFK to grab lunch before I forget to entirely.
jemc has quit [Ping timeout: 240 seconds]
jemc has joined #sandstorm
frigginglorious has quit [Quit: frigginglorious]
frigginglorious has joined #sandstorm
kxra has quit [Ping timeout: 258 seconds]
amyers has joined #sandstorm
amyers has quit [Remote host closed the connection]