Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
remon
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
61.
▲
by
remon
7y ago
It is. People keep getting offended by the notion that money incentivises people to do a better job. Most jobs where this has proven to work do exactly that (bonuses, raises, etc.). All else being equal you will get better service from a pe
62.
▲
by
remon
7y ago
I'm not no. I'm from Europe and I strongly disliking tipping as a concept because, as you point out, good services should be the default and any cost for that good service should be factored into the prices. That said, I flipped o
63.
▲
by
remon
7y ago
Less tip = more cost employer = higher prices. One way or the other you're roughly paying the same, only in a way that does not incentivise good service as much.
64.
▲
by
remon
7y ago
I think OP was asking if Amazon is calculating their savings based on the public AWS service pricing or their own cost for running on those AWS services (there's obviously a good chunk of margin on what it costs to run AWS and what the
65.
▲
by
remon
7y ago
> i dont think i ever said label measuring/collision detection is a performance hog. compared to the work of doing the plot itself, it's insignificant. avoiding that work is more of a code size and complexity reduction for uPlo
66.
▲
by
remon
7y ago
And you should calm down a bit. I was referring to your benchmark hitting exactly the functional scope of your library while it's invoking more generic libraries that by extension have to do more work for the same functional result. Ba
67.
▲
by
remon
7y ago
After having a look at the code and the list of "non-features" (which is a rather opinionated list I might add) the "exceptionally fast" part primarily comes from it simply not doing as much as most charting libraries do
68.
▲
by
remon
7y ago
Should I reply here or to sales@octopus.com?
69.
▲
by
remon
7y ago
I'm sorry but this was a bit of a painful read. Hindsight is 20/20 but this was pretty poor engineering and business modelling from the start. "To ensure there was no way for one user’s data to mingle with another, each cloud
70.
▲
by
remon
7y ago
I agree, this is a perfectly valid reason for the SMS flow to error on "Too many attempts".
71.
▲
by
remon
7y ago
Interesting followup: I just tried to permanently delete my Blizzard account and the request is being denied regardless of my method of verification. The SMS passcode verification claimed on first attempt that it was denied "Due to too
72.
▲
by
remon
7y ago
Maybe. If so it might be in their interest to publish the decision making process.
73.
▲
by
remon
7y ago
Okay. Not very effective then.
74.
▲
by
remon
7y ago
One of these again. I struggle to form a coherent opinion on this one. Yes the player broke tournament rules and yes you can argue that he should be banned on that basis alone. But oh my god. Even if they banned him just on the basis of enf
75.
▲
by
remon
7y ago
How on earth is content this shallow drifting to the top of HN? Is any "non expert" software designer walking away from this enlightened in some way?
76.
▲
by
remon
7y ago
That'll be fun to get Google results for. I suppose we can be glad they didnt go for Go + UI, you know, GUI.
77.
▲
by
remon
7y ago
That's...exactly his point. You just 180-ed.
78.
▲
by
remon
7y ago
Hm, I struggle to see an upside with levelling the playing field that way. Groups that have the budget to throw huge amounts of resources at problems are still providing important insights. That can happen in parallel to optimising wattage&
79.
▲
by
remon
7y ago
You're right of course but I think we have to recognise that for all sufficiently complex problems Abrash' "folksy wisdom" is effectively true and, in his particular case, a good chapter title more than a statement of fa
80.
▲
by
remon
7y ago
It's definitely mostly historical but it is an excellent read anyway if you're interested in what kind of problems faced game developers at the time and to what lengths they had to go to solve it. The chapters about getting Quake
81.
▲
by
remon
7y ago
Right? I mostly lurk here but for some reason almost everyone is like "well you can't drive that speed on any normal road anyway". Yes, thank you. You won't typically launch yourself to the Moon either but it's nice
82.
▲
by
remon
7y ago
Not a huge fan of the try built-in spec as proposed but I struggle to understand the reasoning behind people arguing that the current error checking/handling paradigm "at least makes the code readable/understandable". It
83.
▲
by
remon
8y ago
Mature, balanced and on topic opinion.
84.
▲
by
remon
8y ago
I don't think it potentially taking a long time was the primary reason for not making redis multithreaded. In the redis manifesto it is stated that one of the guiding principles is to avoid complexity if they can. Also not that the ben
85.
▲
by
remon
8y ago
Such an amazing read. What positively surprised me, but perhaps shouldn't have, is that they seem almost relieved they didn't get there first. It's reassuring in a way I have trouble verbalising.
86.
▲
by
remon
9y ago
This is such a broken argument. The one upside of behaving this way is that it makes the HN frontpage and one can argue about the value of that for the issue at hand. It's pretty much established fact that, all other things being equal
87.
▲
by
remon
11y ago
Although I agree with the general concerns raised in this thread FB is not sending raw audio to its servers and thus is not "listening" to you. The majority of work is done on the client-side. Specifically, a short audio sample is
88.
▲
by
remon
11y ago
> because nobody is doing this kind of processing client-side. This is a half truth at best. Audio recognition can be based on one of two techniques. The first is audio watermarking which is completely client side (albeit not applicable
89.
▲
by
remon
11y ago
Thank you. Using days as your time unit for measuring requests over time is not useful. I'd be more interested in the req/sec numbers during peak.
90.
▲
by
remon
11y ago
Is it camera angles or is that actually taking off almost vertically there?
More ›