Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kiitos
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
47 ms
·
631.
▲
by
kiitos
3y ago
> The vast majority of AfD voters (75% according to stats I have seen) do not vote for the AfD because they are Nazis. They hold their noses at the awful ideology, but don't see an alternative to some of the awful policies being ena
632.
▲
by
kiitos
3y ago
Induction ranges do not work with aluminum cookware.
633.
▲
by
kiitos
3y ago
The interesting thing here isn't so much the improved latency or whatever, it's the ability to ssh from a client that's on a network which restricts access to anything other than 80/443
634.
▲
by
kiitos
3y ago
Bitcoin is almost never used as a currency in the sense that you're describing. It is almost always used as a vehicle for (unregulated) speculation.
635.
▲
by
kiitos
3y ago
If allocations aren't a major contributor to costs, then there's no reason to use a sync.Pool, is there?
636.
▲
by
kiitos
3y ago
Be careful that you're not pooling buffers of wildly different sizes Also this code has many many problems please never use it to encode JSON :)
637.
▲
by
kiitos
3y ago
https://github.com/wundergraph/graphql-go-tools/blob/dcd50bd... Each iteration of this benchmark measures the aggregate performance of - 1x ParseObject - 3x AppendObject - 3x MergeNodesWithPath - 1x PrintNode
638.
▲
by
kiitos
3y ago
The thing that's missing from this (and most) articles about the described kinds of code optimizations is context: when is it appropriate to make these kinds of optimizing changes, and when is it not? > [with] this change ... the sp
639.
▲
by
kiitos
3y ago
const ( Break BreakOrContinue = iota Continue BreakOrContinue = iota ) This is not how `iota` works...
640.
▲
by
kiitos
3y ago
> This only works if you can trust the people doing the counts ... These kind of security and sharing situations seems to be open questions in the field. Trust in this sense can be safely assumed in every network that isn't open to
641.
▲
by
kiitos
3y ago
Programs are implementations of specifications, they're not specifications themselves. Unless you're talking about like Coq or TLA+.
642.
▲
by
kiitos
3y ago
Last key wins is the most common behavior among widely-used implementations. It should be assumed as the default.
643.
▲
by
kiitos
3y ago
A JSON object with duplicate keys is explicitly defined by the spec as undefined behavior, and is left up to the individual implementation to decide what to do. It's neither valid nor invalid.
644.
▲
by
kiitos
3y ago
Is the HTTP request body part of the input?
645.
▲
by
kiitos
3y ago
Error handling is just as important as "happy path" code.
646.
▲
by
kiitos
3y ago
func QueryDatabase(sql string) (string, *DatabaseError) { Returning *DatabaseError instead of error is a pretty clear programmer mistake, which should be caught and fixed by any reasonable kind of code review.
647.
▲
by
kiitos
3y ago
This is a fun way to describe the academic domain of CS theory, but practice demands an enormous amount of mechanical sympathy.
648.
▲
by
kiitos
3y ago
I definitely have used the OSI model in all of my corporate jobs for my entire career.
649.
▲
by
kiitos
3y ago
Look, just tautologically, if it was so shitty, we wouldn't be talking about it, because nobody would be using it. You're free to use a definition of "shitty" that doesn't take into account usage or longevity, but t
650.
▲
by
kiitos
3y ago
OSI is just a model. Like all models, it's wrong. But its ubiquity, and the fact that it's survived the test of time, clearly signal that it is a useful model. And that's as good as models get.
651.
▲
by
kiitos
3y ago
It's absolutely ubiquitous as a model. It's taught in every CS curriculum in every university in the world. It also doesn't break down in the real world, unless you're being extremely pedantic. Many bits of software don&
652.
▲
by
kiitos
3y ago
> [OSI's] negatives far outweigh its positives. OSI is not theory, it’s not a framework, it’s not helpful, it’s not a standard, it’s not anything those who use it claim it to be. Anything you teach with the OSI Model can better be t
653.
▲
by
kiitos
3y ago
This assumes that you're compressing IDs in batches. I'm sure that's a common situation, but I'm not sure why it's assumed to be the _default_ situation, nor am I sure why this is assumed to be the primary metric fo
654.
▲
by
kiitos
3y ago
You're just consistently a jerk in all of your comments. I'm not sure what else you expect.
655.
▲
by
kiitos
3y ago
Usually you use UUIDs when you don't want your IDs to be guessable.
656.
▲
by
kiitos
3y ago
> how expensive UUIDs are I don't quite get it. The normal string encoding of a UUID (d92b13b6-6780-4b98-82cc-d469dcdd42ab) clearly requires more bytes (36B) than the actual UUID itself (16B). The string encoding is for showing to u
657.
▲
by
kiitos
3y ago
OK.
658.
▲
by
kiitos
3y ago
Every versioning scheme necessarily describes intent, not reality.
659.
▲
by
kiitos
3y ago
Quiz: which RFCs do you need to know and implement to implement DNS?
660.
▲
by
kiitos
3y ago
DNS is an enormous protocol, almost unmeasurably large.
More ›