Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
q3k
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
29 ms
·
481.
▲
by
q3k
5y ago
The cred isn’t to stroke a researcher’s ego, it’s because the alternative is to not get to do any research. Or to not have access to research institutes. Or to not eat. Privileged researchers in areas that aren’t as affected by this problem
482.
▲
by
q3k
5y ago
There's more choice than just 'megacity and walk everywhere' and 'bumfuck nowhere and drive everywhere'. Small/medium towns with a fairly dense downtown/market square exist, and while yes, it's more u
483.
▲
by
q3k
5y ago
Yeah, it seems like we agree :).
484.
▲
by
q3k
5y ago
... socially, too. That part sucked.
485.
▲
by
q3k
5y ago
> when they should be able to kick the app over the wall and let infra ensure that the app is deployed in two separate PCR zones with the failover plan etc, which should itself be mostly automated Not entirely - the developers should act
486.
▲
by
q3k
5y ago
> What exactly are these "peer bonuses"? Is it real? Is it what I think it is? Each month, you can nominate another employee for a small bonus. This is designed to be given to coworkers who have gone above and beyond what was e
487.
▲
by
q3k
5y ago
People with HA production experience can easily vibe with points made by Broccoli Man. Yes, these things make a lot of sense if you actually want to get code running reliably, especially at scale (organizational and userbase). But we must n
488.
▲
by
q3k
5y ago
IMO/IME it's the clash between tooling, systems and and processes designed for running long-term highly scalable and reliable services maintained by teams in multiple geographical locations and used by billions of people; and gree
489.
▲
by
q3k
5y ago
> It's no different to phones, consoles, etc. You can use a Nintendo Switch or an Android phone without an online account.
490.
▲
by
q3k
5y ago
This post is a good reminder to never fall for “I don't want to cause offense, I want to understand the causes of difference.” again.
491.
▲
by
q3k
5y ago
'W' in Polish is already used, but for a different sound - it's pronounced like the English 'v'. 'V' in turn is not present the Polish alphabet (in the sense of it not being present in words of Polish orig
492.
▲
by
q3k
5y ago
You might enjoy this: https://archive.org/details/sonda
493.
▲
by
q3k
5y ago
> Can Ł have an alternative representation? Nope. Neither can ź, ć, ś, ą or ę. You can, and people do write them as z, c, s, a and e when writing in a restriced character set, but that is not 'correct' and is not a bijection, i
494.
▲
by
q3k
5y ago
It seems that you're implying computers are universally american and therefore people are expected to speak/use/adapt to american.
495.
▲
by
q3k
5y ago
> When you have non-standard characters in your name 'standard' by what measure? Ł is more standard than X or Q in the polish alphabet. ~ Sincerely, a person whose name contains „ń” and therefore had to deal with this bullshit
496.
▲
by
q3k
5y ago
Especially bundling these together as equally bad/legacy is weird. LDAP itself can actually be quite easy to understand and work with if you limit yourself to a useful subset of functionality, ie. a account/group directory. Any Ke
497.
▲
by
q3k
5y ago
There's two things: 1) Text templating YAML is just bad. It's the serialized format of some structured data - instead of templating its text representation (and dealing with quoting, nindent, stringly-typed variables, and general
498.
▲
by
q3k
5y ago
> ... advocate for this. All what you are describing, which is basically what every hardcore k8s user/evangelist will tell you to do, it's reimplementing many, if not all, the features a Cloud provider is already giving you in
499.
▲
by
q3k
5y ago
It should've been, and it can be. There's nothing official or special about Helm, just don't use it.
500.
▲
by
q3k
5y ago
> How do you deploy a thing to run on k8s? kubectl apply -f ~/git/infra/secretproject/prod.{json,yaml} One JSON/YAML file too uwieldy? Generate it using jsonnet/CUE/dhall/your favourite programming
501.
▲
by
q3k
5y ago
> but all the clients our Kubernetes team works with all want separate clusters or testing, staging and preproduction. And I think that's one of the biggest issues with how people use Kubernetes these days (another candidate being i
502.
▲
by
q3k
5y ago
Kubernetes is much more than container scheduling. Custom resources, identity and a powerful RBAC system allow you to use it as a general configuration/operational data store in your own code, from implementing operators acting upon ku
503.
▲
by
q3k
5y ago
> The problem isn't with JSON but how some JSON deserializers work. That makes no observable difference to the end-user of JSON wishing to use it as an interchange format. The standard might as well be perfect, but if nearly all of
504.
▲
by
q3k
5y ago
> Though I think the biggest benefit of JSON is that it is so simple, at least compared to XML. Or more precisely, that it appears simple at first glance, and that it is very easy to get started with. TFA (or just practical experience tr
505.
▲
by
q3k
5y ago
You can use whatever you want :). I personally would rather still go with Protobuf if I'm going to put in the effort to add a schema and codegen. It gives me other nice-to-have features (faster [de]serialization, smaller messages, fiel
506.
▲
by
q3k
5y ago
> Shouldn't be deserialized into a map. but a Array<Map<string,string>> like structure. But that's the thing: you might actually expect/want a Map<string,string>, but a malicious/broken system might
507.
▲
by
q3k
5y ago
> Instead - I have an informal contract that almost all fields are plain unsigned bytes (0 to 255) which works fine for my use-case, requiring just 1/8th the space. Right, but that informal contract is at the detriment of everyone e
508.
▲
by
q3k
5y ago
> Compare that to something like protobuf: it's not a self-synchronizing stream, so if you send someone multiple messages without framing them (prefix by length or delimited are popular approaches), they're going to decode a si
509.
▲
by
q3k
5y ago
> I'm a little suprised to learn there's no self-reference support in protobuf, as I wouldn't have assumed parsing that would be an issue (as all it really is is a pointer to an existing object in the message to say, put a
510.
▲
by
q3k
5y ago
The problem doesn't really exist in Protobuf, as protobuf (de)serialization is performed based on an IDL definition of the message type. Whatever that IDL specifies, a corresponding typed definition and (de)serialization function will
More ›