Sure it does- we'll know what we're buying. And when they have to advertise 3 GB caps, the first carrier to offer 4 GB for the same price will get an advantage, forcing them to compete on data caps. But right now most people think they actually have "unlimited".
No, it is absolutely for a government agency, as everything in this post proves shows you are NOT capable of making such a decision. Thanks for proving my point for me.
And living near San Francisco, there's streets my mother or grandmother wouldn't be able to climb. Even most locals won't walk in those areas. We can't control nature, but that's no excuse for not doing better than that when we can. Out of all the point of the ADA that could use fixing, you picked the one that makes perfect sense to complain about?
The 9th circuit is the largest court with the most cases. So of course it has more overturned. When viewed by percentages they're one of the least overturned courts. The whole "9th is the most overturned court" meme is from Republican wishful thinking trying to downplay importance of cases out of there,
I wish I had some modpointa today. Competing for driver attention=causingcrashes=people die. Unless your app is for passengers only, it shouldn't fucking exist.
People who want cross-platform on iOS and Android have had it since day 1. Write your logic in C or C++. Its how cross-platform has been done for decades. Then write a wrapper in whatever language the platform uses for the UI.
If your complaint is that you want cross-platform Ui code as well- no you really don't. The two platforms are so different that you'll never get an app with a good look and field without writing 2 separate UIs. Unless you want to release an Android like UI for Apple (which will get hatred from users) or an iOS like UI for Android (which will get hatred from users).
Because reaching your customers directly is hard. If it was easy, nobody would sign up for these services. Its especially hard for a small business like these- you expect them not only to be master craftsmen, but master marketers, master SEOs, and master businessmen as well? And do all of it in the span of a working day? Not exactly realistic. Now alternatives competing on margin- that can and will happen. Amazon isn't even the first here. Some of them, like ANgie's list, are paid for by monthly subscriptions.
Does it matter? I'd think Amazon will be happy to grab a percentage on as many of them as they can. 20% of 50% of transactions > 20% of 0% of transactions.
Even when running on Exchange I've never seen recall actually work. I've gotten "Would like to recall" messages by the dozens. It never actually deleted the email.
Great. Then you don't mind if I take a hit out on your life? I mean, its just a contract, the fact its to kill someone doesn't outweigh my liberty to enter into it, does it?
Congratulations, you've just said the stupidest thing I've ever read on the internet. That includes "Where does babby come from".
THey have a careers subpage. I would be willing to bet its got a form or two, and that's *very* personal info. I would also be willing to bet there's internal pages hosted on that website with logins.
Besides that, HTTPS would protect what pages you're visiting (even if plaintext knowing you're going to pages on, say worker's comp benefits is private information) allowing packet sniffers to only know what server you're hitting and not the exact page.
Remember- its not always what's on the page, its the fact you went to a specific page too.
There is absolutely no reason to use HTTP for anything. Encrypting the connection costs very little, prevents you from having stupid mistakes by not encrypting things that need to be, and provides enhanced privacy to things you may not realize that person is sensitive on. There's no reason NOT to make HTTPS everywhere.
Its almost 0 government websites. Do you really think that there's any of those that don't have at least 1 form or login, even if only for employees? I doubt there's even one. Unsecured http is dieing, and good riddance to it.
There was an ice age 10K years ago. So there are definitely longer term weather patterns on this planet. That's not evidence for or against global warming, but to claim we understand the climate well is disingenuous at best.
It didn't put either of us at a disadvantage. We had enough to destroy them 10x over. Being able to do it 20x over doesn't make us any more powerful. Now when you start getting down towards the 1x threshold you might have a point.
-You seem intent on sticking to your view regardless of all the evidence to the contrary -You call everybody else "shitty programmers" for using auto yet you can't explain what you don't like about it.
The reason they're useful for iterators is that they fucked up iterators. There should have been a base abstract iterator class with child classes for the various types/classes. Then you could have just declared it as an iterator* and not worried. Rather than providing bad patches they should fix the initial problem. Patching on mistakes just leads to problems.
If you want to use auto, go to a dynamically typed language. Strong typing is a feature, it prevents bugs and saves time and effort in maintenance. If you use auto, you're a shitty programmer. Auto solves NO problems except the number of characters you need to type when declaring stl iterators. Its a bad feature used to patch over other poorly designed features. Which basically describes almost all of the additions in the last 10 years to C++.
Float for autos- someone used the wrong version of a library function that returned float to initialize the auto. Kid was new, he didn't know the effects it would have. Auto wasn't the bug, but without auto the bug wouldn't have existed- the problem would have been minimized to a single call and caused a compiler warning that we would have caught and fixed. Auto made the bug worse.
No, I've used C++ in a very normal environment. STL container classes- used all over the place. The algorithms library? More complicated, harder to understand, and much harder to maintain. Very few places use that. And they shouldn't- while min and max aren't too bad, I would always prefer to see an explicit loop with the code embedded in the loop than a function call where I have to hunt down a functor (another thing that should never have come to be) to find out what the fuck is actually being done.
If you want to write Ruby- use Ruby. Keep that shit out of C++.
I'm cool with nullptr for 0. But auto absolutely causes bugs. I've seen it, where programmers assume the auto datatype is one thing and it turns out to be another. It was a major performance issue in a program I debugged. Turns out the compiler assumed they were using floating point where they wanted to use int, and the processor didn't have a floating point unit, so it was all emulated in software. Unfortunately it wasn't found until after release.
In addition, it decouples the data type from the code in maintenance. Want to know what that auto loop is actually doing? You need to find and check wherever the container was defined. This takes time, and leads to bugs when maintainers forget or make the wrong assumption. For saving 10 characters at writing time you cost orders of magnitude that when maintaining the code.
Furthermore- the reason for auto was they fucked up the STL by adding too many features (allocators) and insisting on their algorithms library (which in 15 years of writing C++, I have never seen used) being compatible with pointers as well without using a wrapping class. Stupid, stupid ideas. You don't perpetuate mistakes with new features which add new problems- you correct them.
I completely understand the new features of C++- I just think the vast majority are a bad idea.
Then you're extremely lucky, I've had iOS hard lock when dogfooding apps fairly frequently (although that was a few years ago, maybe they're better). But I don't trust ANY device without a real pull the plug option, not after years of doing firmware and mobile development. If a device needs batteries, I will not buy it unless those batteries are removable.
I wish people would stop adding to C++. C++ as it stood in 1998 was a good, if somewhat complex, language. The new additions (except for a few of the libraries) make the language way too complex and lead to unreadable code.
You need to learn that concise != good. If it did, everyone would be programming in perl 1 liners. Auto is the most braindead addition in history, it causes bugs, loses all the advantages of a typed language, and only needs to exist because they fucked up the STL by not using proper inheritance. Any code review that uses them is an auto bounce and fix. Templates are the most abused language concept in history- if you're using it for anything other than a container class, odds are 98% that you're writing hard to follow, hard to maintain code that should be rewritten
Slashdot Mirror
Sure it does- we'll know what we're buying. And when they have to advertise 3 GB caps, the first carrier to offer 4 GB for the same price will get an advantage, forcing them to compete on data caps. But right now most people think they actually have "unlimited".
No, it is absolutely for a government agency, as everything in this post proves shows you are NOT capable of making such a decision. Thanks for proving my point for me.
And living near San Francisco, there's streets my mother or grandmother wouldn't be able to climb. Even most locals won't walk in those areas. We can't control nature, but that's no excuse for not doing better than that when we can. Out of all the point of the ADA that could use fixing, you picked the one that makes perfect sense to complain about?
The 9th circuit is the largest court with the most cases. So of course it has more overturned. When viewed by percentages they're one of the least overturned courts. The whole "9th is the most overturned court" meme is from Republican wishful thinking trying to downplay importance of cases out of there,
I wish I had some modpointa today. Competing for driver attention=causingcrashes=people die. Unless your app is for passengers only, it shouldn't fucking exist.
People who want cross-platform on iOS and Android have had it since day 1. Write your logic in C or C++. Its how cross-platform has been done for decades. Then write a wrapper in whatever language the platform uses for the UI.
If your complaint is that you want cross-platform Ui code as well- no you really don't. The two platforms are so different that you'll never get an app with a good look and field without writing 2 separate UIs. Unless you want to release an Android like UI for Apple (which will get hatred from users) or an iOS like UI for Android (which will get hatred from users).
Because reaching your customers directly is hard. If it was easy, nobody would sign up for these services. Its especially hard for a small business like these- you expect them not only to be master craftsmen, but master marketers, master SEOs, and master businessmen as well? And do all of it in the span of a working day? Not exactly realistic. Now alternatives competing on margin- that can and will happen. Amazon isn't even the first here. Some of them, like ANgie's list, are paid for by monthly subscriptions.
No they don't. At least not in the US. Do you think the guy who drives a train has a state certification? And they're the originals.
Does it matter? I'd think Amazon will be happy to grab a percentage on as many of them as they can. 20% of 50% of transactions > 20% of 0% of transactions.
Even when running on Exchange I've never seen recall actually work. I've gotten "Would like to recall" messages by the dozens. It never actually deleted the email.
Great. Then you don't mind if I take a hit out on your life? I mean, its just a contract, the fact its to kill someone doesn't outweigh my liberty to enter into it, does it?
Congratulations, you've just said the stupidest thing I've ever read on the internet. That includes "Where does babby come from".
THey have a careers subpage. I would be willing to bet its got a form or two, and that's *very* personal info. I would also be willing to bet there's internal pages hosted on that website with logins.
Besides that, HTTPS would protect what pages you're visiting (even if plaintext knowing you're going to pages on, say worker's comp benefits is private information) allowing packet sniffers to only know what server you're hitting and not the exact page.
Remember- its not always what's on the page, its the fact you went to a specific page too.
There is absolutely no reason to use HTTP for anything. Encrypting the connection costs very little, prevents you from having stupid mistakes by not encrypting things that need to be, and provides enhanced privacy to things you may not realize that person is sensitive on. There's no reason NOT to make HTTPS everywhere.
Its almost 0 government websites. Do you really think that there's any of those that don't have at least 1 form or login, even if only for employees? I doubt there's even one. Unsecured http is dieing, and good riddance to it.
Which is why Iran never went to war with Iraq.
Oh, wait.
There was an ice age 10K years ago. So there are definitely longer term weather patterns on this planet. That's not evidence for or against global warming, but to claim we understand the climate well is disingenuous at best.
It didn't put either of us at a disadvantage. We had enough to destroy them 10x over. Being able to do it 20x over doesn't make us any more powerful. Now when you start getting down towards the 1x threshold you might have a point.
In what world do PCs have a standard hardware model?
Case size/shape- nope.
Cpu socket- nope.
RAM type- nope.
Peripheral bus- nope.
The only thing that all PCs have in common is a CPU instruction set. And not even 100% on that (x86-64 or IA64 was a battle not too long ago).
Pot. Kettle.
Yup that too.
The reason they're useful for iterators is that they fucked up iterators. There should have been a base abstract iterator class with child classes for the various types/classes. Then you could have just declared it as an iterator* and not worried. Rather than providing bad patches they should fix the initial problem. Patching on mistakes just leads to problems.
If you want to use auto, go to a dynamically typed language. Strong typing is a feature, it prevents bugs and saves time and effort in maintenance. If you use auto, you're a shitty programmer. Auto solves NO problems except the number of characters you need to type when declaring stl iterators. Its a bad feature used to patch over other poorly designed features. Which basically describes almost all of the additions in the last 10 years to C++.
Float for autos- someone used the wrong version of a library function that returned float to initialize the auto. Kid was new, he didn't know the effects it would have. Auto wasn't the bug, but without auto the bug wouldn't have existed- the problem would have been minimized to a single call and caused a compiler warning that we would have caught and fixed. Auto made the bug worse.
No, I've used C++ in a very normal environment. STL container classes- used all over the place. The algorithms library? More complicated, harder to understand, and much harder to maintain. Very few places use that. And they shouldn't- while min and max aren't too bad, I would always prefer to see an explicit loop with the code embedded in the loop than a function call where I have to hunt down a functor (another thing that should never have come to be) to find out what the fuck is actually being done.
If you want to write Ruby- use Ruby. Keep that shit out of C++.
I'm cool with nullptr for 0. But auto absolutely causes bugs. I've seen it, where programmers assume the auto datatype is one thing and it turns out to be another. It was a major performance issue in a program I debugged. Turns out the compiler assumed they were using floating point where they wanted to use int, and the processor didn't have a floating point unit, so it was all emulated in software. Unfortunately it wasn't found until after release.
In addition, it decouples the data type from the code in maintenance. Want to know what that auto loop is actually doing? You need to find and check wherever the container was defined. This takes time, and leads to bugs when maintainers forget or make the wrong assumption. For saving 10 characters at writing time you cost orders of magnitude that when maintaining the code.
Furthermore- the reason for auto was they fucked up the STL by adding too many features (allocators) and insisting on their algorithms library (which in 15 years of writing C++, I have never seen used) being compatible with pointers as well without using a wrapping class. Stupid, stupid ideas. You don't perpetuate mistakes with new features which add new problems- you correct them.
I completely understand the new features of C++- I just think the vast majority are a bad idea.
Then you're extremely lucky, I've had iOS hard lock when dogfooding apps fairly frequently (although that was a few years ago, maybe they're better). But I don't trust ANY device without a real pull the plug option, not after years of doing firmware and mobile development. If a device needs batteries, I will not buy it unless those batteries are removable.
If the phone is locked up, yes. Same thing for your computer and everything else. Hardware off switches are a rarity these days.
I wish people would stop adding to C++. C++ as it stood in 1998 was a good, if somewhat complex, language. The new additions (except for a few of the libraries) make the language way too complex and lead to unreadable code.
You need to learn that concise != good. If it did, everyone would be programming in perl 1 liners. Auto is the most braindead addition in history, it causes bugs, loses all the advantages of a typed language, and only needs to exist because they fucked up the STL by not using proper inheritance. Any code review that uses them is an auto bounce and fix. Templates are the most abused language concept in history- if you're using it for anything other than a container class, odds are 98% that you're writing hard to follow, hard to maintain code that should be rewritten
C== was better when it was treates as C++98.