tpz

In the form of periodically-interspersed sponsor posts which are explicitly stated as being such and which are never mixed with actual content. As feed monetization goes, its about as above board as it can get.

Of course, being as above board as possible would still not be good enough for the anti-Marco brigade stomping around this pale imitation of what HN once was. I certainly wasn't here right from the beginning, so no hipster douchbaggery intended by any stretch, but I swear to those who have arrived more recently: You have no idea how good HN used to be compared to this. Sad, truly sad.

Not quite. Gitlab merge requests are very useful but only act between branches of a single repo, not across repos. Hence "merge" request, not "pull" request.

Seeing as we're splitting hairs... :)

In the Ruby version I wouldn't use that selector with any parens. The resulting line would be one character longer than the ObjC version but use the Shift key one less time and would avoid two pinky trips out to the square brackets. (unless I am miscounting)

All other things being equal between the two options, and of course they aren't but let's just keep splitting hairs for a moment, it sounds like a typing win for the Ruby option. Readability is of course in the eye of the beholder.

It pains me to feed the trolls, but just in case someone finds their way to this page in the future and actually tries to wade through all of the bullshit: Apple uses IPS displays in every product except perhaps the iPod Nano and/or Classic, and I only mention those two because I can't be arsed to check them.

I intend no ill will with this response, but it is worth pointing out that "the first two" "bigger issues" have nothing to do with your revision control system.

Lack of builds is something about which you and your CI server need to have a chat, and refactoring is something about which you and your people need to have numerous chats before, during, and afterwards.

Since no one else responded with this: you're right, it is not an accident that he would be considering 48fps, the reason being that a good amount of 24fps film projection occurs at 48fps on equipment that double pumps each frame. Such equipment (and the related equipment and processes around it) would likely be easier to upgrade/retrofit to 48fps than to 60fps.

Mono directly benefits their biggest competitor.

Mono directly benefits Oracle?

Your point is a very important one that I was surprised to find was not expressed by other commenters. It convinced me of something that was bouncing around my head while reading the article and the comments before yours:

If, as everyone seems to agree, movies are becoming more 'safe', more 'lowest common denominator' on average, reviews should be becoming _less_ polarized in response, not more.

That the opposite is happening suggests that reviews are progressively carrying less and less 'truth' than they once did, and this is likely the case even when they may be in general agreement on a given film.

I honestly doubt that the various Git-knocking commenters on this story have any real experience using Git on Windows. They are likely just parroting what they have heard about the early days of Git on Windows.

All of my Windows work during 2010 used Git and it was perfectly fine. The only thing that even comes to mind is that there was a tiny bit more effort with initial setup of SSH than on other platforms.

My mother suffers from severe (but now under treatment) sleep apnea and believe me when I tell you that if left untreated it could cause you far larger problems than wanting to feel fresher when you wake up.

Please, please, please see your doctor about the cause of your sleep apnea before treating its obvious symptoms with a device like the WakeMate.

Thanks for the details. I will have a think about what other questions I might like to ask you and will try to fire them over to your contact email in the next day or so.

Since the site doesn't describe this in any detail: can you define 'necessity'? In other words, can you tell us anything about how and when your service decides to scale up or down, for dynos and for workers? And what have you done to avoid porpoising (to borrow an aviation term for lack of a better option coming to mind at the moment.)

Also, can your service scale workers all the way down to zero and then spark up the first worker upon the next job submission? Or can it only scale workers as low as one?

Thanks for that bit of info. At the moment things like Passenger are obscured from my view/concern, as I'm not managing the servers myself, but should that change I'll definitely keep that tidbit in mind.

Regarding backup, I definitely understand the feeling.

AFAIK, if you have a Rails app that will be accepting files from users, Rails is probably not the best thing to use. Ruby likewise, short of using something evented (and I say this as someone thoroughly enjoying working with both Ruby and Rails.) Seeing as you'll be tying up processes rather quickly that way, no?

That aside for the moment, and based on your S3-related comments nested below, I thought I might pop by to mention that I (using Rails on Heroku) have been handling uploads by using direct pre-authorized posting to S3 and it has been very nice to work with.

The tool you mentioned forgetting in your original list is almost surely Terminitor: https://github.com/achiu/terminitor

Very nicely summarized. I would like to add one minor note regarding entertainment, just in case anyone considering Vancouver is a concert addict:

