inglor

81 ms·

871.
by inglor 11y ago
Here is the relevant software engineering term for relevance https://en.wikipedia.org/wiki/Design_by_committee
872.
by inglor 11y ago
From the front page: "Optional P2P backup, so even if your Own-Mailbox is offline temporarily you don't lose any email from your self-hosted addresses as long as you maintain 70% up ratio." and "16GB storage, possibility
873.
by inglor 11y ago
> How would maintaining a SSA representation of the code help detecting dead code paths? Well, if a variable assigned but never appears in a path that might have side effects it's dead. It's only the halting problem if you pret
874.
by inglor 11y ago
Oh yes, they do some static analysis but it's not even close to the level of Coverity, sorry if my initial comment was misleading.
875.
by inglor 11y ago
Why? You'd just keep the code in SSA and diff whenever the user adds code - you need to create the form _once_ but after you've created it diffing it should be reasonably fast - the creation can be done at project creation time an
876.
by inglor 11y ago
A tool like IntelliJ can do deep analysis off-line and in the background and only tell you about the results. This is a good tradeoff between fast feedback and deep analysis.
877.
by inglor 11y ago
ReSharper (on C# in Visual Studio) and Visual Studio itself do perform static analysis and find out bugs like "possible multiple enumerations of IEnumerable" for you pretty readily, developers also use code coverage tools. Still,
878.
by inglor 11y ago
> Not all promises libraries support `call`. As I said twice before, the `call` bit is irrelevant, I used it because you used Q in the article. It would have worked with bluebird or When just as well - library is really not the big deal
879.
by inglor 11y ago
Thanks for clarifying, I did not know that - I'll make sure I check this sort of stuff in the future.
880.
by inglor 11y ago
> I used a similar code flow as the standard callback example previously described, except that I included the chaining of error handling with parallels to synchronous try/catch/finally flows. You do the promise-as-a-pyramid e
881.
by inglor 11y ago
Chaining them is also perfectly viable (still one nesting level), as long as you're not dipicting a non-existing problem ("callback hell") it's all good. I used .call since OP used Q promises in the article - this works
882.
by inglor 11y ago
Both parts are incorrect, the native way is `Promise.resolve('done')`. As for .call - native promises let you subclass them. If you have a promise enabled environment you can use generators anyway. I used Q's syntax because t
883.
by inglor 11y ago
The reason this works is that promises are already representative of queues of pending values. To contrast, here's the ES7 version (works with babel) I added to the gist https://gist.github.com/benjamingr/d08cfe94d
884.
by inglor 11y ago
The promise usage here is so terrible it's not even funny. I've made a gist of how it'd look like with correct usage. Just contrast the single level of nesting (for the branching) in the correct version vs. the 5 nesting leve
885.
Download Valley(en.wikipedia.org)
6 points by inglor 11y ago|0 comments
886.
by inglor 11y ago
Everyone with updated software is safe from these attacks since the authors disclosed them to the effected software beforehand. As for smartcards there is no reason to assume they would do anything to mitigate this.
887.
by inglor 11y ago
Also related their previous work with RSA inventor Adi Shamir at http://www.tau.ac.il/~tromer/acoustic/
888.
by inglor 11y ago
For what it's worth - the authors know each other from before and knowing both parties Mark did not intend to mean any offense.
889.
by inglor 11y ago
This is a really cool idea, I think if you show off some of the interesting people and meetings in the home page it'd go a long way to show you won't (probably) be meeting weirdos. It'd be nice to know if you can elaborate a
890.
by inglor 11y ago
I wonder, why did this get nuked?
891.
by inglor 11y ago
tl;dr - found an XSS via HTML injection on an Uber petition page. What they did was a pretty basic XSS attack. The fact they were successfully able to do this is a major problem for Uber basically. Not escaping arbitrary user input you&#x27
892.
by inglor 11y ago
Just as a data point, Google paid Mozilla 300 million dollars two years ago to be the default search provider in Firefox. This is definitely a market.
893.
Implement arrow functions in v8(code.google.com)
44 points by inglor 11y ago|56 comments
894.
by inglor 11y ago
Right, for the code base it is good - from Apple's PoV however they lost market-share in a billions-of-dollars market
895.
by inglor 11y ago
I don't blame them after what Google did with Chrome from all the hard work they poured into WebKit. Especially since they later forked it into a separate project. So while this is a programming language and such an issue is not likely
896.
EcmaScript 6 approved by ECMA as a standard(ecma-international.org)
3 points by inglor 11y ago|0 comments
897.
PCC: Performance-Oriented Congestion Control(modong.github.io)
1 points by inglor 11y ago|0 comments
898.
by inglor 11y ago
So why didn't you publish anything about it? You've had tons of chances to make amends to the io.js community before the merge - a simple "I know what io.js is" tweet would have done it, or a blog post, or even a comment
899.
by inglor 11y ago
This is the same guy who said 'io.js, what's that?' And paid people not to switch... He's not fooling anyone http://readwrite.com/2015/02/03/joyent-nodejs-incubator-iojs... One more thing:
900.
by inglor 11y ago
This is about as easy to do with every other language - I could have done it in C, or Python or PHP or Java or C# or whatever - node was just the lowest friction one for the PoC - all you ned is an HTTP server that lets you write dynamic re

More ›