I've never gotten this argument. I mean, I have totally normal (nearly 20/20, but not quite... thanks to aging) vision, yet I can see the blurred edges of diagonal and rounded images perfectly fine on an iphone 5s at 2 feet. I think people just aren't really looking. I tried a thunderbolt display recently, and it was painfully low resolution. I haven't seen the math recently, but I have hard time believing that any phone today, let alone any monitor or television, really reaches the resolution of print.
Nice city, but with 114% of the population being smokers...
I love Europe, but for being so developed, it's amazing how many places there people still think smoking is 'cool,' and 'a symbol of freedom.'
I do like Vienna, but I think I'd choose Hamburg if I had to choose a city in the German-speaking world. Or Berlin - only slightly less cosmopolitan, but the tech start-up scene is kind of happening, and the cost of living is cheaper.
As an ex-Ruby cum Node.js lover recently converted to Go...
Programming in Go, once it clicks, really does feel relaxing and productive. If you're a decent Node.js programmer, it's like stepping up to "Node Pro", in the sense that you work close to the metal with your web server so everything feels clean and easy to wrap your mind around.
But Go code is cleaner and tighter. The code formatting conventions contribute to that greatly, as well as the fact that you just don't have to pull in as much 3rd party code because so much functionality is already beautifully integrated.
There are a lot of positives about Go that reveal themselves over the first couple days of coding in it.
I do wish the documentation convention included not only a brief description each function, etc., but also a brief example.
By the way, I also evaluated Scala for a few days before settling on Go as my preference. I like Scala, but it quickly becomes a sprawling language as your explore it further, and frameworks like Play and Lift bring even more baggage along for the ride. The core language, on its own, was attractive, but overall, the experience just didn't have the compact, robust, completely under control, and nimble feeling that came with Go.
Oh ya, and the Go syntax felt ugly and awkward at first. That feeling quickly faded after a day of use, but it's worth mentioning because I bet it turns some people away from Go before they even get to the great parts.
I thought 95% of the syntax was a dramatic improvement over straight obj-c, which I actually don't mind at all.
I admit, the one time I paused was when I saw the trailing return types. It was the only part that felt unintuitive.
By mere convention it felt odd, but I'm willing to explore a break with convention. Seeing how well-designed the other 95% of the syntax is, I'm giving the architect the benefit of the doubt, and hoping that this trailing return syntax ultimately proves MORE intuitive, despite my initial recoil.
I'm really curious now about the practical issues of putting Eero into real-world use (which, since we're talking obj-c here, means OSX or iOS development).
Most of the comments here are way off base, focusing on the relative worth of the objective-c language, rather than the value of Eero for developers who have no choice but to use objective-c, regardless of how good they think it is or isn't.
If you haven't already - I highly recommend following the link. RubyMotion was somewhat interesting, but really didn't feel like a massive improvement over plain old objective-c, especially once you factor in all the Cocoa APIs.
However, Eero looks amazing. The syntax used represents a vast improvement over straight objective-c or RubyMotion. Take a look - it's genuinely exciting.
personally, I've had great luck with namecheap and host all my domains there, then forward to ec2, linode, and rackspace as needed. great means simple and they haven't ever tried to screw me, which is unique among players in that market. i almost never have to think about my domains, and that's what makes a good domain host in my eyes. just my 2 centimes
I'm on the hatin' side actually. Locked down privacy to the max, only to find it all re-opened again when FB changed their privacy options. That happened 3 times.
Those shenanigans finally stopped, but then I'd be browsing the web and find comments like 'Your friend x likes this page.' It's creepy that to see that on a site I've never visited before when I have my FB locked down completely. I understand the technology, but the instinctive reaction is still 'How the hell do you know who my friends are, random website?'
I haven't noticed that lately (desensitized to it?), but I just noticed on a friend's public-facing FB page (I logged out to verify that it was totally public) that it said she was in Country Y, city Z on date D, with ME. There was my full name and my location in the world posted to the world, despite locking down EVERY SINGLE privacy setting available and allowing NO third party applications, etc. Even my friends cannot see or post to my 'wall.' This is all very disturbing, so yes, I'm still hatin', despite recognizing the cool benefits of a single centralized place to stay in touch.
1.) Youtube, Twitter, Facebook... blocked
2.) Google... rerouted to HK and still censored
3.) Gmail... increasingly unreliable
4.) Chinese mostly don't care, but only because of length of time that the situation has endured. China runs on 'Guanxi', or relationships. In other words, rampant nepotism and (sometimes) thinly veiled corruption. You start company Y competing with foreign company X. You get the government to block company X's service in China. Within a fairly short amount of time, your company's site dominates, and people mostly forget about the foreign competitor.
5.) Foreigners are generally not bothered when using VPNs (I have had excellent experience with one in particular, but avoid posting it publicly for obvious reasons). Assuming, of course, the use is apolitical.
6.) Young Chinese web users have developed conventions for speaking about sensitive topics in ways that (somewhat) evade censorship, such as using homophones, metaphors, etc.
7.) The general atmosphere in China, as regards the censorship, contains less animosity than most westerners would assume. Most web users understand that censors are just doing their job, and occasionally even speak to censors directly in their social network site posts, such as to make a plea to leave the post up for just a little bit longer before censoring it.
8.) In general people in China do desire change, but they're largely pragmatic about it. They've seen incredible progress in their lifetime, and though there are occasional steps backward that are frustrating, the overall march still tends to be in the right general direction (the nature of information - it naturally breeds freedom, bringing access to more information, and thus more freedom, in a virtuous cycle). Young Chinese people are often more informed about political issues than young westerners, through their prolific use of social networking sites (yes - even more than their counterparts in more developed nations).
Ah, back to the point... use a good VPN, and all will be well.
I agree that the context switching costs are quite high, reducing the time actually spent on coding. It might be better to focus on one language/framework for five straight weeks, for example, while still changing specific design patterns/recipes per week. It reduces switching costs, gives devs time to grok new languages if need be, and should result in higher quality code for each weekly project.
You might also let devs post fragments of their code as they work on it, and links to their github repos. The reason is that a dev who is really learning a lot, not just exercising existing skills, might get far off track if working in isolation, like a plane that takes off at a heading that is slightly off, and ends up hundreds of kilometers from its target. Plus, it would give more time for people to discuss/debate alternate implementations, and that debate itself would also be a great source of learning.
yep, no luck. i have a good friend just finishing up his phd in a the field and working on applications for similar technology for european automakers.