I find myself driving to Seattle for concerts more often than I would like. Lots of acts come to Vancouver but lots of acts skip Vancouver, usually (from what my music biz contacts tell me) because of two main reasons.

1. It doesn't make sense to add a border crossing to their schedule if it would mean doing just one show in Vancouver before returning back to the states or elsewhere.

2. Some acts have also quit coming to Vancouver because the audience attitude has made shows less enjoyable to perform here. It is sad but doesn't surprise me. I have watched audience enthusiasm progressively fade here, during the last decade especially.

You're also right, to a point. :) I suspect that at some point in the past, and perhaps even today for some limited set of careers (though none that would really apply to anyone on HN), the regular job and the infrastructure are at odds more often that one might hope. Given commutes, expectations held by 'regular' employers, etc., so much of this is incredibly restrictive in this day and age.

For your examples and how they apply in my city, at least:

day care - Fingers crossed you never get stuck at work late, or caught in a nasty rush hour, because your day care has very specific pick-up hours, will charge you big-time if you are late, and good ones may very well fire you as a client if you are late too often.

preschool - Pre-school schedules are not even remotely aligned with 'regular' job hours.

sports - As but one example, do you have any idea the hours hockey moms and dads (not to mention the kids) keep so they can take part in their sport? It's no wonder there are hockey parent fight breakouts from time to time. The parents are exhausted! :)

music lessons - This one isn't so bad, especially as kids get older, but can be much like daycare in that if you're late from work your kids either miss their lesson or are stranded afterwards.

I, for one, would much rather restructure my life so as to work from home during hours that I more directly control than work a 'regular' job. It'll be easier to take advantage of much of the infrastructure, and would eliminate my need to even utilize some of it at all.

For some reason I find myself reminded of the whole RIM Playbook "coping with family" faux pas. It is almost as if WP7 were being promoted on the basis of selecting a phone based on wanting to avoid something: in the WP7 case, avoiding using the phone, in the Playbook case, avoiding your family. Both show a disconnect with reality and neither bode particularly well for the companies involved.

Agreed. I am happy with Heroku so far (I am pre-launch so the effect hasn't been great), and intend to stick with them for at least a while (I might have most of two decades as a dev in this business, but zero of those are as a sysadmin), but 45 minutes is low:

I may be showing 48^ errors in my per-minute checks but those errors occurred in at least^ nine separate blocks across an eleven hour window.

In other words, we are probably looking at around ten hours of issues, even if not outright outage.

^ I disabled the checks at times because it was just a waste, so the true stats are likely worse.

US: Netcraft confirms Microsoft is dying.

UK: Netcraft confirm Microsoft are dying.

I figured that either the original situation went over your head or that your post went over mine, so at least now I know which. That and that I should have gotten more sleep last night. :)

At least you were able to work the system there for a good six months. The vast majority of people finding themselves in that kind of work situation don't tend to fare nearly as well as you did.

Don't kid yourself. You were called into those meetings because, like at many companies, there was a promise of time in return for extra time put in but, like at many companies, that promise was never intended to go both ways.

The first meeting was because you dared to utilize their promise and get some time in return.

The second meeting was because their usual course of action in such first meetings backfired on them and you were in the room to get brought back into line (specifically, back onto salary.)

You didn't mention quitting in response or forcing them to give you a raise in acknowledgment of your efforts. Did you?

And why would you think that a novice on the web with Photoshop _couldn't_ do better than a 'professional' with blah blah blah, especially when this new logo is amateur hour at best and utter crap at worst.

I sincerely hope that the entire Internet is being trolled by The Gap on this one, given that the alternative is entirely depressing.

Either that or this logo is legit, meant to last, will work on consumers, and in turn will reduce designer's hourly rates around the world. :)

Not quite. Japan can and does defend itself just fine against neighbours like North Korea, Russia, and China.

The American taxpayer does something different than you state. In actuality, they fund the projection of force everywhere that the US has interests. To relate back to the example of Japan, this means that the American taxpayer funds the defense of the things the US wants from Japan, not truly the defense of Japan itself though the defense of the former can often aid the defense of the latter. This holds true essentially everywhere else the US chooses to project force and the distinction is absolutely critical but too easily forgotten.

