Here is a list of people with behind-the-scenes access to the airport who are not screened upon entry: The McDonald's employee, the guy driving the delivery truck which delivers the buns to McDonald's, the guy putting stuff (hopefully just luggage) into the cargo portion of the plane, the guy who puts fuel in the plane, the mechanic who verifies the plane is in working condition, etc. etc. All of these Jack Bauer conspiracy theories of how things might get on a plane are completely irrelevant.
I've ranted about this plenty of times on slashdot. There is no such program in the US. You can buy a "pay as you go" phone but the cost/minute is generally higher than the contract plans. Bringing your own phone to the deal only grants you the freedom to not sign a contract for a *normal* monthly plan. There is no discount whatsoever.
I could see this... have the front-end and back-end communicate over a socket or something and have a simple delimited message format where someone could alter the results by using a sql-injection style attack on your parser. That way, at least, the input has to be somewhat complex, but the code could look very innocent.
The same was true for Java in its early days and now it's quite fast. I'm no Ruby fan, but I am confident that it will get over its speed issues in time. It's definitely an up-and-comer. Personally I'm pulling for Groovy and GRAILS, but I don't think it'll ever get past being a knockoff.
I think the single greatest thing about the CLI is that it basically doesn't change. I can do pretty much anything in XP you might want in a matter of minutes but when the cable guy installed wireless on my grandfather-in-law's Windows 7 laptop... all I wanted to do was verify he set up encryption properly. It took me a good 20 minutes poking through the GUI to find out it was in fact set up properly. If there was a good command line tool to verify the settings I wouldn't have had to spend all that time figuring out the new GUI configuration system Microsoft made. Considering the linux alternative... 20 years from now there's a pretty good bet that iwlist and iwconfig will still work regardless of whatever the latest and greatest GUI whizbang looks like. I'm not hating on GUIs either, they're really great and I use them most of the time, but having a good knowledge of the command line tools will allow you to function with little re-learning for a long time.
*shrug* At my company I put it in the suggestion box to support some of the open source projects we use. The manager pulled it out and got with a few other development departments and all of a sudden several open source projects got a check for several thousand dollars each last year. I was hoping we'd drop them a $10 spot or something. Not every work place would do that.
I ran into this case last week. My mother in law opened some malware and you can't even boot to command line safe-mode. As soon as you log in it logs you back out and goes to the login screen.:( So today I'm going back with a liveCD to try to get the documents off before doing a wipe.
I hear you on the poor java coding. I work in a shop that's 25% Java, 75% C/C++ (mostly C). You can pick a random class out of our Java code and immediately tell whether it was written by a C programmer or a Java programmer. All public variables, Hungarian notation, no thought for encapsulation or any OOD whatsoever. I'm not even though to get into the 10k line classes, or the 1500 line methods which is bad practice no matter what language. But those things aren't specific to my shop. From what I've seen it's everywhere. There's no escaping it.
The problem seems to me to be the old "do you trust the cloud", i.e. having crucial functions handled by servers beyond your control.
For most businesses I think the question is more "Do I believe the random guy I hired off the street is going to be able to keep the service going better than some outside vendor."
It would be quite a technical feat for Google to take away your privacy. I'm not even sure how that could happen. It's just like Facebook.or your blog. If you don't want that information being out there don't put it out there. If you don't want Google to analyze your searches don't use them or obfuscate them in some way. If you don't want them analyzing your browsing then block their ad script and don't use their browser.
They have a competitor on the board since the competitor elected itself to the board with all the shares which they bought. No one but this competitor is happy with this setup.
Clarification... No one but a significant owner (who just happens to be a competitor) is happy with this setup. It sounds like a diet form of hostile takeover.
That wouldn't work out for me. I buy the afforementioned "loss leader" printers and then buy cheap third party ink cartridges from places like lasermonks or something. Buying the expensive printer up front would just waste money for me. Of course I don't print much so I'm sure it's worth it to some people to have a nicer printer. My "starter ink" lasts me more than a year.
I don't really see that as arrogant. Let's say there's a few engineers in high places that are taking IE in the direction Google prefers (for example: implementing HTML 5 standards). If Google hires those engineers away then it could hurt Google's future. It needs those developers pushing the 500lb gorilla in the room in the direction it wants them to go.
Welcome to the new work force. The company doesn't owe you anything and you owe them nothing in return. Your loyalty to a non-person entity was a waste of your talent and probably cost you a small fortune. It also left you in a position where it will be hard for you to find other work in the work force because you are only familiar with one single way of doing things.
Documentation is the result of poor user interface design. Simple as that. It doesn't matter whether it's Windows, Linux, Apache, IIS, etc. The non-technical user should never have to look at any documentation whatsoever. The technical user should only have to look at documentation if they're scraping the very edges of your software's capabilities.
This raises an interesting question about the "in plain view" laws. For example the police may have a warrant to search your safe. If, in serving that warrant, they see evidence of illegal activity in plain view (like you have some drugs or something on the counter) they can arrest you for it. Does "in plain view" include peering through your walls with radar devices from the street? I suspect it will come to be that way.
The telephone was invented in 1876, making it 133 years old. So telephone technology was 84 years old when you were born. ARPANET first came online in 1969. I bet by 2053 (when the internet turns 84) plenty of people will be saying "I've never gotten in my flying car and not had immediate access to the internet." or some other nonsense.
I think (surely someone will correct me) in the US if you don't actively pursue protection of your trademarks you will lose them. Therefore there can be a case where it's not possible to "selectively enforce" for some intellectual properties.
Slashdot Mirror
Air bags kill more people than terrorists in the U.S.
Here is a list of people with behind-the-scenes access to the airport who are not screened upon entry: The McDonald's employee, the guy driving the delivery truck which delivers the buns to McDonald's, the guy putting stuff (hopefully just luggage) into the cargo portion of the plane, the guy who puts fuel in the plane, the mechanic who verifies the plane is in working condition, etc. etc. All of these Jack Bauer conspiracy theories of how things might get on a plane are completely irrelevant.
I've ranted about this plenty of times on slashdot. There is no such program in the US. You can buy a "pay as you go" phone but the cost/minute is generally higher than the contract plans. Bringing your own phone to the deal only grants you the freedom to not sign a contract for a *normal* monthly plan. There is no discount whatsoever.
I could see this... have the front-end and back-end communicate over a socket or something and have a simple delimited message format where someone could alter the results by using a sql-injection style attack on your parser. That way, at least, the input has to be somewhat complex, but the code could look very innocent.
The same was true for Java in its early days and now it's quite fast. I'm no Ruby fan, but I am confident that it will get over its speed issues in time. It's definitely an up-and-comer. Personally I'm pulling for Groovy and GRAILS, but I don't think it'll ever get past being a knockoff.
I think the single greatest thing about the CLI is that it basically doesn't change. I can do pretty much anything in XP you might want in a matter of minutes but when the cable guy installed wireless on my grandfather-in-law's Windows 7 laptop... all I wanted to do was verify he set up encryption properly. It took me a good 20 minutes poking through the GUI to find out it was in fact set up properly. If there was a good command line tool to verify the settings I wouldn't have had to spend all that time figuring out the new GUI configuration system Microsoft made. Considering the linux alternative... 20 years from now there's a pretty good bet that iwlist and iwconfig will still work regardless of whatever the latest and greatest GUI whizbang looks like. I'm not hating on GUIs either, they're really great and I use them most of the time, but having a good knowledge of the command line tools will allow you to function with little re-learning for a long time.
*shrug* At my company I put it in the suggestion box to support some of the open source projects we use. The manager pulled it out and got with a few other development departments and all of a sudden several open source projects got a check for several thousand dollars each last year. I was hoping we'd drop them a $10 spot or something. Not every work place would do that.
I ran into this case last week. My mother in law opened some malware and you can't even boot to command line safe-mode. As soon as you log in it logs you back out and goes to the login screen. :( So today I'm going back with a liveCD to try to get the documents off before doing a wipe.
Hmm, I'm creating a new programming language to run on the CLI. Perl#. It's natural state is obfuscated.
I hear you on the poor java coding. I work in a shop that's 25% Java, 75% C/C++ (mostly C). You can pick a random class out of our Java code and immediately tell whether it was written by a C programmer or a Java programmer. All public variables, Hungarian notation, no thought for encapsulation or any OOD whatsoever. I'm not even though to get into the 10k line classes, or the 1500 line methods which is bad practice no matter what language. But those things aren't specific to my shop. From what I've seen it's everywhere. There's no escaping it.
The problem seems to me to be the old "do you trust the cloud", i.e. having crucial functions handled by servers beyond your control.
For most businesses I think the question is more "Do I believe the random guy I hired off the street is going to be able to keep the service going better than some outside vendor."
How is this particularly different from what brick and mortar stores do?
It would be quite a technical feat for Google to take away your privacy. I'm not even sure how that could happen. It's just like Facebook.or your blog. If you don't want that information being out there don't put it out there. If you don't want Google to analyze your searches don't use them or obfuscate them in some way. If you don't want them analyzing your browsing then block their ad script and don't use their browser.
Little did you know I keep a camera in my car and take pictures of you every day during your commute. Nice pants.
I don't get Google fanboyism. I really don't. Every time something like this happens...
What exactly has happened?
They have a competitor on the board since the competitor elected itself to the board with all the shares which they bought. No one but this competitor is happy with this setup.
Clarification... No one but a significant owner (who just happens to be a competitor) is happy with this setup. It sounds like a diet form of hostile takeover.
That wouldn't work out for me. I buy the afforementioned "loss leader" printers and then buy cheap third party ink cartridges from places like lasermonks or something. Buying the expensive printer up front would just waste money for me. Of course I don't print much so I'm sure it's worth it to some people to have a nicer printer. My "starter ink" lasts me more than a year.
I don't really see that as arrogant. Let's say there's a few engineers in high places that are taking IE in the direction Google prefers (for example: implementing HTML 5 standards). If Google hires those engineers away then it could hurt Google's future. It needs those developers pushing the 500lb gorilla in the room in the direction it wants them to go.
Welcome to the new work force. The company doesn't owe you anything and you owe them nothing in return. Your loyalty to a non-person entity was a waste of your talent and probably cost you a small fortune. It also left you in a position where it will be hard for you to find other work in the work force because you are only familiar with one single way of doing things.
Documentation is the result of poor user interface design. Simple as that. It doesn't matter whether it's Windows, Linux, Apache, IIS, etc. The non-technical user should never have to look at any documentation whatsoever. The technical user should only have to look at documentation if they're scraping the very edges of your software's capabilities.
This raises an interesting question about the "in plain view" laws. For example the police may have a warrant to search your safe. If, in serving that warrant, they see evidence of illegal activity in plain view (like you have some drugs or something on the counter) they can arrest you for it. Does "in plain view" include peering through your walls with radar devices from the street? I suspect it will come to be that way.
The telephone was invented in 1876, making it 133 years old. So telephone technology was 84 years old when you were born. ARPANET first came online in 1969. I bet by 2053 (when the internet turns 84) plenty of people will be saying "I've never gotten in my flying car and not had immediate access to the internet." or some other nonsense.
I think (surely someone will correct me) in the US if you don't actively pursue protection of your trademarks you will lose them. Therefore there can be a case where it's not possible to "selectively enforce" for some intellectual properties.
In my county the firemen work 24 hours on 48 hours off. So they do in fact spend quite a bit of time watching DVDs and sleeping.
No worries, most of the code where I work appears to have been written while inebriated.