It says iphones and blackberrys are equally affected.
3,809 karma · joined January 27, 2009
It says iphones and blackberrys are equally affected.
I think that, given another year, they might be able to get decent traction. Their biggest problem of course is going to be marketing and, historically, that's always been Microsoft's biggest problem.
Businesses use the country's infrastructure just as much as the citizens. They want police so they don't get robbed, they want roads and a post office, they want electricity for their buildings and sewers and all the other stuff taxes pay for.
If you're making millions of dollars a year you're probably only spending a small fraction of it and if there's only sales tax you pay tax on a percentage of what you spent. So let's say you made 30 million dollars and spent 8 and say the sales tax rate is 15%. In this case you paid 1.2MM in tax for a marginal tax rate of 4%.
On the other hand if your income is 15k you're probably spending it all or very close. In which case your marginal tax rate is 15%.
Not all that fair I'd say.
Personally I like the progressive income tax method. I just think capital gains should be taxed as income rather than at a flat 13% and no special rules for corporations either. If they want to be people they can be taxed like people. If they want to be different then we can just get rid of corporate personhood. I doubt they'd like that much.
The base system was 280+ mb along with 190+ mb of documentation. I found it mildly amusing that I had to download ~500 mb of stuff just to update my cv.
I imagine only a few of the big guys (yahoo, microsoft, google) could handle large unexpected volumes without hiccup.
Obviously eBay must see other reasons for the acquisition than just the tech itself.
Also, if it's also in large part a talent acquisition then they're going to paying more than 80 million since they're going to need to pay for some new pairs of golden handcuffs to keep the talent around.
Netflix had their own and paid a million dollars as prize payout for an absolutely state of the art system.
If it really was just a tech acquisition they massively overpaid.
It's Europe, where netflix hasn't launched yet, that is left in the cold.
Then you can do some research on company x and try to get in touch with someone there.
For the first few episodes, each main character is going to get a recap episode of what they've been up to.
(Now my personal opinion:) Of couse, the other characters are going to show up but I think it's a very original catching up if they do it from each character's perspective. It will allow for a deeper understanding of their world and when they bring things back into a meld it will be that much more funny because of the conflicts set up in the first few episodes.
If you mean why is it a problem at all, it's usually because of database size. On any large scale deployment (ie you have at least a million users) schema modifications will take hours. The only way to do reliable schema modifications is to have extra capacity and do it in stages. Also, your forward changes have to be backwards compatible. (AKA you're not allowed to both add and remove a column at the same time.)
The way to do it is to take some of your slaves out of the request pool and run the alter tables on them. You do this many times depending on your available capacity. (You probably can't just rip out half your slaves, you probably need to do at least 3 batches.) After you've altered all your slaves you can promote one to master and take the master offline to do its own alter. Then you push the code changes to production and add the old master back into the pool as a slave once it's done its alter.
In this scenario you need 3x the time the alter takes. So if the alter takes 6-7 hours (common in mysql if you have a large-ish table) it's going to take you at least 18 hours before you can push your code that depends on a database change.
Doing this manually at scale instead of an automated deployment process is extremely risky and will almost certainly be screwed up often.
This is one of the main reasons people are hoping schemaless databases work out in practice.
Maritz says VMware doesn’t have a concentrate plan for making money from Cloud Foundry. “A leap of faith,” he calls it.
I imagine the obvious business model though is to position themselves as the world experts on this platform and provide hosting and support to enterprise customers that would rather pay a premium for peace of mind as opposed to startups that would shop around for the cheapest option.
The poor performance is probably mostly due to the fact that the version of android on the fire is version 2.2.
Version 2.3 is the one that got all the performance improvements. There's a very big difference between the responsiveness of a phone on 2.2 and the same phone upgraded to 2.3.
At first we would only treat urls with certain file types (jpg, png, mp4, etc) as files when found on the server, the rest as pages and we switched from a whitelist of file types to anything that had an asset directory path in the url. Our original htaccess rules were definitely deficient. The idea was that we wanted tracking pixels and the like to be able to run code.
I haven't used it but I wouldn't put much faith in a "review" by an Apple fanboy who refuses to port his hugely popular instapaper app to Android because he hates it.
In the later afternoon a marketing guy on the traffic team came over and told me there was a problem with our trial signups. They'd dropped ~7% today for no apparently reason. We looked at the charts and today, for most of the day, compared to many other days and the past week there was indeed a dip. There were no changes to their marketing campaign or traffic levels either so they concluded it was a software bug.
But we hadn't pushed any new code that day. All that got pushed was some css changes from a designer so I concluded that it couldn't be a dev problem. I started looking from an ops perspective but couldn't find anything abnormal there either. There weren't a lot of memcached evictions, the db was doing fine, server loads were normal, etc.
I spent easily a couple of hours trying to find the source of the problem when marketing found it for me. Someone else was going through the metrics and noticed that we had the same trial signup rates for firefox, chrome and mobile browsers, it was only ie that had dropped. When filtered by ie and broken down by browser version he noticed that IE9, IE8 and IE7 were all the same as other days but IE6 had a 0%.
When you signed up to our site you signed up as a free member but were immediately offered a 5 day trial for a premium account and we had enough volume that the signup rates were predicatable and didn't vary much. When I created an account with IE6 it put me directly into the home page without showing me the trial offer page first.
Turns out the problem was indeed from the stylesheet change. The designer had not only changed a couple of buttons, he'd also added a font-face declaration. This font-face was not yet used anywhere and the font itself hadn't been uploaded to assets in production. What happened was IE6 would try to download the font-face and, when logged into our site we don't output 404 for pages that don't exist we redirect to the home page. So IE6 would get the redirect inside a stylesheet and follow that redirect in the browser. All the later IEs and other browsers simply ignored the redirect.
It was a very strange bug that would've resolved itself on its own the next day when the designer actually used and uploaded the font but it sure gave me a lot of head scratching and I never would've found it without the analytics.
What I mean by this is that when you come across some common engineering problem, if you've never seen it before, you'll spend a lot of time trying to re-invent the wheel, probably very badly. That's why engineering programs spend so much time on fundamentals and so much time on studying because when you hit a similar problem you're supposed to have a switch go off and say wait, I've seen something similar before, know where to head to do your research and find a solid answer.
So yes, the cramming and huge amount of coursework is "mostly useless" but in reality just having gone through all that work turns out to be a real boon later in life.
(I went through a Computer Science/Software System degree but have many SOEN/Mech/Civil/Indu friends.)
The school gives this guy a great amount of latitude and it's great that they do because he's truly knowledgeable, does a lot of research and helps his students a lot.
But, for every one of him, there are many others that, given the same latitude, will instead foist their pre-conceived ideas on students and insist that their view of sexual life, however either perverted or abnormally repressive it may be, is the way to go.
It's a hard problem with no easy solution because it involves a great many number of humans.
I really wish all sex-ed could be as great as this school has but I feel like a pessimist when I say that if that amount of latitude was given to every teacher that there would be a regular and constant amount of disasters created.
(Though I do agree that we can do way way better than our current sex-ed curriculum which is absolutely abysmal.. we need something that will at the very least address and provide some counter-points to the vast amounts of hardcore pornography now easily accessible.)
It was founded in 1994. It had its IPO in 1997. It posted its first net profit in 2002.
It lost money for 8 years. Hardly "something that was viable immediately".
On the other hand it didn't take that much investment before IPO. It was seeded with 300K from Bezos and his family followed by 50K in angel money and finally an 8MM round.
http://www.quora.com/Who-were-the-original-investors-in-Amaz...
It rode the cheap cash infusion from the dot com bubble for as long as it could until the bubble collapsed. At that point it had cash but was going to run out eventually which is why I imagine they decided then it was time to try and make the company profitable rather than expand through investment.
The real reason I wouldn't use dwolla for a consumer web transaction over my credit card is not the credit aspect but the risk aspect. With a credit card I'm protected against fraud fairly well whereas with debit or dwolla the protection isn't nearly as good.
Let's say you renegotiate down 50% like you suggested. That means from now on you make 50% and before you made 100%.
A vesting schedule though almost always accelerates towards the end. So if you renegotiate down 50% towards the end you may in fact be likely losing 75% or more. That's the problem with renegotiating stock grants/options, you likely still have a large amount left unvested and you put in all the hours and work beforehand with the promise that loyalty would be rewarded over time.
"One lawyer said that over the past year, he has heard executives of three social-media sites discuss the possibility of clawing back equity from some employees. Another lawyer, who has handled stock-compensation issues with technology companies for decades, said he never saw a company try to take equity from employees until about two years ago, but has since seen three such cases at start-ups."
I don't see how this is anything other than theft. They're saying that either you give us some of your compensation back (you may not have joined if it were not for those stock options/grants) or you're fired and lose it all. Insane.