EDIT: in case the above sounds a bit too much like some kind of anti-American rant, the point I should have made more explicit in response to the parent is this: parent makes it sound like Japan is restricted from defending itself against the listed neighbour countries and therefore requires outsiders to do so. This is not true, and since it is not true, one should periodically ask themselves why the US has forces there (and everywhere else.)

Don't write Vancouver off quite yet. There's Vancouver and then there's Vancouver. Vancouver proper can be expensive or not so expensive, and then there are the numerous very closely-located suburbs which are less expensive and situated well enough that you can take advantage of everything the Vancouver area has to offer. Heck, in many cases the things Vancouver is known to offer are not in Vancouver itself but rather in those very suburbs.

This area certainly isn't the least expensive in which to live, but it isn't the most either. I can only speak for myself but I find that the view that it is too expensive has been largely blown out of proportion, especially given the benefits the area provides.

For someone bootstrapping it does depend largely on your budget and support system, so if you have any ballpark budget numbers it would be relatively easy to give you an idea of what the Vancouver area would be like on that budget.

"I am amazed at how trivial this error is."

Agreed. However...

"Probably their QA got fired after this event."

I doubt it. I have seen many QA staff at a variety of companies get so used to IE's various oddities that over time they will simply stop opening some kinds of bugs against the site on IE, even perfectly legitimate bugs like that in the article. All it takes is for product management to punt mixed content warning bugs during a few releases before QA also stops reporting them. If someone does later bring one up, over time it evolves into "Oh, that's an IE thing we can't fix." These are smart people doing generally diligent work, but they do tend to get worn down around IE.

I can't say for sure why this happens but I've seen it most with IE mixed content warnings.

I pre-ordered mine (64GB 3G) when they became available for pre-order in Canada.

It has very nearly replaced my computer for casual computer use, leaving my computer for work, occasions where I need to do especially tab-heavy surfing, and the odd bit of Flash usage. My hours of daily casual computing have moved from the office to the living room, kitchen, and deck, something that hasn't happened before even with both a 15 inch and an 11 inch laptop in the home. My girlfriend loves it too, and will grab it from me to pull up a recipe, do a quick search, etc.

It has also proven to be a more-than-capable gaming device running everything from casual match 3 games through light strategy (Strategery is a must) on to board games we can play together (Small World and Carcassone are also musts.)

On the work side, I use it often for background reading (the Apple HIG from front to back, for example, and that isn't a short document), quick bits of research, etc. whether at the desk or as a chance to get away from it for a little while.

One of the best things about it has to be its ability to disappear during use, leaving you sitting or standing with the application in your hands, not a device. Or at least it seems that way, and that is certainly not something that laptops or desktops (or even handheld or living-room-bound game consoles) do particularly well if at all. That you can then set that application down on a table for a moment or hand it to someone else so naturally is something that you will have heard about the iPad but really must experience for yourself a few times to truly understand it. It seems like a small thing but it fundamentally changes one's relationship with computing and the computer.

The iPad can't and won't replace traditional computers for everyone, but from what I have seen and have heard from other purchasers it is certainly proving itself as a device that can replace most 'casual'/'personal' usage of traditional computers for most people most of the time.

I use mine every day and it gets the full 10-11 hours most people are getting for non-gaming activities, somewhat less for gaming activities, and charges way faster than I can drain it (though I haven't tried this while gaming I suspect it'll still be true.)

Something is definitely wrong with your iPad, and you should take it into an Apple Store to have it checked out.

In the current version of WHS (I can't speak for the upcoming "Vail" release) you can think about its redundancy in terms of file-level software RAID 1 without integrity checking.

Pros and cons abound in that setup, of course, but setting aside the lack of integrity checking ala ZFS for a moment, I have personally taken advantage of the file-level software RAID 1 portion when my first WHS server encountered an internal hardware issue and I had to pull its drives (normal NTFS drives full of the files) and bring them online in a replacement WHS server. Each drive was brought online out of the storage pool, its files copied into the pool volumes, and finally the drive was added to the storage pool. It requires an extra drive already in the pool to pull this off, but given that it worked very well, far better than some of the horror stories I've heard about people trying to transplant RAID 5 and 6 setups when other NAS solutions have failed at the server level. A part of me of course wishes for a ZFS-style WHS, and perhaps MSFT will get there some day, but in the meantime I can certainly see how WHS's design decisions were reached.