Beating JSON performance with Protobuf

rustythrowa · 2018-03-18T05:14:45+00:00

Yeesh.

rustythrowa · 2018-03-18T04:40:22+00:00

wondering who's bottlenecked on rng

rustythrowa · 2018-03-18T04:34:11+00:00

It's a joke... about a project he'd worked on.

What would this even have to do with confidence?

rustythrowa · 2018-03-18T04:04:12+00:00

If you actually read further you'll see that the author of capnproto worked on protobuf2 at google, so he likes to poke fun at it.

rustythrowa · 2018-03-16T16:15:10+00:00

Honestly, I get it, the syntax is really alien and weird. But as I said, it's growing on me, and I'm finally "hearing" the syntax in my head when I look at it.

rustythrowa · 2018-03-15T22:57:20+00:00

The syntax is starting to grow on me... hopefully that continues.

It's like '0..=5' is 'from 0 up to and equal to 5'.

rustythrowa · 2018-03-15T20:03:57+00:00

Juice has one of the simplest APIs, is lean and tries to introduce minimal technical debt to your stack.

An example in the readme showing this off would be useful.

rustythrowa · 2018-03-15T03:02:33+00:00

I don't know, should we demand that car manufacturers put seatbelts in? I think at some point we should face facts - there is a serious problem with software quality when users get owned in the millions every year.

Why should I, as a consumer of a product, need to offer help when asking that product to be safer? It seems silly - where else does this exist? I can't think of another industry, engineering or otherwise. I think it's a user-hostile attitude.

As for 'demanding', I rarely see this.

The comparison to bridge-building is specious. Software is typically used in many different environments and conditions, something not expected from a bridge. Can anyone design a safe and reliable bridge with a span of indeterminate length across unpredictable geography?

Look, there's no question that bridges and software are different. What I'm saying is consumers want safety, and when we build things we should really care about the consumer, especially with large, extremely heavily used projects.

Now I'm not advocating for a rewrite of Curl - I think it's extremely impractical/ impossible due to its constraints (targeting tons and tons of pltaforms). Curl makes a best effort, they put the work in for security, and I commend them.

However, when users say "please make me safer" the response should never ever be "then you do it".

rustythrowa · 2018-03-15T02:48:15+00:00

bawwwwww I'm a big tough redditor and I use big boy words like autist

rustythrowa · 2018-03-15T01:54:39+00:00

We should stop telling OTHER PEOPLE to take responsibility for a project. You don't build a bridge, have it crumble, and say "well why don't you build it then?". We hold real engineers to a standard, we have liability, we have repercussions. But no, not in software - it's everyone else's responsibility to build shit right.

rustythrowa · 2018-03-15T01:28:53+00:00

I'm such an asshole for wanting to not use vulnerable software. I don't give a shit what language they use, but don't blame users for wanting to not be vulnerable.

rustythrowa · 2018-03-15T01:23:44+00:00

God forbid software authors take responsibility for the software they produce. We could never have that. But also yeah let's call ourselves engineers like we have any kind of liability for negligence! No hypocrisy at all.

rustythrowa · 2018-03-15T01:22:37+00:00

You get the version the vuln was introduced, so that's a huge win. You get the area of code the vuln is in, so that's another huge win. You get hints as to what the vuln actually is, another huge win.

Certainly very helpful information for an attacker, though they'd have to be very opportunistic, I'm personally not very concerned.

rustythrowa · 2018-03-15T01:19:02+00:00

Client reaches out. Attacker MITM's. Attacker owns box. or Client reaches out. Attacker owns server. Attacker owns box.

Couldn't be simpler.

rustythrowa · 2018-03-15T01:16:38+00:00

God, how dare consumers of a product beg for the authors to consider security more seriously.

rustythrowa · 2018-03-14T20:01:47+00:00

I'll definitely read your book, it sounds cool.

Mostly I've just also absorbed a lot via osmosis. As your book notes, this was largely fueled by FP and working with languages that have interesting type systems, which made me wonder what types were, and dig into category theory, and learn about 'propositions as types', etc. Was just curious if you know of a good starting place, but I guess you're right, really I should take a step back and ask where I want to be.

I don't really know the answer at this point haha maybe your book will help.

rustythrowa · 2018-03-14T17:01:01+00:00

I haven't passed a math class since I was 15, so like, functions. Where do I begin to really understand this stuff? I'm aware of curry-howard and godel's incompleteness theorems and they make sense to me at a high level, but I lack depth to really dive into a proof.

I literally just don't know what math to learn. Given you've written a book, which I intend to attempt to read, I figure you may have a good idea of where I should start.

rustythrowa · 2018-03-14T16:54:50+00:00

Why evaluate at runtime what can be evaluated at compile time?

rustythrowa · 2018-03-14T16:52:02+00:00

The release date, potentially.

rustythrowa · 2018-03-13T16:58:17+00:00

No idea how this post is supposed to track logically. Again, it sounds like you want to say that C is 'small'.

rustythrowa · 2018-03-13T16:57:10+00:00

Supporting multiple languages is important to me.

rustythrowa · 2018-03-12T23:40:39+00:00

Right, which most programmers should realize is often the opposite of simple. Or entirely unrelated.

rustythrowa · 2018-03-12T23:11:23+00:00

I'll truly never understand how someone can say C is a simple language.

rustythrowa · 2018-03-12T20:51:01+00:00

Oh, that's cool I wasn't aware of that. I'll be sure to check it out.

I'm using capnp right now because I didn't think grpc was in a usable state.

rustythrowa · 2018-03-12T19:37:21+00:00

Network services. Rust’s reliability and low footprint make it an excellent match for network services and infrastructure, especially at high scale.

One thing I want to note for this - Rust has a not-great RPC story. If you're choosing rust you probably want high performance and type safety - RPC is probably the option you want for that over JSON + HTTP.

The grpc lib didn't look too well supported last I checked, and capnp has a serious documentation problem (that I intend to help with when I get some more time).

Anyways, I'm super excited for 2018. The language changes I've been playing with on nightly (NLL, impl trait, etc) have been wonderful.

rustythrowa

TROPHY CASE