One suggestion: if the code wasn't changed yet, switching languages should adjust the syntax in the initial example. So the default `var foo = 'bar';` in JavaScript should become `foo = 'bar'` in Python, etc.
580 karma · joined October 1, 2011
http://xion.io http://twitter.com/Xion__
One suggestion: if the code wasn't changed yet, switching languages should adjust the syntax in the initial example. So the default `var foo = 'bar';` in JavaScript should become `foo = 'bar'` in Python, etc.
The UX is indeed very nice. Just a small issue: FF19 on OSX 10.8.3 displays a horizontal scrollbar. Looks like a margin or padding problem with the central feed element.
When I bought a Kindle more than two years ago, one of the first use cases I discovered was finding an article on the web, deciding it's too long to read on a glare screen and wanting to send to the Kindle's browser. What I ended up doing was adding the articles to Pocket (Read It Later at that time) and crafting a small PHP script that turned the RSS feed of Pocket's items-to-read into a simple page with links, suitable for Kindle.
I still use Kindle for that sometimes, although I've moved with most of my Web reading to a tablet.
You just made my day posting this. It's absolutely hilarious!
DOM and Javascript engines still need few more man-centuries of iteration to bring their performance closer to e.g. JVM which doesn't really require hacks like that anymore.
They throw tantrums. They throws hissy fits. They scream bloody murder. They divine doom and gloom for Google about how severely this will affect it in much more important markets like Android and Chrome.
And yet the world is not ending, and not every Facebook wall has this petition [1] plastered all over. Even GOOG stock underwent as a much as a correction, still hovering comfortably above $800.
What did happen, though, is that self-important "opinion leaders" had their illusions of power dispelled. No wonder they are furious.
[1] https://www.change.org/petitions/google-keep-google-reader-r...
Of course, this (i.e. civilization quickly become extinct) is just one possible resolution to the paradox, but the arguably simplest one. If the actual reason(s) we don't see advanced life are different, the Great filter hypothesis holds less water. We don't know that yet, though.
The scary implication of #1 is that it updates our probability for long-term survival and becoming a technologically advanced, space-faring species: by _lowering_ it. That's because it pushes the potential Great Filter [1] closer to our present condition and increasing the odds that it's actually somewhere in our future.
But about those dark corners, I guess the point wasn't to present any particularly nasty gotchas, but rather some precious little lesser known tricks. C has plenty of very well known features you can be bitten by (mostly related to memory management, of course). While the presentation reiterates over some of them, the most valuable parts are about various _good_ parts of the language which are rarely heard of (viz. the usage of `static` inside brackets).
And this, I must say, I like a lot.
As IT industry, we might not be there yet when it comes to eradicating sexism, but at least it seems that this test has been passed successfully. Strongly as some may feel about Meyer's policy, it has been criticized almost exclusively on the grounds of merit and predicted effectiveness in achieving its desired goal (i.e. making the company more innovative). Little I've seen references to Meyer's gender and/or maternity playing a role here; that article (and the NYC article it quotes) look like exceptions rather than a rule.
That's the IT/hacker community I like and respect.
Which, I think, is one of the main reasons why Python is recommended more: it's simpler and has less sharp corners. The other thing is that Ruby is significantly slanted towards the object-oriented paradigm while Python remains much more neutral in this regard.
[0] http://ivanvillareal.com/osx/setup-iterm2-to-behave-like-gua...
I wouldn't mix those two when making a comparison to Perl.
As an example, there are like four different ways to write a simple 'if' statement in Ruby, with some blurring the difference between that statement and conditional expression (ternary operator in C-like languages). In Python, there is just one 'if' statement which is also clearly distinct from 'if-else' conditional expression.
However, given the success of Chrome OS, it might not be that difficult, actually.
It could really use a more specific description, and maybe a diagram too.
But obviously, this is nowhere near the price point you are suggesting. I think the reason cheap laptops look cheap is that they are, well, cheap. Users do not really expect them to last and therefore manufactures do not focus on longevity or style.
Good design is a premium for which you simply need to pay extra.
Valve is already doing mile-length steps in terms of upending one of the Windows' biggest advantages over Linux: games. Arguably, Office is another, but this time it's supposedly Microsoft itself who is about to diminish yet another selling of point of their own operating system.
I'm really confused, if that's indeed true. You could say it follows naturally with all the screw-ups MS made recently with respect to Windows 8 & Metro UI. But really, seeing a company undermine their own business so blatantly... I don't know what to think about this.
Whoa whoa, hold it right there. Unless your webmail supports simple keyboard shortcuts (like 'A' for archiving), threaded messages views, multiple email accounts at once and few other useful-but-not-for-majority features, snark statements like that are unfounded.