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.
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.
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.
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.
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.
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.