Live data from Hacker News

The Sandstorm Team Is Joining Cloudflare

sandstorm.io

61–70 of 108 posts

Re: The Sandstorm Team Is Joining Cloudflare

#61

Best of luck, kenton! If anyone is looking for alternatives: http://alternativeto.net/software/sandstorm-io/ . I think Cozy, Yunohost, Cloudron, arkOS are the closest alternatives (Bitnami is about 1-click images and DO/linode are about cloud servers). Would be great to hear about other alternatives...

Unless I missed something, none of these are capability-safe designs, whereas Sandstorm is capability-safe on the wire up to the edge of Capn Proto.

Re: The Sandstorm Team Is Joining Cloudflare

#62
post #9

Hi all, I'm not sure how responsive I'll be able to be on this thread since I'm in orientation today. :) But, here's the things I expect to be repeating a lot: - Sandstorm is still an independent company, under control of Jade and myself. - Sandstorm is "my baby" and I'm not going to stop working on it just because I have a day job. Yes, it will slow down a bit -- but on the bright side, we were previously spending t…

> Sandstorm is still an independent company, under control of Jade and myself. Whenever I hear that I'm subvocalizing 'for now'. How do you see this in the longer term?

Contrast that with the problem for Sandstorm if they couldn't figure out how to fund the effort.

Re: The Sandstorm Team Is Joining Cloudflare

#63
post #60
post #58

Earlier quoted context omitted.

Can you provide a 'top 3' list of reasons to use Cap'n Proto over Protobufs?

1) Cap'n Proto doesn't encode/decode messages thus it's nuch cheaper for processing and memory management 2) protobuf in the proto3 design doesn't cary default values. So if you have a bool field and want to explicitly send false, well you have to change it to some other type or use the default values all the time 3) protobuf generates incredibly large serialization/deserialization support coce for each template. For…

Thanks. Those are pretty significant advantages. These things should be on the home page of the project. That's how smaller projects gain share.

Re: The Sandstorm Team Is Joining Cloudflare

#64
post #37

Earlier quoted context omitted.

As far as I can tell, Sandstorm did not get acquired or acquihired - Kenton, Jade, and others (?) as individuals all accepted job offers from Cloudflare.

Ah ok, so the team has joined cloudflare but the corporate entity continues with the original owners. So in some ways better than an acquihire and in some ways worse.

It seems almost universally better? I can't think of any acquirer that would be more successful with Sandstorm than the founders themselves. Nobody I can think of is aligned with "users own their data" and big enough / cares enough to help Sandstorm gain adoption.

Even Sandstorm not gaining traction with their B2B strategy is likely a blessing in disguise: with enterprise money coming in they would have felt a hard pull to do more things that enterprises like. No matter how much conviction you have, making payroll often trumps that.

Now, they've proven that the enterprise route doesn't work. My hope is that the project can continue to improve and gain traction to the point where it sets up or joins a foundation, then potentially try to restart a complementary commercial venture on top of that.

Re: The Sandstorm Team Is Joining Cloudflare

#65
post #60
post #58

Earlier quoted context omitted.

Can you provide a 'top 3' list of reasons to use Cap'n Proto over Protobufs?

1) Cap'n Proto doesn't encode/decode messages thus it's nuch cheaper for processing and memory management 2) protobuf in the proto3 design doesn't cary default values. So if you have a bool field and want to explicitly send false, well you have to change it to some other type or use the default values all the time 3) protobuf generates incredibly large serialization/deserialization support coce for each template. For…

re: "Doesn't encode/decode messages"

Does this mean that individual fields are encoded/decoded lazily?

Re: The Sandstorm Team Is Joining Cloudflare

#67
post #44
post #15

Earlier quoted context omitted.

Sandstorm takes apps that normally would need someone to run a server, breaks them down into the smallest shareable unit (a "grain"), and lets you host them all centrally, on the Sandstorm server. Whether that's the Oasis service, your own machines, or something in between. So instead of running a whole Gitlab server, you'd run a Sandstorm server that hosts Gitlab grains, each consisting of a single repository. Gitla…

> Whether that's the Oasis service, your own machines, or something in between. To clarify: does a "grain" just run in one place, or is each "grain" a cluster of containers that can be spread-scheduled between disparate regions (i.e. "the Oasis service" and "your own machines" at the same time)? And, if the latter, do the cluster nodes have awareness of their locations, and can take advantage of that?

I have honestly no idea, other than I know that the grains are not permanent resident processes. IOW when they are not in use, they spin down and do not actively consume resources other than disk.

I think the grain runs in one place, I think to use the container analog it would be one container, but as a point of clarification I believe that it is not using one of the container runtimes like docker or rkt that you will be familiar with, but uses its own sandboxing instead.

I have not tried running the newly opened up Oasis backend so I can't really speak toward how it works. My experience with a single server running Sandstorm has been good, painless automatic upgrades, I would expect from what I know about this team, that since it's their dogfood they made it taste good.

Re: The Sandstorm Team Is Joining Cloudflare

#68
post #60

Earlier quoted context omitted.

1) Cap'n Proto doesn't encode/decode messages thus it's nuch cheaper for processing and memory management 2) protobuf in the proto3 design doesn't cary default values. So if you have a bool field and want to explicitly send false, well you have to change it to some other type or use the default values all the time 3) protobuf generates incredibly large serialization/deserialization support coce for each template. For…

re: "Doesn't encode/decode messages" Does this mean that individual fields are encoded/decoded lazily?

Well, you could look at it that way. But the "encoding" is the same encoding that an "int" field in a struct uses, and "decoding" it is a trivial load instruction.

Re: The Sandstorm Team Is Joining Cloudflare

#69
post #64

Earlier quoted context omitted.

Ah ok, so the team has joined cloudflare but the corporate entity continues with the original owners. So in some ways better than an acquihire and in some ways worse.

It seems almost universally better? I can't think of any acquirer that would be more successful with Sandstorm than the founders themselves. Nobody I can think of is aligned with "users own their data" and big enough / cares enough to help Sandstorm gain adoption. Even Sandstorm not gaining traction with their B2B strategy is likely a blessing in disguise: with enterprise money coming in they would have felt a hard p…

> Now, they've proven that the enterprise route doesn't work.

Well, no... I don't think we proved it didn't work, only that we lacked the expertise to make it work. With more time and some good hiring I think we could have fixed the problem, but the investor money ran out, so...

Post reply on HN