inglor

76 ms·

841.
Ask HN: What are some things your software team does that makes it successful?
10 points by inglor 11y ago|4 comments
842.
by inglor 11y ago
That's not very helpful. All the commit contains is a version bump. Not what changed, not why, nothing. Anyone can tl;dr what changed?
843.
Traitorous eight(en.wikipedia.org)
1 points by inglor 11y ago|0 comments
844.
by inglor 11y ago
Possibly stupid question: Isn't this how the Playstation 4 plays Playstation 3 games (in a nutshell)?
845.
by inglor 11y ago
Wait, so Samsung wrote their own new JavaScript engine for embedded devices? This is actually very cool. It looks very constrained in what it supports so far though. Update: They're at ECMAScript 5.1 https://github.com/
846.
by inglor 11y ago
It's probably a good idea to link to the presentation directly as it explains the point and methodology more clearly IMO: http://jscert.org/popl14/?full#1
847.
by inglor 11y ago
You can't talk about JavaScript formal analysis for security without mentioning Mark Miller's amazing work here: http://www-cs-students.stanford.edu/~ataly/Papers/sp11.pdf Here, not only does he built a
848.
by inglor 11y ago
Probably the amount of eyes that read it. This stuff is insanely easy to get wrong in very subtle ways and reimplementing the stack always carries a risk. This is why people usually prefer to stick to the "regular" libraries even
849.
by inglor 11y ago
This is currently being discussed in io.js (and remember it's being backported to the main NodeJS branch). Feel free to come participate in the discussion.
850.
by inglor 11y ago
https://github.com/domenic/unhandled-rejections-browser-spec
851.
by inglor 11y ago
Well - the moral is to complain more, when I wrote and advocated for detection in io.js I needed people on my side - Domenic needs people to complain and help now for the browser spec - we're always a hand short :)
852.
by inglor 11y ago
process.on('unhandledRejection', function(promise,reason) {` since io.js 1.3
853.
by inglor 11y ago
Not if I can help it :) In io.js this is no longer an issue, you have a process event you can catch on "silent errors" to make them loud. This lands in NodeJS soon. Bluebird promises don't behave this way and have never done
854.
by inglor 11y ago
This gets so much easier with promises it's amazing: 1. You can `throw` in async functions (when things are promisified) and `.catch` async errors. 2. You can't forget the error handling or ignore the `err` parameter, it will prop
855.
by inglor 11y ago
No no, singletons are pathological liars http://misko.hevery.com/2008/08/17/singletons-are-pathologic... Atomic mutable global state is still mutable global state. DI containers mean you don't need a sin
856.
by inglor 11y ago
A singleton is basically a global variable and those aren't really important to "shim" in Go. Object method calls are pretty much the same conceptually as message passing but when you actually need to synchronize as you point
857.
by inglor 11y ago
There is, singletons are an anti-pattern, they're still interesting to discuss like this in terms of making them safe. In a language with both concurrency primitives and globals singletons have little (no) place anyway. I still learned
858.
by inglor 11y ago
Wow, that totally got me, thanks. 2011 definitely explains a lot of the choices like including jQuery and 'almost jsx' syntax. They have some interesting projects with it (the end to end encrypted chat) but I think they might have
859.
by inglor 11y ago
Here is an "introduction for coders" on GH - I think it explains it better than the website https://github.com/MLstate/opalang/wiki/A-tour-of-Opa
860.
by inglor 11y ago
Very nice work pulling this sort of thing up - but honestly? This looks terrible to actually use in code. Even if they do commit to working on this language - and it offers advantages over Meteor (which it looks to be inspired a lot from) -
861.
by inglor 11y ago
Mixins are being considered for ES2016: https://esdiscuss.org/topic/about-lightweight-traits meanwhile you can Object.assign behavior into things.
862.
by inglor 11y ago
As a fellow numpy user - why? I would love having sugar for this, I use it all the time. Introducing a single operator to overload seems odd but it's definitely a pragmatic solution to making code more readable. What would you do ins
863.
by inglor 11y ago
Let's not forget https://www.python.org/dev/peps/pep-0484/ which looks really promising
864.
by inglor 11y ago
> Does it mean that it will be possible to create realtime apps with python? I'm not sure what you mean by realtime but usually real time means something else and requires more deterministic behavior. If you mean applications that u
865.
by inglor 11y ago
I'm extremely enthusiastic about `async/await` semantics, and in particular async iterators and the `for async` loop. It's astonishing to see how fast Python is moving in this direction. It is truly a powerful language for as
866.
by inglor 11y ago
That's because 99% of times when people use it it's an anti pattern: stackoverflow.com/questions/23803743/what-is-the-explicit-promise-construction-antipattern-and-how-do-i-avoid-it
867.
by inglor 11y ago
You can reject inside a `then` by `throw`ing an error, like synchronous try-catch.
868.
by inglor 11y ago
Promises - the assumption here is that native promises are fast - this is amusing. Userland implementations like Bluebird promises are significantly faster than native promises. Not to mention the fact that converting an API to use promises
869.
by inglor 11y ago
The part where you're abusing an old "array like" and the way Array.from works with it and uses the index argument in the mapper argument to force it into a range. How many people do you think understand what `Array.from({len
870.
by inglor 11y ago
`Array.from({ length: n }, (v, k) => k + x)` this is a terrible way to create a range, it only works incidentally. Please do not use it.

More ›