gsands

I'd say no, and let them know when/if I planned to.

Do you mean you want to sell the domain? Because streamjoy.tv doesn't seem to have anything going on at the moment.

Jerry Seinfeld on stuff (new): http://youtu.be/HfYzlSNHapA?t=1m15s

edit: start time

It is called a "zero-day" because the programmer has had zero days to fix the flaw (in other words, a patch is not available).[0]

[0] http://en.wikipedia.org/wiki/Zero-day_attack

Could be a good oculus rift controller. Very tactile.

Agreed. But am I the only one who was disappointed when not every subsequent photo after the first had movement? About half did for me.

They lose right off for me because the back button doesn't work on jet.com to even exit back to the previous site you were on.

I would fix it up.

You get 3 benefits:

1. Continued income from it (people aren't going to continue to buy it if the bad reviews keep coming in).

2. You keep/improve your reputation. If your software isn't working well for any reason at all, it can give a bad reputation to the person/company attached.

3. You increase the chances of a good buy-out in the future, over what it would currently bring now.

We all know it can be difficult to get traction on a project, not to mention paying users. You already have proved this one can get both.

Check out the Chrome extension Videostream for Google Chromecast, link: https://chrome.google.com/webstore/detail/videostream-for-go...

I actually think high level questions like these are just conversation starters which can get into highly technical conversations quickly.

Sort of like the technologies themselves; GameCenter and CoreEverything are abstractions of lower level functionality. Being able to discuss their purpose, how to use them, and how to glue them together is what a good developer is. The rest is just syntax.

I think part of the idea of interview questions like these is that it will get a developer into those finer points, if they are in a technical discussion.

I love this. For a couple of reasons.

1/I often discover new things and have new thoughts and ideas along the way of an implementation which hadn't presented themselves previously.

2/I think it's a great way to avoid overthinking a feature or arguing too much for or against it. If nearing a majority consensus (with oneself or team) and there is time to spare, add it to Version 2 -- advantages being point #1 above, and having it prepared should it be deemed worthy to be merged to Version 1. I've heard that having features in the chamber ready to release is something big corps commonly do.

"After conducting an initial background check of a candidate for employment, USIS was required to perform a second review to make sure no important details had been missed. From 2008 through 2011, USIS allegedly skipped this second review in up to 50 percent of the cases. But it conveyed to federal officials that these reviews had, in fact, been performed."[0]

Other than the obvious-- Snowden turned out to do what he did, Altegrity allegedly made other mistakes, which the submitted article didn't mention.

[0] http://www.washingtonpost.com/business/economy/company-alleg...

edit: formatting

To be fair, filling out a form for a sandwich is about 5% of the food service operation at Google.

Most are just like lunchrooms in school, with much better food. Sorry that someone didn't give you a better experience there, with regards to food and otherwise.

interviewing for a promotion/different team?

I look forward to seeing your music site on Show HN sometime!

Nice, happy holidays!

Awesome dude! I've had similar experience and wish to echo this for all the hackers with questions about how to get involved.

I totally agree web site and web app are used interchangeably sometimes -- I was just answering the op as to how I and many people I know classify them and their differences as they relate to the topic of the article, javascript.

2012 MBP retina with 8gb ram here.. Major performance issues with Chrome -- when videos are playing in tabs, 10+ tabs open, etc. Systems Preferences are the least of the problems I've came across.

As a user of Angular, Backbone, and React (not all at the same time!), I feel like their largest benefit to me is in providing application structure -- good because as it has been said, if you aren't using a framework, you are writing your own. I don't really see how any of the 3 items under the article's "So what do we need now?" will provide that benefit.

quite different-- Web app, think Google Docs/Sheets.

Web site, think blog, information landing page, or even web store product page(s).

Web app is highly interactive (may or may not be an SPA single page app), relying heavily on javascript for UI events, saving/fetching application state, remote datasets, and sometimes making use of modern HTML5 browser features.

Web site is displaying information and is just augmented with some javascript mostly for improving the UX or attaching analytics/social plugins etc.

codepen.io would be a good place to learn by example. You will see many isolated code samples with the clearly separated HTML/CSS/JS.

As you wrap your head around 'what is happening' as you put it, you can start to combine what you see to make new creations of your own.

For the basic timeline of when things happen, research how a website is rendered. Here's some info to get you started: http://frontendbabel.info/articles/webpage-rendering-101/

+1 for linking to the lowest price I can find for it on the web (199 vs Amazon's 266).

Congrats on your first startup, but I really recommend you address the issues with your site immediately.

Like others, the top image(s) never loaded for me and I'm on a 50mbps connection.

I also wasn't even aware there was anything below the fold either, since you have such a nice sticky footer!

If I were you I'd just scrap the top section while you get the compressed image decisions made so the products are front and center when users hit the page.

Feel free to msg me, email's in my profile.

similar learning curve with both -- with either one your learning will be split between learning language constructs (Obj-C/Swift or Java), app architecture (iOS and Android both have unique ways of doing common things), and the ecosystem library (Cocoa Touch or Android).

"So now that octodog is part of the family, octocat is all depressed. Since we love octocat more than octodog, we'll turn his frown around by removing octodog.txt."

Interesting analogies they use in the tutorial.

For OSX apps, yes. iOS, not possible AFAIK, since sideloading is not possible on iOS.

There's a debate over whether or not class-based views are a good idea to use. Discussion here: http://lukeplant.me.uk/blog/posts/djangos-cbvs-were-a-mistak...

I agree, I tend to think of 'print' as writing data to some place, not necessarily to physical paper.

I guess the hackiest part is playing along with a message exchange dance that refers to things like ink and paper.