Even if you trust one vendor and they defy that trust, you can always switch to another one and most likely be able to run all your old programs. It doesn't pay for distros to cheat their users. The users will just move to another.
That's the difference between a rogue developer slipping in code and an evil corporation hiding code.
Actually, I would much rather prefer a car that could go over 70-80. Not because I want to do it on a regular basis, but because I had a car that would do 80 on a good day, down hill and with the wind at my back. But it would do 85(!) and that was about it. It took me miles to get to that speed and wasn't very economic at that speed. Good old Mercury Lynx. Anyway, to my point. A car designed to go 80 will start to lose some of it's torque near the high end of the speed band and to start to lose that ability to avoid a crash, pass a car, or anything useful over 55mph if you might actually need it.
Around 150 mph seems to be a common cutoff in the last two cars I've owned (both Mazda) and they've had plenty of power to do what I needed and when I needed it at highway speeds and below. My RX8 was capped at 150 by the transmission gearing/red-line and my MX5 seems to be the same (though I haven't had a chance to get it to the track to see.)
My first guess is that he may work for an accounting and or payroll function and he might not be suited for a training department or operations programming. (or vice versa)
Were I work there are several different departments all with different programming needs. It helps to know some intimate details about accounting in order to give them the right tools to do their jobs. It would also be a pretty steep learning curve for that same developer to put their accounting knowledge on the bench while being tasked to write a program for the operation of the company. Without knowledge of the processes that go on in the operation, they will likely create software that's useful, but not very elegant or meaningful for the front line supervisor that needs to update numbers.
Where I work, they have a dedicated development staff, and the projects they roll out are very well planned, organized, and managed. Unfortunately though, there are some things the operation needs and wants in short order that would help them perform better and they can't wait for a full 2 year project plan and all that. That's where the fun happens. It used to be tasked to some poor supervisor or someone that might be a hobbyist programmer in an area to create something in Access to get them their numbers or perform the task of training someone... yes, they would train people with Access because that's all they had to work with.
Recently though, there has been an upstart of a group that handles "mid-level" operational reporting tools and rapid development tasks in order to take on these one man projects and try to standardize them across the company instead of having 80 odd programs in different states and countries doing the same things (frankly wasting time solving the same problems all areas face.)
Is it the best solution? Probably not. But it's been working. The "start up sub group" has been able to quickly roll out applications (web apps in this case) to the field so they can perform their job easier and more efficient. If they run across something that requires more development, it's pushed up the chain to the dedicated development/systems teams to do a corporate assessment. There's something to be said for project planning and all that, but sometimes it's ungainly slow and cumbersome. In this small group, the developer is usually tasked with talking to the requester, laying out the design and functionality of the application with the user and coding it up on the framework in place. Granted, it's a lot of work on the developer, but they gain a knowledge of what the field needs and can better layout what that niche of the company needs to do it's job in a rather short period of time where the common standard project time line for the dedicated team of developers would take way too long to gather that knowledge, lay out a plan, and code the application.
(I know I probably shouldn't say this... but I can't stop typing!)
You see, this is why ____ will never make it. If I have to keep using these obscure command line fixes in order to make my system work the way I want, regular people will never use it.
Also, in curving the pipe it helps reduce the old noises traditional piping had where water would travel down a long straight run and immediately slam into a bend causing "clunk" noises and hissing.
My argument is in an above thread on this issue. It shouldn't matter what the cost of living is in an area. Products should NOT be priced differently in different countries forcing one country to foot the bill for Microsoft's world domination. Why should the US/Europe/Japan have to pay more for something so they can sell their software for a really cheap price in China/Africa to undercut competition in those countries?
That to me is anti-trust to a "T." In no way whatsoever would another company get away with this.
You see, that's where I get really foggy on this whole MS anti-trust issue. I'm pretty sure it's considered "unfair practice" to sell your product to one area (State?) for less or more than another at base cost. (making one market pay more to cover the cost of underselling your product in another market... ahem $3 per license Windows in Africa(?)) Shipping and taxes would influence the end price. This is what confuses me about how Microsoft does business and how it's still considered legal. The cost of Windows should only be influenced by taxes since digital transfers really cost nothing. (I guess you could add in the shipping cost of CDs though...)
Isn't it global anti-trust to sell a product for less in one country than you do another? Is there such a thing? Who would bring down the hammer on such things?
Especially since "pimping" is mainly about being seen by those you're targeting.;)
I wanted to see before and after shots AT LEAST! I read the summary and was thinking. I was wondering what a 50s era data center looked like... and what did they convert the unused space into?
The PM that works on all distros will win. That's competition. Take the load off the developer in figuring out what distro they are on and let the installer put files where they need. It could also set flags for the program being installed to locate appropriate locations to save and load information from.
No no... the way I interpreted it and was told... you're invisible friend will do whatever they feel like. This is because they think it's better for you than your wish and it will happen in "mysterious ways" that you cannot predict. (AKA: Something good will eventually happen if you do this, the odds are good my friend.)
One odd case in many. How many people go to the store and look at the back of the box for pictures of the game. How many game sites have screenshots... Graphics sell.
One of the more creative ideas I've heard, but how do you avoid people following HOWTOs on building a character the way they are best needed? For instance. If you somehow had to complete objectives in order to achieve a certain skill or trait, those objectives would be recorded and repeated by thousands of people the next day in their ultimate race to the max level. If you make it random, or difficult to figure out, people will cry that they missed the opportunity to get their character the cake baking skill and cry that they are gimped/nerfed/etc.
I know you were being funny, but the only thing they offer that's even remotely unique is the combat and it's not even that unique. I think DDO did combat a little better than the typical click to auto-attack and spam spells/skills.
It's your typical quest grind to max level where you are forced to participate in PVP or raids to pass time. Damn, I'm so sick of MMOs.
Not to mention you could use buttons as shifters. Hit the left shoulder pad and it changes your active spell slots to an alternate. Now you have 8 possible spells you can cast in a split second (on an standard PS/XB controller.) Use both shoulders on both sides and you have the possibility of 16. Use them in combination (topleft + topright + x) and you come up with 40 buttons and I haven't even touched the direction pads.
I can't tell you how many SUVs I've seen flipped over on 350(315? I can't remember) North from Addison to Schaumburg when I lived in the area... It was an epidemic!
Slashdot Mirror
From what I hear, free healthcare in Canada isn't all it's cracked up to be.
Even if you trust one vendor and they defy that trust, you can always switch to another one and most likely be able to run all your old programs. It doesn't pay for distros to cheat their users. The users will just move to another.
That's the difference between a rogue developer slipping in code and an evil corporation hiding code.
It's probably more entertaining, and productive as well.
At least I still have the Easter Bunny.
I think I'm more scared by "The Press' Poster Boy" voting Yea.
You gotta pay for Windows somehow!
Actually, I would much rather prefer a car that could go over 70-80. Not because I want to do it on a regular basis, but because I had a car that would do 80 on a good day, down hill and with the wind at my back. But it would do 85(!) and that was about it. It took me miles to get to that speed and wasn't very economic at that speed. Good old Mercury Lynx. Anyway, to my point. A car designed to go 80 will start to lose some of it's torque near the high end of the speed band and to start to lose that ability to avoid a crash, pass a car, or anything useful over 55mph if you might actually need it.
Around 150 mph seems to be a common cutoff in the last two cars I've owned (both Mazda) and they've had plenty of power to do what I needed and when I needed it at highway speeds and below. My RX8 was capped at 150 by the transmission gearing/red-line and my MX5 seems to be the same (though I haven't had a chance to get it to the track to see.)
My first guess is that he may work for an accounting and or payroll function and he might not be suited for a training department or operations programming. (or vice versa)
Were I work there are several different departments all with different programming needs. It helps to know some intimate details about accounting in order to give them the right tools to do their jobs. It would also be a pretty steep learning curve for that same developer to put their accounting knowledge on the bench while being tasked to write a program for the operation of the company. Without knowledge of the processes that go on in the operation, they will likely create software that's useful, but not very elegant or meaningful for the front line supervisor that needs to update numbers.
Where I work, they have a dedicated development staff, and the projects they roll out are very well planned, organized, and managed. Unfortunately though, there are some things the operation needs and wants in short order that would help them perform better and they can't wait for a full 2 year project plan and all that. That's where the fun happens. It used to be tasked to some poor supervisor or someone that might be a hobbyist programmer in an area to create something in Access to get them their numbers or perform the task of training someone... yes, they would train people with Access because that's all they had to work with.
Recently though, there has been an upstart of a group that handles "mid-level" operational reporting tools and rapid development tasks in order to take on these one man projects and try to standardize them across the company instead of having 80 odd programs in different states and countries doing the same things (frankly wasting time solving the same problems all areas face.)
Is it the best solution? Probably not. But it's been working. The "start up sub group" has been able to quickly roll out applications (web apps in this case) to the field so they can perform their job easier and more efficient. If they run across something that requires more development, it's pushed up the chain to the dedicated development/systems teams to do a corporate assessment. There's something to be said for project planning and all that, but sometimes it's ungainly slow and cumbersome. In this small group, the developer is usually tasked with talking to the requester, laying out the design and functionality of the application with the user and coding it up on the framework in place. Granted, it's a lot of work on the developer, but they gain a knowledge of what the field needs and can better layout what that niche of the company needs to do it's job in a rather short period of time where the common standard project time line for the dedicated team of developers would take way too long to gather that knowledge, lay out a plan, and code the application.
(I know I probably shouldn't say this... but I can't stop typing!)
You see, this is why ____ will never make it. If I have to keep using these obscure command line fixes in order to make my system work the way I want, regular people will never use it.
Also, in curving the pipe it helps reduce the old noises traditional piping had where water would travel down a long straight run and immediately slam into a bend causing "clunk" noises and hissing.
My argument is in an above thread on this issue. It shouldn't matter what the cost of living is in an area. Products should NOT be priced differently in different countries forcing one country to foot the bill for Microsoft's world domination. Why should the US/Europe/Japan have to pay more for something so they can sell their software for a really cheap price in China/Africa to undercut competition in those countries?
That to me is anti-trust to a "T." In no way whatsoever would another company get away with this.
You see, that's where I get really foggy on this whole MS anti-trust issue. I'm pretty sure it's considered "unfair practice" to sell your product to one area (State?) for less or more than another at base cost. (making one market pay more to cover the cost of underselling your product in another market ... ahem $3 per license Windows in Africa(?)) Shipping and taxes would influence the end price. This is what confuses me about how Microsoft does business and how it's still considered legal. The cost of Windows should only be influenced by taxes since digital transfers really cost nothing. (I guess you could add in the shipping cost of CDs though...)
Isn't it global anti-trust to sell a product for less in one country than you do another? Is there such a thing? Who would bring down the hammer on such things?
You forgot about the 106" Plasmas on the ceiling that play Xzibit videos on loop.
Especially since "pimping" is mainly about being seen by those you're targeting. ;)
I wanted to see before and after shots AT LEAST! I read the summary and was thinking. I was wondering what a 50s era data center looked like... and what did they convert the unused space into?
How is writing an alternative to X not "UNIX(ish)"?
At least wait for Wine 1.0 SP1. That's the norm, right?
The PM that works on all distros will win. That's competition. Take the load off the developer in figuring out what distro they are on and let the installer put files where they need. It could also set flags for the program being installed to locate appropriate locations to save and load information from.
At least, that's what I'm rooting for.
No no... the way I interpreted it and was told... you're invisible friend will do whatever they feel like. This is because they think it's better for you than your wish and it will happen in "mysterious ways" that you cannot predict. (AKA: Something good will eventually happen if you do this, the odds are good my friend.)
One odd case in many. How many people go to the store and look at the back of the box for pictures of the game. How many game sites have screenshots... Graphics sell.
One of the more creative ideas I've heard, but how do you avoid people following HOWTOs on building a character the way they are best needed? For instance. If you somehow had to complete objectives in order to achieve a certain skill or trait, those objectives would be recorded and repeated by thousands of people the next day in their ultimate race to the max level. If you make it random, or difficult to figure out, people will cry that they missed the opportunity to get their character the cake baking skill and cry that they are gimped/nerfed/etc.
That's the most realistic solution I've found. The other is not making it a race to max level before the game begins.
He did warn you... and thought it bears striking resemblance to every description I've heard, I don't think that's Mr. Christ.
I know you were being funny, but the only thing they offer that's even remotely unique is the combat and it's not even that unique. I think DDO did combat a little better than the typical click to auto-attack and spam spells/skills.
It's your typical quest grind to max level where you are forced to participate in PVP or raids to pass time. Damn, I'm so sick of MMOs.
Not to mention you could use buttons as shifters. Hit the left shoulder pad and it changes your active spell slots to an alternate. Now you have 8 possible spells you can cast in a split second (on an standard PS/XB controller.) Use both shoulders on both sides and you have the possibility of 16. Use them in combination (topleft + topright + x) and you come up with 40 buttons and I haven't even touched the direction pads.
I can't tell you how many SUVs I've seen flipped over on 350(315? I can't remember) North from Addison to Schaumburg when I lived in the area... It was an epidemic!