The sampling part is why I switched to Piwik (now named Matomo) about three years ago. It really sucks trying to find rare events with GA when all of the reports have such a small sample. We had problems that were happing thousands of times a day that wouldn't show-up on Google Analytics.
And Apple stores took down the signs showing which model is which and the prices. I went in December to buy a new phone, but I couldn't tell which model was which or how much they cost. This will make their model confusion even worse.
That's even more frustrating after you waste a bunch of time debugging then when you resort to starting the service at the commandline, it shows a clear error message.
More and more of our customers are switching to Outlook, so it's a pain to train people to save the file and run tnef at the command line. Yes, it's proprietary, but Microsoft is pushing it hard so the problem is just going to get worse.
I disagree that SMART data helps with diagnosing failures. I save the output of "smartctl -a/dev/?" every night for every drive on every server. I haven't seen anything that predicted the huge number of SSD failures that you have with heavy use. We started using them three years ago when we started buying servers with 2.5" drive bays. I think we've replaced the ~75 drives about 120 times. Yes, more than once. If someone could come up with a predicting failures then they will become rich.
And,,the start menu is slow as crap. After a reboot, it can take almost twenty minutes to show the first time. I wish I could disable them, but I use a lot of different servers we use for QA so we have to keep them as close as we can to the customer setup.
> Anything less than a gigabit per second simply isn't broadband,
Did you mean megabit per second? A lot of the country can't get connections that fast. I'm at a friend's apartment now that lives a few hundred yards from Microsoft Redwest. Frontier is the phone monopoly here, and they only offer 1.5 Mbps DSL in his complex which is faster than what I have at home right now.
I hope so! I work on scheduling and time clock software that is hardcoded to LA time but we're based out of Seattle, so this is going to suck. Some of our COBOL code is over 38 years old. I'm still manually fixing employee clock ins that happened Sunday morning during the clock fallback to give them an extra hour of pay. Again, this is going to suck.
Same here. I spent a lot of money on nice headphones, and I enjoy music so there's no way I would downgrade to BT. Plus, the fact that I use them for hours a day means keeping the batteries charged would be a pain.
They're forgetting that education made the company originally and music saved it later. Dropping headphone jacks will be a huge pain and expense for education. I teach a high school comp sci class twice a week, and it's already a huge pain to keep the iPads charged. There's no way the school will be able to afford BT headphones and deal with the hassle of keeping them charged. Also, the best headphones are all wired.
If their protest was blocking the entrance to Google so people couldn't get to work, then it would be effective. Not saying that's right, but it would work.
I think that spoke more to the terrible quality of QA that Microsoft had. When you pay less than you can make at a local McDonald's, then of course you're going to either get unqualified or unmotivated people.
> didn't care to investigate any possible other mitigations
To be fair, I don't think Microsoft has the expertise on staff to do that. They got rid of most of their more experienced devs in order to save money. Several friends that are great devs got fired since they were so good at their jobs they couldn't be promoted, but Microsoft fires you if you don't get promoted enough. Their system gets rid of the people that are the best at their jobs.
It's only 72 hours a week as compared to 16 Mon-Thu and 12 Fri-Sun.
The sampling part is why I switched to Piwik (now named Matomo) about three years ago. It really sucks trying to find rare events with GA when all of the reports have such a small sample. We had problems that were happing thousands of times a day that wouldn't show-up on Google Analytics.
And what are the purposes of each besides to render HTML?
You might can avoid them, but Comcast's Javascript that broke our web site is pretty much unavoidable.
https://www.apple.com/iphone/compare/
And Apple stores took down the signs showing which model is which and the prices. I went in December to buy a new phone, but I couldn't tell which model was which or how much they cost. This will make their model confusion even worse.
Grocery stores don't hide name-brand items on the shelf behind their own.
That's even more frustrating after you waste a bunch of time debugging then when you resort to starting the service at the commandline, it shows a clear error message.
I guess that depends on if Microsoft is a competitor. My employer has asked all employees to delete our LinkedIn profiles after abuse by Microsoft.
More and more of our customers are switching to Outlook, so it's a pain to train people to save the file and run tnef at the command line. Yes, it's proprietary, but Microsoft is pushing it hard so the problem is just going to get worse.
Still better than Microsoft that has a lawyer as president.
since Comcast doesn't offer service over their entire monopoly area.
I disagree that SMART data helps with diagnosing failures. I save the output of "smartctl -a /dev/?" every night for every drive on every server. I haven't seen anything that predicted the huge number of SSD failures that you have with heavy use. We started using them three years ago when we started buying servers with 2.5" drive bays. I think we've replaced the ~75 drives about 120 times. Yes, more than once. If someone could come up with a predicting failures then they will become rich.
You forgot to mention SF with poop on the sidewalks.
And, ,the start menu is slow as crap. After a reboot, it can take almost twenty minutes to show the first time. I wish I could disable them, but I use a lot of different servers we use for QA so we have to keep them as close as we can to the customer setup.
> Anything less than a gigabit per second simply isn't broadband,
Did you mean megabit per second? A lot of the country can't get connections that fast. I'm at a friend's apartment now that lives a few hundred yards from Microsoft Redwest. Frontier is the phone monopoly here, and they only offer 1.5 Mbps DSL in his complex which is faster than what I have at home right now.
I hope so! I work on scheduling and time clock software that is hardcoded to LA time but we're based out of Seattle, so this is going to suck. Some of our COBOL code is over 38 years old. I'm still manually fixing employee clock ins that happened Sunday morning during the clock fallback to give them an extra hour of pay. Again, this is going to suck.
Same here. I spent a lot of money on nice headphones, and I enjoy music so there's no way I would downgrade to BT. Plus, the fact that I use them for hours a day means keeping the batteries charged would be a pain.
They're forgetting that education made the company originally and music saved it later. Dropping headphone jacks will be a huge pain and expense for education. I teach a high school comp sci class twice a week, and it's already a huge pain to keep the iPads charged. There's no way the school will be able to afford BT headphones and deal with the hassle of keeping them charged. Also, the best headphones are all wired.
If their protest was blocking the entrance to Google so people couldn't get to work, then it would be effective. Not saying that's right, but it would work.
I think that spoke more to the terrible quality of QA that Microsoft had. When you pay less than you can make at a local McDonald's, then of course you're going to either get unqualified or unmotivated people.
And don't finish the UI changes you start. See the control panel.
Just sucks that Microsoft has gotten rid of so many good employees that they can't finish that task they started over five years ago.
> didn't care to investigate any possible other mitigations
To be fair, I don't think Microsoft has the expertise on staff to do that. They got rid of most of their more experienced devs in order to save money. Several friends that are great devs got fired since they were so good at their jobs they couldn't be promoted, but Microsoft fires you if you don't get promoted enough. Their system gets rid of the people that are the best at their jobs.
like the rumors. It's weird how Apple so often forgets how much they make off of music.
And have a source address that isn't blackholed since most cable and DSL IP addresses are blacklisted.
Or goatse.cx