I just heard of Unicorn / Rainbow as a way to get more out of Heroku workers/dynos. I wonder if this is also compatible, or a better alternative?
I'm new to this whole concept, so am just about to get my feet wet.
Hopefully, Heroku will implement something like this internally, as it seems it would help them to eliminate the greatest flaw with their system - that each deployment require 5-10 seconds of downtime as new dynos are started.
Perhaps in order to resolve this ethical quandry, he should include customizable limiting features when notifications are implemented, much like HN has. This would be unusual in a consumer web product, and might be both a differentiating feature and good for PR.
"bug me no more than once every 4 hours" might be a nice setting.
If you want to create a new framework, why create it in PHP instead of switching to a language that is not deeply flawed?
Any decision to use PHP on a green project seems to me the consequence of either technical decision making incompetence, or personal or organizational inertia, only the last of which is generally excusable.
Using PHP otherwise seems like requiring your organization to use IE7 because you don't have the resources or energy to learn how to upgrade your infrastructure. At best it's a reasonable preservation of resource, but generally it's laziness. Learn something new and good - Ruby, Python, Java, Scala, C#, node, heck even Perl.
I know I'll take hits for this, but seriously - how is continuing to use PHP any more justified than forcing old, flawed technologies like IE 7 unnecessarily on your organization? It's the same stubborn laziness and curmudgeonry - sticking to and forcing on others your bad status quo. PHP is better at nothing than alternatives (except introducing obscure bugs) and worse at so many things .
"If you have a website, we'll send you sample alert code to get working in advance. The next time there's an emergency, we'll tell you and send new code."
Am I the only one who finds this either unnecessarily complicated or technically incompetent?
I'm not familiar enough with the consequences of this change, however it seems likely such a major transition of a fundamental network layer could hardly occur as smoothly as expected.
Perhaps someone knowledgeable can explain what the worst case scenario might be and whether this will be a thorn in our sides for the next 10 years.
I'm not sure what attitude you are referring to. You may be reading a bit too much into this.
I was simply trying to draw some perspective - "really pathetic" is a bit of an overstatement for not linking to Chrome on a browser recommendation page, and we all make plenty of oversights each and every day, so shitting on others for them is bound to undermine your karma.
As an employee, you certainly take a "risk" that your job will not last forever. You may be fired, downsized, or the company may go bankrupt.
Fortunately, since we live somewhere where you can fire, downsize, and go bankrupt, there are companies willing to hire you for some period of time between when they need you and when they don't need you anymore. Otherwise, who would hire anyone if they could never fire them (here's looking at you France)?
The possibility of losing a job is inherent and essential to the concept of employment.
I'm going to assume you've never done anything so pathetic in your life as to leave a web page with something less than the latest, greatest, most open sourcey, freedom-loving information.
Who the hell cares? Take a deep breath of chill the fuck out and don't read so much into things.
I doubt they spent much time debating which browsers to add here, or that this came out of a strategy meeting with Zuckerberg. I wouldn't be surprised if this was designed before Chrome was popular (perhaps with some styling fixes since then).
Even if they did exclude Chrome intentionally, they are entitled to promote whichever browsers they want to promote for whichever reasonable non-evil reasons they want.
Tips can't both be discretionary and an entitlement. That's a contradiction, and I think where the discomfort arises.
Either they are an entitlement - in which case they should be disclosed and added as a fee, or they are discretionary, in which case the servers wages should not be reduced because of the expectation.
Not really. The 10% is required and disclosed, so it is no difference than raising the prices. Tips on the other hand are an imposition since they are both expected and discretionary.
Sure, the 10% could be included in the price and wages raised, but it doesn't make much difference. It's the difference between a VAT tax and a sales tax - in the end the amount is the same - sales tax is just more apparent to the consumer.
I agree. Treat trolls and snappy shitheads like they didn't do anything offensive or annoying. Reward their good behavior and don't respond to their bad. Most will quickly realize that constructiveness instead of belligerence is getting them the attention and respect they seek. Challenging trollish behavior will just force them to attempt to justify their behavior through argument and attitude.
Regardless of anything else, it's wrong that servers are paid less per hour just because tips are common. This places an unfair burden on customers, and took tips from being part of a culture of discretionary generosity to being enshrined law. Since the tip is now required for the server to earn minimum wage, it is no longer a tip but a sort of marginally optional "fee."
IMO, a 10% service charge without expectation of a tip makes much more sense and is much fairer.
The entitlement culture in the service industry is so great that servers will angrily say things like "if you can't afford to tip on a bottle of wine, don't order it or stay home." Yikes. How about I just don't tip you.
> "because of the demographic of people who use rails right now"
What do you see as the problem with the demographic?
While I know historically Rails had a heavy conceited, dickhead user base (in Seattle particularly), the demographic has expanded so much that it doesn't seem to be the case overall anymore.
I occasionally venture into the IRC rooms for Rails, node.js, or some other technology when I need a quick answer that can't be found elsewhere.
I'm always shocked at how stereotypically asinine and snarky the responses to legitimate questions are. Yes it's IRC, yet somehow I expect it not to live up to its reputation - yet it does every time.