wldlyinaccurate

I've had similar experiences with Ruby - I used Sinatra to write a really simple REST API, and while getting the core stuff working was relatively simple, there were many times towards the end when I wished I'd just written it in PHP.

Oh, and don't even get me started on deployment.

Buying a Dell with Ubuntu preinstalled is a PITA because you have to purchase it as a business which apparently means you lose all your consumer rights. I found this out the hard way when I was told that returning my XPS 13 would cost me a 15% "restocking fee".

Besides, they're preinstalling 12.04, and upgrading to newer versions (in my experience) requires blacklisting kernel modules and setting kernel params.

I took the survey while I was playing DotA2 on Ubuntu, but since taking the survey I no longer use Steam on Linux. The main reasons are that only 4/50 games in my library are available on Linux, and because graphics performance still sucks (Intel HD4400).

I'll try it out again whenever a new game is available or when there's a graphics driver update, but at the moment I'd much rather reboot into Windows than pull my hair out over how bad Linux is for gaming.

Why are you comparing crack cocaine to cannabis?

To me, this seems really convoluted - maybe as a non-rails developer I'm missing some key information?

Why, for example, would you use this over client-side templating and data-binding? Create the template once, grab some data with AJAX, bind it to the template...

You know what? I wish companies let me play with their codebase in an interview. At least then I could see how much truth there is to all the "yeah we totally have a great automated test suite and build process" I get told during interviews.

A whole day is unreasonable, but I'd jump at the chance to do what TFA describes as "free work" for an hour or so.

I could be wrong, but I think they're just poking fun at all the "An X interpreter written in Y" where X and Y are the current trendy languages. Usually one of X or Y are JavaScript or Go, so seeing both in the same headline is like some sort of Hacker News headline jackpot.

I work in an open office with no dividers. Unfortunately for me I don't have selective hearing, so 95% of the time I'm trying to drown out the buzz by wearing over-ear headphones (usually with no music playing). I also spend a lot of time fending off product managers and testers who just refuse to acknowledge the headphone rule and constantly bug me about trivial things that can be put in an email or an IRC message.

The other 5% of the time is great - as other people have already mentioned, it's really easy to listen in to conversations and get an idea of what everybody is up to.

I'm living in the UK right now, and I'm the same as you with having only one card. However most of my friends have several credit cards, which I find really strange. I wonder if it's a symptom of how broken the economy is... It's too easy to get multiple credit cards and use them all to pay each other off, so you're essentially living in constant debt.

When I find myself worrying too much, I take a walk. I find that being away from my worries helps me work through them more easily.

> Even if Node was 5x slower than PHP I would still go for Node because of its easy jQuery syntax

That "jQuery syntax" has nothing to do with the language itself. jQuery uses Sizzle[0], which is a CSS selector library for JavaScript. There are plenty of PHP libraries which provide CSS selectors, such as the Symfony CssSelector component[1].

[0] https://github.com/jquery/sizzle

[1] https://github.com/symfony/CssSelector

Can you give an example of where you've had to use $watch? Usually too many $watch is an indication that you could improve your app's architecture, e.g. by abstracting into directives.

FWIW I'm only speaking from personal experience and in your case lots of $watch might be necessary.

It took me 10 seconds to go from your landing page to a really useful page full of things to do in Berlin. Awesome work!

jQuery does exactly that, with polyfills for browsers without the native implementation. jQuery 2.x does away with many of the polyfills since older IE versions aren't supported.

If you want an even smaller jQuery, you can build your own[0] without the modules you don't need.

[0] https://github.com/jquery/jquery#how-to-build-your-own-jquer...

I couldn't find a full changelog, but GitHub's compare system makes generating a changelog fairly trivial: https://github.com/knockout/knockout/compare/v2.3.0...v3.0.0

Depending on the window manager, there are reports[1] of Linux achieving better battery life than OSX. That's not surprising though, as a lightweight WM like i3 is going to use much less resource than OSX's shiny interface.

[1]: http://www.reddit.com/r/linux/comments/1jjdi8/ultrabook_with...

The fact that C++ is a compiled language automatically removes it from my "scripting toolbelt". Aside from that, I just don't find it to be anywhere near as expressive as shell or Python, which is hugely important when you want to understand a script you (or somebody else) wrote several years ago.

It seems to work with @{any letter}. Can anybody explain to me how GitHub is interpreting this search term?

Apologies for being vague. Regarding the SSL certificate, I was referring to modern browsers refusing to load "unsafe" assets.

When the JS can't load, JS-heavy apps tend to either be raw templates (i.e. full of {{ statements }}) or completely blank (if the templates were going to be loaded in a separate request). As Isofarro said, non-JS pages don't suffer from this because the content is there in plain HTML.

Always interview the person. Always give them a code test - at the very least a simple 30 minute test.

My current employer currently hires people without doing any sort of code test, and we have recently had to let people go because they just weren't very good. 30 minutes could have saved us a lot of wasted time and money.

If you are able to "pre-render" a JavaScript app like this, then you should be serving users the pre-rendered version and then enhancing it with JavaScript after onload.

JavaScript-only apps are a blight on the web. All it takes is a bad SSL cert, or your CDN going down, and your pages become useless to the end-user.

Dear website owners,

Please take the time to set up a service like CloudFlare[0]. It's free, and will prevent your site from going down during traffic spikes. There's really no downside.

Regards, Frustrated User

[0]: https://www.cloudflare.com/

> Almost all cats look the same

Congratulations, you've just dramatically simplified the algorithm. This means that once you can identify a cat, you can say that any image which isn't a cat is most likely a dog.

Also, cheer up! This isn't supposed to be "useful". Who cares if it's narrow and can't be applied to anything else? It's a chance to have a bit of fun and for some people (like me) it's a chance to learn about image recognition techniques.

> The alternative is to hijack the click event, wait for say 100ms, and then load the new page via JavaScript, but that also break the open in a new tab functionality.

How does it break the open in new tab functionality? You can detect if the user was Cmd/Ctrl-clicking, or using the middle mouse button. I've done this on many sites and it works fine.

One of those Internet Fridges. Yeah, buy one of those.

Wow, this made me painfully aware of how few languages I know. I hadn't even heard of some of them!

I used the Wikipedia layer extensively during a road trip around Scotland. It was a great way to find nearby places of interest - I daresay the trip wouldn't have been anywhere as interesting without it. More recently I was in France, hoping to do the same thing. To say I was disappointed to find the feature had been removed is a massive understatement.

I don't really understand how Google gets away with this sort of thing, I thought it was Software 101 to never remove features. It's sort-of understandable if the feature has very few users, but it sounds like this one is used by quite a lot of people.

Agree. Solid blades being spun by a powerful motor? Not the sort of toy I would give to my kids.

What? I can't tell if you're trolling, but I'll answer anyway...

The Android emulator allows you to run applications that were compiled for ARM because it translates the ARM instructions to x86. This is really CPU intensive and can eat a lot of memory as well.

Technologies like Intel HAXM[0] speed this up, which is how the x86 Android images manage to be so much faster than the regular ARM images.

[0]: http://software.intel.com/en-us/articles/intel-hardware-acce...

With regards to the speed, that's because the Android emulator is an emulator - it's converting ARM instructions to x86. Because of this, the Android emulator is actually a better representation of how apps run on real hardware than the iOS simulator.

There are x86 images available for the Android emulator, which will run as fast as your host machine will allow.