emn13

96 ms·

901.
by emn13 10y ago
Although the color-coding is odd; red doesn't mean insecure or even "dubious", even though it does sometimes... So using the site even for testing TLS clients seems a little non-obvious. At least if the idea was that your cli
902.
by emn13 10y ago
Given what you say - what's the point of this website? After all, a safe client should connect to green things (but might not support everything, fine), and... should also connect to many red things (if they're actually safe). Wh
903.
by emn13 10y ago
That depends on your definition of rational. Clearly, it's not the greatest risk, not even remotely close to that. But there are a lot of interesting cognitive biases at play here, and some of those exist for a reason. For instance
904.
by emn13 10y ago
async/await is possibly simpler to implement. At least: in go effectively every method is async (at least the api doesn't show what is and is not), and that means you can't afford the inefficiencies that typical async/a
905.
by emn13 10y ago
Then I don't understand what the problem is. Comparing ships (which most people aren't familiar with) to cars (which most people are) serves merely to give people a sense of what's possible. And that sense is reasonable; mak
906.
by emn13 10y ago
So I'm not a mathemetician, certainly not anymore. But for a while I did read a lot of this stuff, and wrote things like it. Aaand... to some extent you get used to it. But it really is simply a worse syntax. It's not just habit.
907.
by emn13 10y ago
The client could be open source; indeed the network protocol might even be simple. The client distribution or even implementation might be handled by third party. If for commercial reasons the provider wants a fancy shell and doesn't
908.
by emn13 10y ago
Ships are more like cars than they are like agriculture; so the comparison isn't insane. Especially since it demonstrates that cleaner combustion is possible even in tricker (smaller) circumstances. I'll go out on a limb and specu
909.
by emn13 10y ago
It's somewhat ironic that the article is perfectly clear and reasonable, and only the HN title which is misleading. Perhaps you should simply not read too much into HN titles?
910.
by emn13 10y ago
The problem is in the hackernews title, not the article. Perhaps a better hacker-news onliner would have been "Just 15 of the biggest ships emit more sulphur- and nitrogen-oxides than all the world's cars"
911.
by emn13 10y ago
Unfortunately, if convetional habit is for people to sign regardless and trust they'll get lucky or stay friends, then despite your reasonable intentions, you may still be hurting your position by refusing and absurd contract. See also
912.
by emn13 10y ago
In small programs like this, it might not even take a lot of effort. It's trivial to read a program like this and make a very good guess as to where bottlenecks are without even running it, let alone profiling it. That kind of simpli
913.
by emn13 10y ago
Well, we expect social media sites to try and avoid blatantly taking sides. But they definitely thrive on human-interest stuff (such as this), especially if it's something with a social mobilisation aspect, and that's almost boun
914.
by emn13 10y ago
I don't think the distinction really matters to the story -but yeah, the author wasn't subtle in trying to present one party as the victim here. But even if the roles were reversed (threatening anti-gun violence ads on an NRA piec
915.
by emn13 10y ago
Why does any organisation? Why does the NRA? Perhaps it would be nifty to split the world into commercial entities without no permission to lobby, and political entities with no permission to deploy commercial activities, but that sure isn
916.
by emn13 10y ago
Oh yeah, I have no reason to believe it's worse; it's just that I also doubt it's going to help much either. But... trial and error and all ;-).
917.
by emn13 10y ago
I suspect all languages without exception use some standard library functionality in at least a few of those sample programs, and most "standard" libraries aren't constrained to be self-hosting - so all of em use some native
918.
by emn13 10y ago
Yeah. But in this kind of tuned benchmark, I doubt clang will do any better across the board - especially not considering the fact that the current programs are likely to be at least somewhat tuned specifically for gcc.
919.
by emn13 10y ago
The problem isn't the number of bits (yet). The problem is the choice of hash. A truncated sha2 would still be fine for years to come (barring a sha2 break, which doesn't look imminent). 160bits may not be a huge margin, but it
920.
by emn13 10y ago
Also: that cost is certain to drop, and it might drop quite quickly - simply due to software and hardware improvements. If anything algorithmic shows up, it could change dramatically. Let's not wait for that to happen.
921.
by emn13 10y ago
If it is business as usual, that kind of makes it worse. Then again, we have no idea what was in those emails, and wccftech is openly pro-amd, so even though I have no reason to think they're lying, they might easily still be interpret
922.
by emn13 10y ago
People sometimes overstate the impact of length extension attacks. If your format has a length prefix (really common) then you may well be "vulnerable" in the sense that appending arbitrary data is "valid", but a canonic
923.
by emn13 10y ago
There are pros and cons there. The overhead isn't huge; if you use any ads whatsoever those likely swamp this effect anyhow. And dev time is limited - how much time is it worth shaving at best 100ms off for a small and shrinking grou
924.
by emn13 10y ago
I'm currently experimenting with if-no-window.Promise-then-polyfill via polyfill.io (I dont quite trust synchronous dynamic script loading yet, but we'll see if that's robust enough on old browsers). Sure, old browsers need a
925.
by emn13 10y ago
On the one hand, the deficiencies in that table don't look all too serious. Maybe Date.toJSON missing is the worst. On the other hand, that's a poor excuse - why the heck haven't they fixed these issues? Cross browser compa
926.
by emn13 10y ago
Sure, there are situations in which it's faster. In my (limited) experience with x264 at least the more extreme quality settings didn't scale quite as well, and those are the only ones I use. Regardless: some programs paralleliz
927.
by emn13 10y ago
I seem to have misremembered, the odd one out was WhenAny, and the issue is that it crashes when given the empty set, instead of waiting forever (which is fine if you're dealing with a specific number of tasks, but not fine if you&#x27
928.
by emn13 10y ago
Sure, the 8-core runs at a lower clock speed and and old arch - that's a major (but unavoidable) part of the problem, as I said. To be specific: you can't get the equivalent of a 7700k with eight cores - the 6900k is (AFAIK) the n
929.
by emn13 10y ago
For fun bits of API inconsistency there, would you think that... "task.Wait()" is to "await task" as "Task.WaitAll(tasks)" is to "await Task.WhenAll(tasks)"? Maybe it's just me, but I sure did.
930.
by emn13 10y ago
These chips look better suited to servers than clients as is. Most software still scales poorly with additional cores (or rather: most workloads still have a few single-core bottlenecks). E.g webbrowsers, compilers, video de and en-coders

More ›