You say 'It's not worth my time or effort to figure it out.'
So you have a relatively standard piece of well supported hardware that you're getting less then optimal use from and you post a long whining rant about the lack of support you're getting. Then when someone points these facts out you say that 'It's not worth my time or effort to figure it out.'
Either you're new to trolling or you're one of those idiots that make people quit tech support positions...
I won't tell you that everyone has a 1GIG machine now, but I will say that in less than 3 years most fortune 1000 businesses will have >1Gig machines.
Nope, they won't. The Fortune 1000 probably trail other businesses in upgrading their machines (due to depreciation, other uses for the $, etc).
I work for one of them and basically the speed of your machine is related to when you started - the longer you've been here the slower your machine is. Simply, a new employee gets a new machine (the latest and greatest) - but that machine doesn't get replaced ever unless it either breaks or there's a legitimate business need (or you're a manager...). Just replacing machines 'because it's old/slow' isn't a business need.
Case in point - I started almost 3 years ago and have a 700Mh Pentium III. One of my co-workers started 4 years ago and has 233Mh Pentium II. Companies don't just run around upgrading people's machines willy-nilly.
WTF? All you have to do is install the MS Project viewer which is freely distributable.
That'd be a good idea if Microsoft made a viewer for Project... Go to the download page for Microsoft Project and try to find any viewers - none exist (although they do have them for other products in the 'office' family).
I think I was one of the few people to ever try doing software development on AIX/i386 (it was back when an IBM Model 70 was hot stuff).
The only reason we did it was because the IT managers of one of our biggest clients was willing to pay $$$ for us to port from SCO Unix to AIX/i386. This guy was the poster child for 'no body ever got fired for buying IBM' (hell, he even bought a Model 50 for home because 'by the end of the year, everyone will be making MicroChannel machines').
The only good thing about doing the port was that the contract kept the company alive through a lean period.
Re:"MFC programming", what the heck?
on
Qt vs MFC
·
· Score: 2
Actually, a lot of the mess in MFC is not due to the changing Win32 API, but left over from the switch from 16-bit Windows (i.e. 3.11) to 32-bit Windows (95/NT & later).
It's this backwards compatablity that hampered MFC through too many years. Unfortunately, the only way to get rid of it now would be to start over (which will never happen now that.net is MS's future).
"He also defends UnitedLinux against Mandrake's criticism. He would, since he works for Conectiva..."
Yes, I know it from the submitter (not an editor), but it's still a dumb comment.
Just because you're an employee doesn't mean that you can't have opinions and express them. If anything, I'd think an employee of a company dealing with Open Source software would be more likely to express dissatisfaction when warranted. I suppose PDAJames (the submitter) only says nice things about the company he works for?
First, the Army way doesn't scale well to 400 people with many shifts, so I doubt if it'll work for this problem.
The reference on how to do Army duty rosters properly (i.e. without screwing people or pissing them off) is to follow the directions in AR 220-45
and to fill out DA Form 6.
As another former S1 (and later G1), this was the only way to do it. I saw command investigations where people were repremanded for not following the regs properly (or at all). In this case, the regulation does set out a fair way to rotate duty in a group.
I'm actually using this for scheduling Level 3 support in my development group and there've benn no complaints...
From this 'article' it seems that Michael is stepping into Katz shoes. The only difference is that Michael seems to have a bit more of an 'edginess' about him (Katz seems more laid-back).
Add this to his add-on editorial for Warcraft III - is he trying to get a payraise for upping the number of hits to/.?
Ebone carries about 25%, the rest of KPNQwest carries another 25% - the total company carries about 50%. Ebone was never really integrated into the rest of the KPNQwest network (hadn't had time before the company went splat).
The 'Barbie' camera is a total POS - I wish it did 320x240!
I looked at getting one for my 8yo daughter to play with (rather then using my digital camera) and, although cheap, wasn't worth anywhere near what they wanted for it. It also has a totally closed interface with really sucky software that you have to use to retrieve the photos!
I passed it up but, unfortunately, my in-laws didn't... It's worse then I'd thought (it only stores 6(?) of the really tiny photos onboard). I'll probably end up getting a cheap (but ok quality) camera for her.
Equipment costs, employees, I realize, all take part of that pie, but WTF is all this money going?
Well, besides bandwidth, I assume it's going to equipment costs, employees and taxes/fees.
By just dismissing them out of hand, you've just shown that you don't really understand the costs involved.
Despite staunch opposition from certain developers
Since this reference the email to the kernel dev list from The Open Source Club at The Ohio State University (who don't seem to have done much kernel development) I assue that when you say 'certain developers' you mean 'people who may have looked at the source but who don't really contribute to it.'
Nope, as others have said previously, SCO Unix was based on the AT&T source (which is why they could brand it as Unix reather then Xenix). It was a different source base and development continued on the Xenix line in parallel for a while afterwards.
Not just Pizza Hut, I worked on the project at McDonalds to convert the in-store system from SCO Xenix 286 (yep, 286) to SCO Unix. It was running in all company owned stores and quite a few of the franchise stores.
McDonalds was using Xenix 286 (on AT&T 386 WGS boxes) because of a bug in the original 386 math co-processor (remember those things?). Xenix 386 would crash with the faulty co-processor installed. Rather then try to remove ~1200 co-processors (already in stores) it was decided that it was cheaper/easier to just use the 286 version (SCO came out with a fix/workaround after the 286 version was already distributed)...
How about relinking the kernel (and rebooting) everytime you make a minor system configuration change. Perhaps Linux's loadable modules, and dynamic detection of devices has spoiled me
Welcome to the real Unix world. This was SOP for Unix systems - loadable modules are a recent development on the Unix timeline.
Since radio stations pay a fee to the music publishers (and, therefore, to the artists) for the music they play, Musicnet is closer to the way radio works then Napster.
OTOH, if it is something that you need to distribute, say... to your customers for their use, I would agree with the previous poster who wrote that contributing your patches back to the project might be necessary to prevent a lawsuit.
Nope, you only need to provide the patches to the customers you distributed the software to. Since you have to be able to give them the source anyways (because of the GPL), this shouldn't be much of a burden.
With the GPL, you don't have to give the source to anyone you didn't give the binary to. It seems that most people read things into the GPL that aren't really there...
Slashdot Mirror
Simple, they (the Japanese) canceled Iron Chef quite a while ago. Can't be on it if they aren't making any more.
Also, they never did have very many non-Japanese chefs (which makes sense since it was a Japanese show).
So you have a relatively standard piece of well supported hardware that you're getting less then optimal use from and you post a long whining rant about the lack of support you're getting. Then when someone points these facts out you say that 'It's not worth my time or effort to figure it out.'
Either you're new to trolling or you're one of those idiots that make people quit tech support positions...
Nope, they won't. The Fortune 1000 probably trail other businesses in upgrading their machines (due to depreciation, other uses for the $, etc).
I work for one of them and basically the speed of your machine is related to when you started - the longer you've been here the slower your machine is. Simply, a new employee gets a new machine (the latest and greatest) - but that machine doesn't get replaced ever unless it either breaks or there's a legitimate business need (or you're a manager...). Just replacing machines 'because it's old/slow' isn't a business need.
Case in point - I started almost 3 years ago and have a 700Mh Pentium III. One of my co-workers started 4 years ago and has 233Mh Pentium II. Companies don't just run around upgrading people's machines willy-nilly.
That'd be a good idea if Microsoft made a viewer for Project... Go to the download page for Microsoft Project and try to find any viewers - none exist (although they do have them for other products in the 'office' family).
I think I was one of the few people to ever try doing software development on AIX/i386 (it was back when an IBM Model 70 was hot stuff).
The only reason we did it was because the IT managers of one of our biggest clients was willing to pay $$$ for us to port from SCO Unix to AIX/i386. This guy was the poster child for 'no body ever got fired for buying IBM' (hell, he even bought a Model 50 for home because 'by the end of the year, everyone will be making MicroChannel machines').
The only good thing about doing the port was that the contract kept the company alive through a lean period.
Actually, a lot of the mess in MFC is not due to the changing Win32 API, but left over from the switch from 16-bit Windows (i.e. 3.11) to 32-bit Windows (95/NT & later).
.net is MS's future).
It's this backwards compatablity that hampered MFC through too many years. Unfortunately, the only way to get rid of it now would be to start over (which will never happen now that
Yes, I know it from the submitter (not an editor), but it's still a dumb comment.
Just because you're an employee doesn't mean that you can't have opinions and express them. If anything, I'd think an employee of a company dealing with Open Source software would be more likely to express dissatisfaction when warranted. I suppose PDAJames (the submitter) only says nice things about the company he works for?
The reference on how to do Army duty rosters properly (i.e. without screwing people or pissing them off) is to follow the directions in AR 220-45 and to fill out DA Form 6.
As another former S1 (and later G1), this was the only way to do it. I saw command investigations where people were repremanded for not following the regs properly (or at all). In this case, the regulation does set out a fair way to rotate duty in a group.
I'm actually using this for scheduling Level 3 support in my development group and there've benn no complaints...
(The browser war) isn't over until we say it's over!
From this 'article' it seems that Michael is stepping into Katz shoes. The only difference is that Michael seems to have a bit more of an 'edginess' about him (Katz seems more laid-back).
/.?
Add this to his add-on editorial for Warcraft III - is he trying to get a payraise for upping the number of hits to
Ebone carries about 25%, the rest of KPNQwest carries another 25% - the total company carries about 50%. Ebone was never really integrated into the rest of the KPNQwest network (hadn't had time before the company went splat).
But 3 would work for me...
The 'Barbie' camera is a total POS - I wish it did 320x240!
I looked at getting one for my 8yo daughter to play with (rather then using my digital camera) and, although cheap, wasn't worth anywhere near what they wanted for it. It also has a totally closed interface with really sucky software that you have to use to retrieve the photos!
I passed it up but, unfortunately, my in-laws didn't... It's worse then I'd thought (it only stores 6(?) of the really tiny photos onboard). I'll probably end up getting a cheap (but ok quality) camera for her.
Well, 2 cute 22 year old girls would be better (although probably lethal in my case).
By just dismissing them out of hand, you've just shown that you don't really understand the costs involved.
Nope, as others have said previously, SCO Unix was based on the AT&T source (which is why they could brand it as Unix reather then Xenix). It was a different source base and development continued on the Xenix line in parallel for a while afterwards.
McDonalds was using Xenix 286 (on AT&T 386 WGS boxes) because of a bug in the original 386 math co-processor (remember those things?). Xenix 386 would crash with the faulty co-processor installed. Rather then try to remove ~1200 co-processors (already in stores) it was decided that it was cheaper/easier to just use the 286 version (SCO came out with a fix/workaround after the 286 version was already distributed)...
What they are doing is licensing the software they wrote under a per-seat license.
You can redistribute/use all of the GPL'd software in United Linux use want without paying a per-seat license, just not the 'propritary' pieces.
Welcome to the real Unix world. This was SOP for Unix systems - loadable modules are a recent development on the Unix timeline.
With the GPL, you don't have to give the source to anyone you didn't give the binary to. It seems that most people read things into the GPL that aren't really there...