Still, all it requires is for one recepient to open up a compose email dialog and hand copy the text and it's out. This just doesn't make sense from a content-management perspective.
Now, it does make sense if the intent is to lock out competing email clients. And as email is more and more a necessary business tool, this could be leveraged to force companies to use Outlook if they want to communicate with (the majority of large US) companies who use Outlook.
See, the wonderful thing about averages is that you can get a whole bunch of trivial sh*t that you classify as "bugs" that you patch in say.... 20 to 30 minutes... hell, you can even classify all changes you make as "bugfixes" and if they're released without a bug report, then you have a whole host of zero-time scores to pull your average 3-month gaping security hole cracker-to-fix time down to something that sounds reasonable.
I always associate spyware/RIAA lawsuits with Kazaa. I like LimeWire better - plus as a Java app, I think it's good to support cross-platform software.
Yea yea yea, and without government farm subsidies 30% of agriculture would evaporate overnight also. Without steel tarrifs 80% of steel would evaporate overnight... Let's not forget that copyright originated as a means of censorship (proud tradition that) and the real "rights" to creative works belong to the whole of humanity - we're only trading those rights temporarily to encourage and reward people for creating those works for us. But we seem to be giving up more and more without getting anything back in return.
Oh, and compulsary copyrights on everything creative sounds like a great idea. Lets just levy more taxes and use the revenue to support whatever art our federal government wants to support. Long live the NEA!!!
I'm not against copyrights, but I am against the perpetual extension of copyright terms. I'm also against labeling copyright infringement as theft - call it what it is - infringement. It's wrong, it's immoral, but the owner is not deprived of the work when it is illegally coppied.
The inconvenience of having to travel to a foreign country to buy it. Incompatible outlet plugs/incompatible power requirements (AC electricity in the US is generated at 60 Hz, while in many other parts of the world it may be generated at 50Hz, or possibly some other rate. Appliances designed for those countries will require a power supply compatible with what would be generated locally.)
Besides,if you wanted to truly be able to buy from any of the regions in the world you'd need to purchace 6 dvd players, because if you only bought the one player from the cheapest region, then you'd be locked out of movies that have not been released in that region AND some movies in that region may not be available in your native language. It's an easily defeatable system, but that's not the point. The point is to make it inconvenient for someone to defeat it. You as an individual are not a market. You as a large group are, and the large group is not going to each buy 6 dvd players.
It's called segmenting the market, and it's the reason airline tickets are less expensive 2 months in advance than they are 1 day in advance. Certain segments of the population are willing/able to pay more for the same good than other segments. If you can devise a way to sell the same thing to each segment for the maximum price that segment is willing to pay then you make more money than you would if you either: 1) sold for the high price and got fewer sales or 2) sold for the lower price and didn't make as much off of each sale. Airlines want to segment business travelers (who typically buy tickets only a day or 2 in advance) from vacationers (who buy tickets weeks in advance). The MPAA wants to split the market into USians who are willing/able to pay $20 to $50 a movie from other markets who may only be able to pay a little more than the cost of the media the movie is recorded on. Region encoding does this since a person is most likely to purchace his DVD player in the country in which he lives, thereby forcing him to also buy movies at the price set for his local country's economy.
I've heard the whole viruses are written by MS haters argument also, and what's always baffeled me is that it seems that most of them are written in VB which I cannot imagine any self-respecting MS hater even knowing.
I don't know about it replacing init (which I find to be quite easy to follow and understand) but he's got some good (or at least insightful) ideas to improve the "perceived" startup that perhaps could be incorporated into init.
I dunno about just getting a slap on the wrist for this one. It feels to me like there's not a lot of tolerence for stock shenanigans anymore. What with the head of the NYSE stepping down and mounting pressure to replace the entire board of directors. I think the financial market is tired of the BS.
Besides I don't think SCOX is quite as sophisticated in their stock scam as Enron was. I think it'll be easier to see, demonstrate and prosecute.
Hey, I did the same thing. Wish now that I'd been able to forsee the idiotic runaway price buildup so that I could've sold around $10 instead of $4. But hey, I didn't lose any money over it, which is better than I suspect most of the people buying at $17 will be able to say once the dust settles.
I heard on the radio this morning. Seems that some telemarketing firm in Baton Rouge was getting sprayed for cockroaches.... and about 60 of their employees got sick from the fumes and had to be evacuated.
Well, for what it's worth, it was my understanding that the original decision to use Banyan VINES (instead of Novell) was more politics than technology as well. But that may have just been rumors....
Does anyone remember Enable? I wonder whatever happed to what was the first integrated office suite I was exposed to. I remember being told to port compiled dBase applications to some kind of macro-language in Enable.
I went in as a 4063 back in 1990 and actually spent probably 3 or 4 months learning COBOL and Natural. That's helped me get serveral legacy-type jobs since then... Not too many people learn COBOL and JCL anymore - and learning to work in TSO or Roscoe is a bit different from coding on a pc (though I hear that there is a PC-based TSO available... dunno why anyone would want it though...)
At the time I went through it, I thought it was a fairly good introduction to programming course - something along the lines of taking the first freshman CSCI class where they teach you simple data structures, IO, etc... how to say hello world... and they expected you to get ojt for everything else. Of course I had to be retrained to work with dBase as soon as I got to my first duty station.
The biggest problem I saw during my time in was that the incentives for us to stay in were so poor that those who had talent and potential got the hell out to get a "real job" and those who couldn't make it on the outside stayed in and got promoted to the NCO and junior StaffNCO ranks (think: management. think: the Dilbert principal.) Of course there were some good NCOs who just loved being in the military and would put up with the bs. I noticed a lot of the upper enlisted ranks were populated by ex-infantry who never actually did the programming work their subordinates did, and I think they were a little less effective because of that.
I thought taking a couple weeks off once a year to go to the rifle range was great! (cleaning them afterwards really sucked.) I think more employers should have oraganized group activities with assault rifles, but my suggestions so far have fallen on deaf ears....
No worries over interview "stolen lines"
on
Back To SCO
·
· Score: 4, Insightful
At least McBride doesn't have to worry about interview infringement over "stealing lines" from the Bruce Perens interview. Taking them that far out of context oughta qualify them as being his own and not Perens's thoughts.
Is different systems requiring differing password change times (this prevents me from using the same password on all of them.) On one system it's every 45 days, on another it's every 30 days, and on yet another it's every 90 days...but I can't change it for at least 60 days - so there's no way to keep that password synced up with the rest of mine (the Vax and NT...well I just change the Vax early)
Now the 60 day minimum is designed to keep people from changing their password and immediately changing it back - but do they really need to set that at 60 f---ing days? Gah!
It also sounded like the MS Windows EULA wasn't displayed either. Not that I'd want to run MS Windows anyway, but that may be a way to use it without agreeing to any MS liscence...
Slashdot Mirror
Still, all it requires is for one recepient to open up a compose email dialog and hand copy the text and it's out. This just doesn't make sense from a content-management perspective.
Now, it does make sense if the intent is to lock out competing email clients. And as email is more and more a necessary business tool, this could be leveraged to force companies to use Outlook if they want to communicate with (the majority of large US) companies who use Outlook.
'Cuz that might lead to dancing...
See, the wonderful thing about averages is that you can get a whole bunch of trivial sh*t that you classify as "bugs" that you patch in say .... 20 to 30 minutes... hell, you can even classify all changes you make as "bugfixes" and if they're released without a bug report, then you have a whole host of zero-time scores to pull your average 3-month gaping security hole cracker-to-fix time down to something that sounds reasonable.
but what I want is a way to apt-get clippy the office assistant.
I always associate spyware/RIAA lawsuits with Kazaa. I like LimeWire better - plus as a Java app, I think it's good to support cross-platform software.
Yea yea yea, and without government farm subsidies 30% of agriculture would evaporate overnight also. Without steel tarrifs 80% of steel would evaporate overnight... Let's not forget that copyright originated as a means of censorship (proud tradition that) and the real "rights" to creative works belong to the whole of humanity - we're only trading those rights temporarily to encourage and reward people for creating those works for us. But we seem to be giving up more and more without getting anything back in return.
Oh, and compulsary copyrights on everything creative sounds like a great idea. Lets just levy more taxes and use the revenue to support whatever art our federal government wants to support. Long live the NEA!!!
I'm not against copyrights, but I am against the perpetual extension of copyright terms. I'm also against labeling copyright infringement as theft - call it what it is - infringement. It's wrong, it's immoral, but the owner is not deprived of the work when it is illegally coppied.
The inconvenience of having to travel to a foreign country to buy it. Incompatible outlet plugs/incompatible power requirements (AC electricity in the US is generated at 60 Hz, while in many other parts of the world it may be generated at 50Hz, or possibly some other rate. Appliances designed for those countries will require a power supply compatible with what would be generated locally.)
Besides,if you wanted to truly be able to buy from any of the regions in the world you'd need to purchace 6 dvd players, because if you only bought the one player from the cheapest region, then you'd be locked out of movies that have not been released in that region AND some movies in that region may not be available in your native language. It's an easily defeatable system, but that's not the point. The point is to make it inconvenient for someone to defeat it. You as an individual are not a market. You as a large group are, and the large group is not going to each buy 6 dvd players.
It's called segmenting the market, and it's the reason airline tickets are less expensive 2 months in advance than they are 1 day in advance. Certain segments of the population are willing/able to pay more for the same good than other segments. If you can devise a way to sell the same thing to each segment for the maximum price that segment is willing to pay then you make more money than you would if you either: 1) sold for the high price and got fewer sales or 2) sold for the lower price and didn't make as much off of each sale. Airlines want to segment business travelers (who typically buy tickets only a day or 2 in advance) from vacationers (who buy tickets weeks in advance). The MPAA wants to split the market into USians who are willing/able to pay $20 to $50 a movie from other markets who may only be able to pay a little more than the cost of the media the movie is recorded on. Region encoding does this since a person is most likely to purchace his DVD player in the country in which he lives, thereby forcing him to also buy movies at the price set for his local country's economy.
I've heard the whole viruses are written by MS haters argument also, and what's always baffeled me is that it seems that most of them are written in VB which I cannot imagine any self-respecting MS hater even knowing.
I don't know about it replacing init (which I find to be quite easy to follow and understand) but he's got some good (or at least insightful) ideas to improve the "perceived" startup that perhaps could be incorporated into init.
You see, the fact that IBM is willing to countersue SCO indicates how seriously they take SCO's claim on Linux....
I'm just waiting for it
I dunno about just getting a slap on the wrist for this one. It feels to me like there's not a lot of tolerence for stock shenanigans anymore. What with the head of the NYSE stepping down and mounting pressure to replace the entire board of directors. I think the financial market is tired of the BS.
Besides I don't think SCOX is quite as sophisticated in their stock scam as Enron was. I think it'll be easier to see, demonstrate and prosecute.
Heck, I can hope for it anyway.
Hey, I did the same thing. Wish now that I'd been able to forsee the idiotic runaway price buildup so that I could've sold around $10 instead of $4. But hey, I didn't lose any money over it, which is better than I suspect most of the people buying at $17 will be able to say once the dust settles.
maybe it's just matrices all the way down...
I heard on the radio this morning. Seems that some telemarketing firm in Baton Rouge was getting sprayed for cockroaches.... and about 60 of their employees got sick from the fumes and had to be evacuated.
Coincidence?
Well, for what it's worth, it was my understanding that the original decision to use Banyan VINES (instead of Novell) was more politics than technology as well. But that may have just been rumors....
Does anyone remember Enable? I wonder whatever happed to what was the first integrated office suite I was exposed to. I remember being told to port compiled dBase applications to some kind of macro-language in Enable.
I went in as a 4063 back in 1990 and actually spent probably 3 or 4 months learning COBOL and Natural. That's helped me get serveral legacy-type jobs since then... Not too many people learn COBOL and JCL anymore - and learning to work in TSO or Roscoe is a bit different from coding on a pc (though I hear that there is a PC-based TSO available... dunno why anyone would want it though...)
At the time I went through it, I thought it was a fairly good introduction to programming course - something along the lines of taking the first freshman CSCI class where they teach you simple data structures, IO, etc... how to say hello world... and they expected you to get ojt for everything else. Of course I had to be retrained to work with dBase as soon as I got to my first duty station.
The biggest problem I saw during my time in was that the incentives for us to stay in were so poor that those who had talent and potential got the hell out to get a "real job" and those who couldn't make it on the outside stayed in and got promoted to the NCO and junior StaffNCO ranks (think: management. think: the Dilbert principal.) Of course there were some good NCOs who just loved being in the military and would put up with the bs. I noticed a lot of the upper enlisted ranks were populated by ex-infantry who never actually did the programming work their subordinates did, and I think they were a little less effective because of that.
I thought taking a couple weeks off once a year to go to the rifle range was great! (cleaning them afterwards really sucked.) I think more employers should have oraganized group activities with assault rifles, but my suggestions so far have fallen on deaf ears....
At least McBride doesn't have to worry about interview infringement over "stealing lines" from the Bruce Perens interview. Taking them that far out of context oughta qualify them as being his own and not Perens's thoughts.
Is different systems requiring differing password change times (this prevents me from using the same password on all of them.) On one system it's every 45 days, on another it's every 30 days, and on yet another it's every 90 days...but I can't change it for at least 60 days - so there's no way to keep that password synced up with the rest of mine (the Vax and NT...well I just change the Vax early)
Now the 60 day minimum is designed to keep people from changing their password and immediately changing it back - but do they really need to set that at 60 f---ing days? Gah!
Yea, but I don't hear them offering that protection for their MS Windows offerings either?
it's that new math
It also sounded like the MS Windows EULA wasn't displayed either. Not that I'd want to run MS Windows anyway, but that may be a way to use it without agreeing to any MS liscence...
I saw Sarah Good writing the virus! I saw Goody Osborne writing the virus!
It was Indiana in 1897, and it passed the House there only to be killed by the Senate.
Sigh, it woulda make trig oh-so-much-easier...
since they don't do anything resembling "the practice of engineering" (or the practice of programming for that matter)