Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
cautious_int
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
cautious_int
11y ago
Very unclear. Would not recommend, instead search for some actual commented code.
32.
▲
by
cautious_int
11y ago
In this case the house was burned down by the owner( company ) because someone broke in.
33.
▲
by
cautious_int
11y ago
Here's to the crazy ones. ( Sorry, I couldn't resist. I found it funny in a sad/ironic way. )
34.
▲
by
cautious_int
11y ago
It is, of course, entirely possible the FBI or some other agency was able to extract the password from Glenn while interrogating him – the man changed his plea to guilty halfway through the case, and may have sung like a canary. In other
35.
▲
by
cautious_int
11y ago
Why do we have to resort to public outcries to get attention from a company? If the user agreement really allows this, then it is time to stop supporting them.
36.
▲
by
cautious_int
11y ago
Looks like something that should have been caught with a unit test that would test all possible error paths.
37.
▲
by
cautious_int
11y ago
That is why you should never learn from one exclusive source, especially if they don't provide valid arguments, and imply "trust me". I saw a couple of his introductory videos and I think he is great to teach specifics about
38.
▲
by
cautious_int
11y ago
Oh, you are assuming someone actually wrote that code. That is circular reasoning. It would be much better to write proper checks or just call functions that do so.
39.
▲
by
cautious_int
11y ago
How would that fix existing code without modifying it?
40.
▲
by
cautious_int
11y ago
But what information was even held on the website. Wasn't it just a public listing of usernames with the score. According to this https://news.ycombinator.com/item?id=8181773 then don't even store emails anymore.
41.
▲
by
cautious_int
11y ago
Of course you gain ability to check for overflow after performing the operation, Using exceptions? IMHO only very small fraction of overflow bugs would have been fixed by just wrapping result around. Yes, switching to wrapping integers
42.
▲
by
cautious_int
11y ago
1u/0u
43.
▲
by
cautious_int
11y ago
Assume sizeof(int) == sizeof(unsigned int) == 4 g << h Well defined because 2147483648 can be represented in a 32 bit unsigned int Even under those assumptions, it is implementation defined if unsigned int can hold the value 2^31.