Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
q3k
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
65 ms
·
811.
▲
by
q3k
6y ago
Kubernetes clusters can be upgraded in place, though? GKE definitely allows you to do that.
812.
▲
by
q3k
6y ago
Does DPDK actually let you not have to DMA packet data over to the system memory and back?
813.
▲
by
q3k
6y ago
How is Protobuf 'overly complicated'? I'm not talking about gRPC here - because trying to compare bare ASN.1 and gRPC is just dishonest. This is especially rich when you're comparing protobuf to ASN.1 - which is probably
814.
▲
by
q3k
6y ago
Shitposting on Twitter makes for bad SEO :).
815.
▲
by
q3k
6y ago
Seems to be in the same ballpark as when I got ~3.09Gbps on the Pi4's PCIe, but on a single 10G link: https://twitter.com/q3k/status/1225588859716632576
816.
▲
by
q3k
6y ago
Here's the kicker: while this might sensible to you, some JSON implementations out there will reject duplicate fields (fail a parse completely), and the RFC does not even specify what is the correct behavior (override previous, ignore
817.
▲
by
q3k
6y ago
Sure, gRPC is no magic bullet that will solve all issues across your stack, but it is still a very solid tool/library. Using it instead of REST allows you quickly solve the easy problems (sending typed messages across the wire) while l
818.
▲
by
q3k
6y ago
There's grpcurl and other similar tools for when you just want to run a simple gRPC request against a server. If you server runs the reflection service, it will also let you inspect the schema of whatever is running on a given endpoint
819.
▲
by
q3k
6y ago
It's one of those 'simple at first glace' standards. If you want to confuse someone who advocates for JSON's 'simplicity' as a feature, ask them what happens when their favorite JSON deserializer receives repea
820.
▲
by
q3k
6y ago
> The auth story isn't very clear. Do you use the out of band setup or add tokens in every single RPC? I think it's actually quite well documented. [1] You can have out-of-band authentication data per-connection ('per-chan
821.
▲
by
q3k
6y ago
No, gRPC/protobuf instead provides you with ways to evolve your schema easily in the IDL and the result on the wire, without breaking either side. You can rename fields (but keep the tag number and therefore wire format compatibility),
822.
▲
by
q3k
6y ago
There is some support for that [1]. I prefer to use native binary gRPC because: 1) REST verb/code mapping is too arbitrary for my taste, I prefer explicit verbs in RPC method names and error codes explicitly designed for RPC [2] and on
823.
▲
by
q3k
6y ago
Sure. You would use gRPC when: - You want to have inter-service RPC. - You want not only unary calls, but also bidirectional streaming. - You want a well-defined schema for your RPC data and methods. - You want a cross-lan
824.
▲
by
q3k
6y ago
It's a generic RPC protocol based on a well-enough-typed serialization format (protobuf) that is battle-tested. You'd use it where you'd use REST/API/JSONRPC/... Compared to plain JSON/REST RPC, it has all
825.
▲
by
q3k
6y ago
To build Bazel from source in an environment where you don't want to use any Internet binaries, you need a Java built from source. Needing a Java is painful. You also need a Bazel to build Bazel. And Bazel's build system itself II
826.
▲
by
q3k
6y ago
Another fun thing you can do is to do another clone of the llvm-bazel repo, build that using Bazel again. Things should've cached correctly and the rebuild from a totally different checkout should be pretty much instant, as long as you
827.
▲
by
q3k
6y ago
> If Google won't eat their own dogfood, it doesn't inspire much confidence. Chromium's gn started being prototyped in 2013 [1]. Android's soong started being developed in June 2015 [2]. Bazel's first open source
828.
▲
by
q3k
6y ago
Not as far as I understand. It's closer to CMake/Meson than to Bazel.
829.
▲
by
q3k
6y ago
In practice, this isn't generally noticeable. Bazel is pretty damn fast, and even ships with its own JVM so installing it is pretty much painless. I agree on the bootstrapping issues resulting from that, though.
830.
▲
by
q3k
6y ago
Not every package (especially core system packages, like zlib/openssl/glibc/...) are on GitHub and want to pull in Bazel buildfiles into their source tree. As such, there's no guaranteed canonical-upstream-repo:buildfile
831.
▲
by
q3k
6y ago
I'm okay with it being slightly more difficult to get started with, in return for higher productivity in the long run, yes. Right now, after spending a similar amount of time both with GitHub PRs (and Gitlab MRs) and Gerrit, I still fi
832.
▲
by
q3k
6y ago
Right, so is Wikimedia going to pay $$$ to GitLab for one of the more advanced licenses?
833.
▲
by
q3k
6y ago
The nice UI for review works well exactly because it limits the functionality available to users and enforces a particular commit model. If you don't do that, you get the code review mess that are Github/GitLab PRs/MRs - diff
834.
▲
by
q3k
6y ago
They are still very limited when it comes to functionality though - only the first column in https://about.gitlab.com/pricing/self-managed/feature-compar... , right?
835.
▲
by
q3k
6y ago
I really don't mind the Gerrit UX - it seems to be optimized for daily use by programmers, not for onboarding speed. That's a tradeoff I'm very much okay with.
836.
▲
by
q3k
6y ago
Clear mapping of change request == commit, allowing for easy building of multiple in flight change requests, rearranging them by using git rebase, updating with push to refs/for/master. Easy diffing between states of the CR (patch
837.
▲
by
q3k
6y ago
This is sad. In my experience, Gerrit is a much better code review system than Gitlab merge requests. But it is different from what people are used to.
838.
▲
by
q3k
6y ago
Yep. I use Go precisely because it's boring.
839.
▲
by
q3k
6y ago
Considering how Apple doesn't want either OpenGL or Vulkan on macOS you shouldn't be surprised.
840.
▲
by
q3k
6y ago
Here's a git mirror of the entire repo history up the the latest commit hash that I'm aware of. Compare against the commit hash on Google Webcache [1] for safety: git clone https://code.hackerspace.pl/q3k/
More ›