Your sarcasm is counterproductive. It's not supposed to be a police state. Hopefully this case will pull back the expanded powers a little, and everyone in this country at least should be on that side, because it would probably not be possible to "undo" these expanded powers without this case.
I remember using MFC, and finding very common problems had no MFC equivalent. I had to either call Win32 directly (which is fine for uncommon problems), or futz about updating poorly documented auto-generated code that I didn't understand well enough to be in there making changes. This is because MFC project team just couldn't predict what would be common, and it's the reason OP is having issues, and the reason I avoided toolkits until I couldn't any longer.*
It's very important to be able to tell a product what you want/need, and with open source you get the opportunity to be very clear, in the form of submitting patches.
*I usually drop a toolkit when I realize that a very common function requires several lines of code and an extra variable, such as "Does this directory name end in a terminator, or should I add one?" Especially if it's a platform-specific one that doesn't address the quirks of that platform.
Technology moves so quickly that for a lot of people 1 year or 3 years is more than enough time. If it breaks you get to upgrade. Also, it's hard to find a competing product with a longer warranty so the manufacturers don't/can't get the feedback.
I think people are more willing to spend money separately, and also looking for lower prices. So a $100 product looks more attractive when you take off $10 sold as the store's "replacement program" and make a $90 product with less warranty. Then the $90 product looks like a better deal without the in-store warranty alongside the "I'll upgrade when it breaks" idea.
"Amy" is a nice alternative in my neighborhood, and of course the street address itself is pretty helpful if you run out of ideas. Me, every time someone new moves in I switch mine to impersonate someone else's name or street number. Not sure what I think I'm accomplishing now that I think about it. But at least I'm not leaving it the default.
(But always with a password set of course.)
And that's the user's entire google groups profile. How is it this was posted twice, in its entirety, then 5 years later sent one by one back to the person who sent them (Rob)? "This guy would send us one of these at the end of the week for almost a year."
If you end up searching someone's stuff, and find a bunch of suspect photos, it's a lot easier to write a law that says it's illegal even if it's fake, than to have to go to court and prove that a real child was harmed.
I think that's the real reason behind this - to make enforcement of corner cases into actual clear-cut evidence. People get convicted on the basis of bad laws all the time.
for example, having a pound of marijuana can get you possession *and* intent to distribute, even if you were planning on having one hell of a couple of weeks by yourself. That's so drug dealers can't claim they are going to smoke it themselves, to get out of the intent charge. Same as the DUI/DWI laws, they have an established baseline that says no matter how well you do on field sobriety tests, if you blow a certain percent you get arrested. Long term alcoholics can function just fine at that level since their tolerance goes up, but they can still get arrested simply to make enforcement an objective measure.
You are the one who is shitting. I had to go find an example on google images.
Never in a million years would I have even thought to click on that thing. If I would have had the idea that it might be clickable, I would expect it to open a browser window to the Office home page or something equally useless. Apparently lots of people are shitting you.
Then take a picture of it, put it on a blog, post it to a high traffic site like slashdot, include digg and fark, and wait for a reply and post that too.
I can't believe sueing people like the RIAA does is a viable business model. The costs must outweigh the benefits by far. Even if the RIAA manages to win a case against a poor grandmother who has never heard of P2P and the like, she won't be able to pay the fine because the costs of defending herself have bankrupted her for good. I have a very hard time understanding the people who work for the RIAA and sue people for a living.
It's not a business model. The RIAA is simply an organization put together by the behemoths of the recording industry so they can legally collude without triggering antitrust laws. RIAA does not make money in the sense of selling a product or service. It is a service organization that provides certain actions on behalf of its member groups.
Think about it more like a Union. You pay dues and it gets things done, it's not a money maker by itself. And the fees the RIAA obtains for winning infringement cases or people settling, well that money just goes back into legal tactics and hiring Media Sentry - it doesn't flow back to the companies themselves, and certainly not to the artists they represent. The RIAA is looking out for their own copyright, since the artists typically sign over copyright to the company as a "work for hire" in exchange for whatever percent of album sales minus fees etc.
If you were talking about how the member companies make money ("The (members of the) RIAA"), they contribute fees to the RIAA hoping that RIAA lawsuits will have an effect on file sharing. Obviously this has not worked out well, and I would expect that the global economy slowdown is causing members to rethink what they are getting for their fees and reducing contributions to RIAA.
I found the source code to be repulsive. I could not possibly take over that code and make my own browser out of it, except for minor GUI changes maybe.
I was looking into a problem for ReactOS where the installer would explode, and just browsing the source made my head hurt. There were nearly-identical copies of files in a number of places - so that I couldn't determine which were the files included in the build - or maybe all were... and it wasn't just an old version, these files were out of sync with each other and being maintained separately.
There is no way I would let anyone but Mozilla Foundation play with that code.
I know you don't like the idea of vehicles because of all the global warming they emit, but you have to admit, if not for you I would not know how to recklessly waste gasoline without fear of tickets, because if not for you I would not have the previous poster's comment on the internet you invented. Funny, huh?
Forget time, it's money. I work at a Fortune ~120 company, and we never build anything for ourselves. Even in the name of cost-saving, no outlay happens unless we are confident it will be sold somehow. In a leveraged environment, the first client to need something pays for it, the others get it free (for one-time charges, space and bandwidth are ongoing though).
The client delivery arm of the co. is now requesting to use the web app we made for $car_company, even though they wouldn't fund or blaze the trail for its creation and delivery. Catch-122, it would not have existed if we had done it their way.
To prop up your argument, it's the companies' fault they are in this mess due to greed.
Ralph Brodd, a Nevada-based energy-storage consultant, recently published a report on battery manufacturing for the National Institute of Standards and Technology. He said that though much of the advanced battery technology was developed in the U.S., American companies "opted out" of battery production because of the low returns the business offered. Asian manufacturers picked up the business because of their proximity to makers of electronic devices, which need a steady supply of batteries.
This is the funny thing - it costs money to make something good, and they gave IE away. So I see all of these vulnerabilities in IE as being a direct result of MS trying to enforce their platform monopoly.
If they were still selling IE, we wouldn't have had a 6-year update drought, we would have better standards conformance, and I'm guessing that devs would have noticed some of these bugs a bit earlier with some dedicated QA and fuzzing. As it is, IE is just a loss leader.
Is any of this true? Probably not, but it's what flashes through my head.
I think it might be a little more subtle even than you say - it's that they are making money by being assholes certainly, but they make money by doing the barest minimum and calling it sufficient. And then they create mind-bogglingly complicated solutions to simple problems and wonder why no one bites. Both are forced onto the random consumer in ways that can only make you hate.
Regedit - functional, but no way to "GO TO" a key, despite all the MSDN docs that say go to a specific place and make a change. No, you have to click to expand each folder, then scroll down till you find the one you want. "Find" is kinda nice but it will take you to the wrong one quickly, and the right one slowly. Has no one ever thought this would be a good idea?
File search - find a few files, then do something with the list that takes more than a few seconds. If anything in the search path is modified, the search gets re-started and the list resets. So I have been 500 items into a 4000 item list, and the list resets and the "current selection" is now the first item again.
DirectX 10 - complicated, but used as a leverage to sell operating systems instead of supporting the ones they already sold.
Background apps allowed to give themselves focus, so that when you type you accidentally hit the space bar and unintentionally agree to something by clicking the default button.
The web browser that wouldn't update for 6 years
The AVI filters that think a file format is "unrecognized" just because the length doesn't match what is in the AVI header, so missing a single byte makes a movie unplayable while VLC has no problem with it.
Notification balloons that won't go away on their own.
Did you know that when you use Windows+R to run something, the Run dialog is started using "QueueUserWorkItem"? There is a thread queue and your request gets put into the queue. That's why you can hit Windows+R sometimes and the dialog takes forever to come up. I don't want to wait, I want to run something.
Pay attention next time you search or list something - Windows often finds the folders in reverse order. For example, copying a bunch of folders sometimes gets done in reverse. Or doing an IrfanView slideshow where there are sub directories - within the folder the slides are in order, but the folders are sometimes backwards. IrfanView could work around that, but the point is that behaviour is all over the place and every app has to work around it. Also when copying or moving, why do I get the message about existing file being overwritten if a folder name exists? Why can't it just ask me when it gets to that file? Oh right, poorly implemented code reuse that copies the whole folder, defaulting to overwriting files, when it does ask about individual files in the parent folder. No recursion implemented here?
I need to give an example of this one. When you start SQL Server Management Studio by connecting to a server, you can do a lot of things to that server with relative ease. But when you go under "Legacy" and try to import/export a DTS package, it sometimes says "SQL Server not found". What's the answer - something in the package? Or can it not find the server you are already connected to? No, it turns out Management Studio doesn't do the DTS transfer, it relies on some other tool to do it. So it takes its own connection info and hands it off to another tool, and that tool can't find the server. As far as I've found, there's no documentation on this, and the solution is to disconnect from the server, reconnect using a different alias, and it works now. Nowhere does it say you need to use a connection string that the DTS tool can figure out, and the error looks like it comes directly from the Management Studio app that is already connected. This kind of code/app reuse probably got someone a nice bonus, but I lost 2 weeks of functionality trying to figure out why I couldn't update my DTS package. I use secure WTS and shared hosting, so I can't just write a tool to move from one server
Yes, clearly draw the line about what is your responsibility and what is theirs. If something comes up and it's on your side of the line, say "I will take care of it" and they should never hear another word.
Also make sure they know everything, more than you think they need to know. It helps them auto-prioritize instead of making you micromanage.
"Where are you on this project" or "What did you do yesterday" are good ways to stay in touch, but even more so "What will you be working on tomorrow?" or "What's on your plate?" is more open-ended. Instead of checking up it feels more like planning, but you are still getting a feel for where they are. Subtle and tricksey, and might not work for everyone.
It's not in the editor, it's in a convertor. Kind of like a plugin. In order to make Word files the standard, MS included a utility so that if the user does not buy Word but does buy Windows, they can convert.doc files to text and read it that way. So the text editor loads a plugin to convert files.
At this point, someone has a malicious.doc file which (since it is a binary format and contains complicated structures) overwrites the stack and executescode, which is running in the text editor's address space.
If the.doc file weren't so complicated to read the converter would have had no problems and a simple "text editor" would not be the hottest exploit since Paris Hilton.
I won't search for a citation, but MS definition of "invent" is to create something new, while "innovate" is to use something in a new way. As an example, IE was innovation because it used web browsers in a new way (to crush opposing web browser companies and lock users and developers alike to the windows platform).
So buy GameStop, or make your own competitor, or invent a way for people to exchange used games with you or with each other. A 20% "Loyalty discount" for exchanging an old game for a new title would work, and then you get to resell the old one yourself.
Of course from your perspective, why would you want to get into the resale market - you don't need people to return the games to you to resell, you can make a billion copies if you want. So resell if you want, or just destroy it so no one else can buy it used.
Loyalty discounts, it's the only thing that makes sense. Stimulate new purchases by giving gamers back the money they would normally get by reselling the game. They are going to resell it - do you want it to be to GameStop or to you?
Oh, and send me part of your revenue stream. this is a killer idea.
I don't need a lot of power for my daily routine and neither do most people.
And you think 3 gHz isn't too much for that? By the time the tech is ready and stable (and after the first-adopters work out the kinks), we will need 6 gHz just to stream Heroes.
Slashdot Mirror
Your sarcasm is counterproductive. It's not supposed to be a police state. Hopefully this case will pull back the expanded powers a little, and everyone in this country at least should be on that side, because it would probably not be possible to "undo" these expanded powers without this case.
I remember using MFC, and finding very common problems had no MFC equivalent. I had to either call Win32 directly (which is fine for uncommon problems), or futz about updating poorly documented auto-generated code that I didn't understand well enough to be in there making changes. This is because MFC project team just couldn't predict what would be common, and it's the reason OP is having issues, and the reason I avoided toolkits until I couldn't any longer.*
It's very important to be able to tell a product what you want/need, and with open source you get the opportunity to be very clear, in the form of submitting patches.
*I usually drop a toolkit when I realize that a very common function requires several lines of code and an extra variable, such as "Does this directory name end in a terminator, or should I add one?" Especially if it's a platform-specific one that doesn't address the quirks of that platform.
Technology moves so quickly that for a lot of people 1 year or 3 years is more than enough time. If it breaks you get to upgrade. Also, it's hard to find a competing product with a longer warranty so the manufacturers don't/can't get the feedback.
I think people are more willing to spend money separately, and also looking for lower prices. So a $100 product looks more attractive when you take off $10 sold as the store's "replacement program" and make a $90 product with less warranty. Then the $90 product looks like a better deal without the in-store warranty alongside the "I'll upgrade when it breaks" idea.
"Amy" is a nice alternative in my neighborhood, and of course the street address itself is pretty helpful if you run out of ideas. Me, every time someone new moves in I switch mine to impersonate someone else's name or street number. Not sure what I think I'm accomplishing now that I think about it. But at least I'm not leaving it the default. (But always with a password set of course.)
Interesting. Disagree mail is from Nov. 2007.
The same thing was posted by "rob malda" <ma...@slashdot.org> 3 years before that.
alt.tv.public-access
http://groups.google.com/group/alt.tv.public-access/browse_thread/thread/3b52704212f7d6b/330487904ec7c865#330487904ec7c865
alt.tv.tech.misc
http://groups.google.com/group/alt.tv.tech.misc/browse_thread/thread/ec1caa9d23020f61/235f20df3c7ece53#235f20df3c7ece53
And that's the user's entire google groups profile. How is it this was posted twice, in its entirety, then 5 years later sent one by one back to the person who sent them (Rob)? "This guy would send us one of these at the end of the week for almost a year."
If you end up searching someone's stuff, and find a bunch of suspect photos, it's a lot easier to write a law that says it's illegal even if it's fake, than to have to go to court and prove that a real child was harmed.
I think that's the real reason behind this - to make enforcement of corner cases into actual clear-cut evidence. People get convicted on the basis of bad laws all the time.
for example, having a pound of marijuana can get you possession *and* intent to distribute, even if you were planning on having one hell of a couple of weeks by yourself. That's so drug dealers can't claim they are going to smoke it themselves, to get out of the intent charge. Same as the DUI/DWI laws, they have an established baseline that says no matter how well you do on field sobriety tests, if you blow a certain percent you get arrested. Long term alcoholics can function just fine at that level since their tolerance goes up, but they can still get arrested simply to make enforcement an objective measure.
You are the one who is shitting. I had to go find an example on google images.
Never in a million years would I have even thought to click on that thing. If I would have had the idea that it might be clickable, I would expect it to open a browser window to the Office home page or something equally useless. Apparently lots of people are shitting you.
http://mahoneylibrary.wordpress.com/2007/09/06/ms-office-2007-on-library-lab-computers/
http://mahoneylibrary.files.wordpress.com/2007/09/office07crop.thumbnail.png
Parroting your industry standard reply I see.
Blue flag hanging from the left side, yeah that's the Cryptol side.
Then take a picture of it, put it on a blog, post it to a high traffic site like slashdot, include digg and fark, and wait for a reply and post that too.
It's not a business model. The RIAA is simply an organization put together by the behemoths of the recording industry so they can legally collude without triggering antitrust laws. RIAA does not make money in the sense of selling a product or service. It is a service organization that provides certain actions on behalf of its member groups.
Think about it more like a Union. You pay dues and it gets things done, it's not a money maker by itself. And the fees the RIAA obtains for winning infringement cases or people settling, well that money just goes back into legal tactics and hiring Media Sentry - it doesn't flow back to the companies themselves, and certainly not to the artists they represent. The RIAA is looking out for their own copyright, since the artists typically sign over copyright to the company as a "work for hire" in exchange for whatever percent of album sales minus fees etc.
If you were talking about how the member companies make money ("The (members of the) RIAA"), they contribute fees to the RIAA hoping that RIAA lawsuits will have an effect on file sharing. Obviously this has not worked out well, and I would expect that the global economy slowdown is causing members to rethink what they are getting for their fees and reducing contributions to RIAA.
I found the source code to be repulsive. I could not possibly take over that code and make my own browser out of it, except for minor GUI changes maybe.
I was looking into a problem for ReactOS where the installer would explode, and just browsing the source made my head hurt. There were nearly-identical copies of files in a number of places - so that I couldn't determine which were the files included in the build - or maybe all were... and it wasn't just an old version, these files were out of sync with each other and being maintained separately.
There is no way I would let anyone but Mozilla Foundation play with that code.
Dear Al Gore:
I know you don't like the idea of vehicles because of all the global warming they emit, but you have to admit, if not for you I would not know how to recklessly waste gasoline without fear of tickets, because if not for you I would not have the previous poster's comment on the internet you invented. Funny, huh?
Signed,
The Internet
Forget time, it's money. I work at a Fortune ~120 company, and we never build anything for ourselves. Even in the name of cost-saving, no outlay happens unless we are confident it will be sold somehow. In a leveraged environment, the first client to need something pays for it, the others get it free (for one-time charges, space and bandwidth are ongoing though).
The client delivery arm of the co. is now requesting to use the web app we made for $car_company, even though they wouldn't fund or blaze the trail for its creation and delivery. Catch-122, it would not have existed if we had done it their way.
This is the funny thing - it costs money to make something good, and they gave IE away. So I see all of these vulnerabilities in IE as being a direct result of MS trying to enforce their platform monopoly.
If they were still selling IE, we wouldn't have had a 6-year update drought, we would have better standards conformance, and I'm guessing that devs would have noticed some of these bugs a bit earlier with some dedicated QA and fuzzing. As it is, IE is just a loss leader.
Is any of this true? Probably not, but it's what flashes through my head.
Leave my mom out of this! I pay my part!
I think it might be a little more subtle even than you say - it's that they are making money by being assholes certainly, but they make money by doing the barest minimum and calling it sufficient. And then they create mind-bogglingly complicated solutions to simple problems and wonder why no one bites. Both are forced onto the random consumer in ways that can only make you hate.
Regedit - functional, but no way to "GO TO" a key, despite all the MSDN docs that say go to a specific place and make a change. No, you have to click to expand each folder, then scroll down till you find the one you want. "Find" is kinda nice but it will take you to the wrong one quickly, and the right one slowly. Has no one ever thought this would be a good idea?
File search - find a few files, then do something with the list that takes more than a few seconds. If anything in the search path is modified, the search gets re-started and the list resets. So I have been 500 items into a 4000 item list, and the list resets and the "current selection" is now the first item again.
DirectX 10 - complicated, but used as a leverage to sell operating systems instead of supporting the ones they already sold.
Background apps allowed to give themselves focus, so that when you type you accidentally hit the space bar and unintentionally agree to something by clicking the default button.
The web browser that wouldn't update for 6 years
The AVI filters that think a file format is "unrecognized" just because the length doesn't match what is in the AVI header, so missing a single byte makes a movie unplayable while VLC has no problem with it.
Notification balloons that won't go away on their own.
Did you know that when you use Windows+R to run something, the Run dialog is started using "QueueUserWorkItem"? There is a thread queue and your request gets put into the queue. That's why you can hit Windows+R sometimes and the dialog takes forever to come up. I don't want to wait, I want to run something.
Pay attention next time you search or list something - Windows often finds the folders in reverse order. For example, copying a bunch of folders sometimes gets done in reverse. Or doing an IrfanView slideshow where there are sub directories - within the folder the slides are in order, but the folders are sometimes backwards. IrfanView could work around that, but the point is that behaviour is all over the place and every app has to work around it. Also when copying or moving, why do I get the message about existing file being overwritten if a folder name exists? Why can't it just ask me when it gets to that file? Oh right, poorly implemented code reuse that copies the whole folder, defaulting to overwriting files, when it does ask about individual files in the parent folder. No recursion implemented here?
I need to give an example of this one. When you start SQL Server Management Studio by connecting to a server, you can do a lot of things to that server with relative ease. But when you go under "Legacy" and try to import/export a DTS package, it sometimes says "SQL Server not found". What's the answer - something in the package? Or can it not find the server you are already connected to? No, it turns out Management Studio doesn't do the DTS transfer, it relies on some other tool to do it. So it takes its own connection info and hands it off to another tool, and that tool can't find the server. As far as I've found, there's no documentation on this, and the solution is to disconnect from the server, reconnect using a different alias, and it works now. Nowhere does it say you need to use a connection string that the DTS tool can figure out, and the error looks like it comes directly from the Management Studio app that is already connected. This kind of code/app reuse probably got someone a nice bonus, but I lost 2 weeks of functionality trying to figure out why I couldn't update my DTS package. I use secure WTS and shared hosting, so I can't just write a tool to move from one server
Yes, clearly draw the line about what is your responsibility and what is theirs. If something comes up and it's on your side of the line, say "I will take care of it" and they should never hear another word. Also make sure they know everything, more than you think they need to know. It helps them auto-prioritize instead of making you micromanage. "Where are you on this project" or "What did you do yesterday" are good ways to stay in touch, but even more so "What will you be working on tomorrow?" or "What's on your plate?" is more open-ended. Instead of checking up it feels more like planning, but you are still getting a feel for where they are. Subtle and tricksey, and might not work for everyone.
It would have to be aware that it's off, otherwise it would keep doing things like writing articles on the intartubes.
It's not in the editor, it's in a convertor. Kind of like a plugin. In order to make Word files the standard, MS included a utility so that if the user does not buy Word but does buy Windows, they can convert .doc files to text and read it that way. So the text editor loads a plugin to convert files.
At this point, someone has a malicious .doc file which (since it is a binary format and contains complicated structures) overwrites the stack and executescode, which is running in the text editor's address space.
If the .doc file weren't so complicated to read the converter would have had no problems and a simple "text editor" would not be the hottest exploit since Paris Hilton.
I won't search for a citation, but MS definition of "invent" is to create something new, while "innovate" is to use something in a new way. As an example, IE was innovation because it used web browsers in a new way (to crush opposing web browser companies and lock users and developers alike to the windows platform).
So buy GameStop, or make your own competitor, or invent a way for people to exchange used games with you or with each other. A 20% "Loyalty discount" for exchanging an old game for a new title would work, and then you get to resell the old one yourself.
Of course from your perspective, why would you want to get into the resale market - you don't need people to return the games to you to resell, you can make a billion copies if you want. So resell if you want, or just destroy it so no one else can buy it used.
Loyalty discounts, it's the only thing that makes sense. Stimulate new purchases by giving gamers back the money they would normally get by reselling the game. They are going to resell it - do you want it to be to GameStop or to you?
Oh, and send me part of your revenue stream. this is a killer idea.
Odd coincidence, my gf has a hoosier daddy. But only on the weekends.
And you think 3 gHz isn't too much for that? By the time the tech is ready and stable (and after the first-adopters work out the kinks), we will need 6 gHz just to stream Heroes.