The last meaningful America's Cup races were held in the late '80s. Somebody squinted hard enough at the 12-meter rules and entered a multi-hull. Now it's just a matter of who spends the most money on a carbon fiber boat with a wing sail. This is a sailing race of fundamentally unseaworthy vessels. It would be literally be safer to cross an ocean in a dinghy than in one of these monstrosities.
Come September, do yourself a favor. Watch Deep Water on Netflix. Read any book on Ernest Shackleton. Read any Lin and Larry Pardey book. You'll finish all three before the America's Cup race is over, and you'll know more about sailing than watching every second of the America's Cup races.
I have a late 2008 15" MBP on Mountain Lion. It's fine.
Upgrade to the maximum RAM you are capable of. (A good practice at all times.) Mavericks will be a different beast, and it's well worth waiting to see on a 5+ year old machine, but you're probably fine.
It's actually fairly common for construction projects to run into changes. While nobody requests to turn a shed into a skyscraper, large changes that touch many disciplines occur quite regularly.
The difference between AEC and programming projects is a long history and legal framework that deals with these changes. Projects are given a budget, and that budget is often paid out at milestones--design development, 95%, construction documents, etc. If the owner requests a substantial change, or if a change is required because of unknowable circumstances, the budget is either revised or the work is value-engineered to fit--and this reality is reflected in the contract signed at the beginning.
The problem with programming projects is that there are not very many really good programmers, and programming is not suited to throwing more warm bodies at the problem. AEC is plate spinning, while programming is juggling. You can hire a bunch of folks to help keep the plates spinning, but you can't just send in somebody to help juggle.
If you don't like the 2nd Amendment, perhaps we can interest you in gutting the 1st Amendment?
Come come, now, we can all agree that those evil GUNS and evil VIDEO GAMES are ultimately culpable. Let's all come together and blame things that we don't like.
Auto-documentation is good stuff nowadays. Everything changes so much, and so quickly, that enforced documentation standards lead to better understanding of the underlying API or intent.
(As an example, why is PHP so popular? It's not because it's beautiful, or elegant. It is, however, very accessible, largely due to good documentation.)
Good comments--that are not prescriptive for whatever autodoc tool you use--are invaluable, but bad or marginal ones do more harm than good, especially in interpreted languages. You can condense 4 lines of comments into a 22-character, well-constructed function call/local variable and accomplish the same goal.
For extra points you could probably modify the registration process in all kinds of manners which would confound an automated and replay attacks. Chances are that for the average forum it would be sufficient that no script would even bother to defeat it and would simply move onto softer targets.
This is the answer, more or less. For small-to-middling forums, reducing spam is pretty easy. A few volunteers to delete the ones that get through suffices for the rest.
It breaks down to 1) keep out easy drive-by spammers, which means registration with a valid email address and some kind of barrier to detour the smarter bots (ReCaptcha and the like); 2) filter posts through Akismet or similar method; 3) have a community large enough and engaged enough to want to zero out spam posts.
The third step is the hardest, and has nothing to do with spam posts.
And with Net Neutrality, if you don't get good government-regulated service... what?
Or are you pretty confident that the FCC will handle regulating the Internet as well as they do, say, terrestrial radio and broadcast TV?
Yeah, because Rails is being used everywhere.
I doubt that most of the "scalped" tickets are actually sold by scalpers. Most are probably sold by friends and employees of the event and/or venue.
Think about it--before tickets go on sale, roadies and janitors get a chance to buy premium seats at face value, maybe even with an employee discount. The performers don't care, the venue doesn't have to pay employment taxes on this unofficial employee benefit, and the employee gets some extra cash.
How these tools are used and % of userbase that cares about them:
- <- Developers
------------------- <- Everyone else
------------------- <- Developers
- <- Everyone else
Do you really think the average office worker cares about examining mount points or finding out how many USER handles a process is using? That's why Microsoft doesn't ship any of that with Windows, and they probably never will. More importantly, I'd rather have a third party write these kinds of tools. They're not limited by what marketing and support think is a good idea to ship. If Microsoft made them they probably wouldn't be as useful - not to mention everyone would whine about how they're evil because they're killing a niche.
As long as these tools are available, I could care less where I have to get them from or what I couldn't do before I install them. Duh.
It's the perfect computer for a significant chunk of the population. Email, Web, photos, videos. Takes up little space, and doesn't need to have a nerd peer up its asshole every 6 months looking for malware cancer.
Having a way for people with simple needs to get quick medical attention and out of the waiting rooms so that people who do NOT have simple needs is a good idea.
It doesn't matter if the good idea comes from a source you think is compromised. The good idea stands on its own merits.
This is like the self-checkout line at grocery stores. I say they should go for it.