Simple - by promising this they: 1.) Stop OpenOffice migrations (why migrate when we can just wait for MS to come out with their solution and we'll just buy that) 2.) Get people to upgrade to the next Office.
#1 is typical of MS - promise something, people wait, your competition can't survive when their business dries up, then you kill the project. Problem is, this isn't a pay-for product, so it's not going to go away.
#2 is the real thing - people will buy the next version of office, which is a huge problem for them.
Of course, I wouldn't be surprised if this ends up being a bait and switch...
Nope, I have, except that logic dictates that code that constantly executes under a VM will be slower than code that is JIT compiled and then runs as native code. Of course, this implies that programming skills are equal and all that.
Plus (and perhaps more importantly), all the Java gui toolkits I've seen (well, except the ones running under OSX) look like ass and customers hate them.
C++ provides a good transition to C#. MFC is a leaky, unstable piece of shit. Either use the old Win32 API (more difficult to program for, but leaks memory less and crashes less). I've been using C# under both.NET and Mono (using the GTK# widget set for GUI bits) and have been quite happy with it..NET/Mono has some really nice things that make it way better than C++. (Full disclosure - I've never used Objective-C or Java, so I have no opinion on those).
I work for a consulting company. We go where the money is. Clients want something on Windows, we write for Windows. Clients want something on Linux, we write for Linux. Client want something on Solaris, we write for Solaris..NET/Mono is kind of nice because it allows anything to run anywhere (at least, in theory. Practice has some holes in it, but it will get better).
Just like there's no "security" tab to set file permissions in XP Home. At least, I couldn't find one on Home in the same place it was in Pro. Of course, a SP might have fixed it.
Worms 2 is a great game.
The other thing you could do is just make your son an administrator...
People said the same thing about IBM some 20 years ago. Then a little upstart came along with an OS they purchased from some little company in the Pacific Northwest. They licensed it to IBM and everyone else.
Fast forward - here is a similar situation, except that the OS is free and the incumbent has a much better foothold than IBM ever did.
I did have one problem with commercial binaries for linux: basically, SimCity 3000 has issues running on newer kernels because of the dynamic linker. Basically, it segfaults. A guick google revealed the solution: 'LD_ASSUME_KERNEL=2.2.4/usr/local/games/SC3U/sc3u' And it works.
This is no worse than the problems I've had running old (circa 1998) games on Windows XP (such as the Windows port of the old DOS game XCOM. Which, if you like XCOM, check out UFO Aftermatch. A completely new game, but really has that XCOM feel to it.)
- Seagate invented this "Fluid Dyamic Bearing" technology. As I understand it, rather than standard roller/ball bearings, an oil-like fluid is used so that the rotating shaft builds up pressure within a containing sleeve, similar to what happens with various drivetrain components in cars.
- The Seagate Barracuda IV drives pioneered using this technology about 4 years ago.
- Seagate licensed this technology to Maxtor.
- Other people may use it now, not sure.
- Just about all Seagate and Maxtor drives in the past 5 years use this technology.
- Yes, Seagate drives are typically more expensive, but they have a reputation for extensive testing and high reliability. (I'm not saying it's accurate or inaccurate, just that this is the rep - substantiated by the fact that most non-IBM servers used Seagate drives, though this has changed in recent years.)
- I run a mixture of Maxtor and Seagate drives, all with this technology, and have never had an issue with them.
Despite the tone of your response, you make a valid point in the first paragraph. Therefore I concede the point. Slashcode is fine the way it is because only the things you want to be links should be, and everything else should just be text. I was in error, and apologise.
I didn't say that any of those were hard. I'm saying it's hardER than just cutting and pasting a URL. And since it's hardER, my original question stands: why impose that burden on a user? Shouldn't you make it as easy as possible on your users?
Actually, I purposely didn't, because the/. engine coders really piss me off in this regard. Auto detecting a URL and having your submit handle it correctly isn't hard. Why impose that burden on a user? It's just bad design (and I've never heard any rationale justifying it). Most blog and WiKi engines do it this way, why not Slashdot?
It's one of the conditions of being a "Gold Level" partner.
Of course, this makes one realize how nonsensical the "window of vulnerability" arguments comparing Windows vs. Linux security are. For those of you who don't know, these arguments compare how much time time from announcement of a vulnerability to the time that the patch comes out. The F/OSS community is big into full disclosure, and the MS community isn't, so, the MS Window of vunlerability is almost always smaller, hence leading to claims that it's more secure. That is, until someone finds a bug that's been swept under the rug for a couple years and uses it to make the next Nimda.
I used Gentoo for awhile, but the huge times it took to update the system started to get to me. Plus, Ubuntu is polished enough that I can recommend it to family for casual use.
Actually, if memory serves, MS *does* control these situations. If you are a Microsoft Partner (I don't know at which level this restriction starts, but I think it's just about any partner), then you are required to disclose the vulnerability to Microsoft, and cannot disclose it publically until Microsoft allows you to. Failure to adhere to this results in a loss of your favored status.
Yes, you are correct, but this is Slashdot, and most people don't draw the distinction between WM/DE, and when talking about the "features" of each, they're talking about the features of the DE's WM's and typically not the other features.
Also, where's the Rendezvous support? KDE added mDNSResponder support, but where's the same from the GNOME crew?
Slashdot Mirror
Simple - by promising this they:
1.) Stop OpenOffice migrations (why migrate when we can just wait for MS to come out with their solution and we'll just buy that)
2.) Get people to upgrade to the next Office.
#1 is typical of MS - promise something, people wait, your competition can't survive when their business dries up, then you kill the project. Problem is, this isn't a pay-for product, so it's not going to go away.
#2 is the real thing - people will buy the next version of office, which is a huge problem for them.
Of course, I wouldn't be surprised if this ends up being a bait and switch...
I click on the link and get an ASPX (ASP.NET) runtime error..
LMAO..
A refresh seems have it just report a generic (properly rendered) "there is a problem with the forums" page.
Damn skippy. LaTeX has the best output of anything I've ever used, and auto-formats bits in a non-annoying way.
Don Knuth is the man.
I was unaware of that development. Thanks for the info; I'll look in to it.
Nope, I have, except that logic dictates that code that constantly executes under a VM will be slower than code that is JIT compiled and then runs as native code. Of course, this implies that programming skills are equal and all that.
Plus (and perhaps more importantly), all the Java gui toolkits I've seen (well, except the ones running under OSX) look like ass and customers hate them.
C++ provides a good transition to C#. MFC is a leaky, unstable piece of shit. Either use the old Win32 API (more difficult to program for, but leaks memory less and crashes less). I've been using C# under both .NET and Mono (using the GTK# widget set for GUI bits) and have been quite happy with it. .NET/Mono has some really nice things that make it way better than C++. (Full disclosure - I've never used Objective-C or Java, so I have no opinion on those).
I work for a consulting company. We go where the money is. Clients want something on Windows, we write for Windows. Clients want something on Linux, we write for Linux. Client want something on Solaris, we write for Solaris. .NET/Mono is kind of nice because it allows anything to run anywhere (at least, in theory. Practice has some holes in it, but it will get better).
Nope. I think you need XP Pro for that.
Just like there's no "security" tab to set file permissions in XP Home. At least, I couldn't find one on Home in the same place it was in Pro. Of course, a SP might have fixed it.
Worms 2 is a great game.
The other thing you could do is just make your son an administrator...
Family Guy is much more amusing if you are from Rhode Island (as I am).
Just like Farelly Bros. Movies.
FC3 and OSX 10.3 came out, what? 2 YEARS after XP? Sounds like a logical keeping up with the rate of progress in the PC industry, to me.
Or Ubuntu...
People said the same thing about IBM some 20 years ago. Then a little upstart came along with an OS they purchased from some little company in the Pacific Northwest. They licensed it to IBM and everyone else.
Fast forward - here is a similar situation, except that the OS is free and the incumbent has a much better foothold than IBM ever did.
I did have one problem with commercial binaries for linux: basically, SimCity 3000 has issues running on newer kernels because of the dynamic linker. Basically, it segfaults. A guick google revealed the solution: /usr/local/games/SC3U/sc3u'
'LD_ASSUME_KERNEL=2.2.4
And it works.
This is no worse than the problems I've had running old (circa 1998) games on Windows XP (such as the Windows port of the old DOS game XCOM. Which, if you like XCOM, check out UFO Aftermatch. A completely new game, but really has that XCOM feel to it.)
That's what got me into computers.
Show them TuxRacer or something, and explain that it was made by a bunch of people like you.
In the late 1980's, I wasn't even a teenager. :-)
Feel old yet?
Just goes to show that so many good ideas are shelved, just to be ressurected or reinvented years later.
Yes, the Barracuda's changed.
- Seagate invented this "Fluid Dyamic Bearing" technology. As I understand it, rather than standard roller/ball bearings, an oil-like fluid is used so that the rotating shaft builds up pressure within a containing sleeve, similar to what happens with various drivetrain components in cars.
- The Seagate Barracuda IV drives pioneered using this technology about 4 years ago.
- Seagate licensed this technology to Maxtor.
- Other people may use it now, not sure.
- Just about all Seagate and Maxtor drives in the past 5 years use this technology.
- Yes, Seagate drives are typically more expensive, but they have a reputation for extensive testing and high reliability. (I'm not saying it's accurate or inaccurate, just that this is the rep - substantiated by the fact that most non-IBM servers used Seagate drives, though this has changed in recent years.)
- I run a mixture of Maxtor and Seagate drives, all with this technology, and have never had an issue with them.
Despite the tone of your response, you make a valid point in the first paragraph. Therefore I concede the point. Slashcode is fine the way it is because only the things you want to be links should be, and everything else should just be text. I was in error, and apologise.
I didn't say that any of those were hard. I'm saying it's hardER than just cutting and pasting a URL. And since it's hardER, my original question stands: why impose that burden on a user? Shouldn't you make it as easy as possible on your users?
Actually, I purposely didn't, because the /. engine coders really piss me off in this regard. Auto detecting a URL and having your submit handle it correctly isn't hard. Why impose that burden on a user? It's just bad design (and I've never heard any rationale justifying it). Most blog and WiKi engines do it this way, why not Slashdot?
Err, there are no spaces in the URL.
/.
Farking
Since folks moderated this so highly, here's more info:
4 80 6/24806.html
http://www.windowsitpro.com/Article/ArticleID/2
It's one of the conditions of being a "Gold Level" partner.
Of course, this makes one realize how nonsensical the "window of vulnerability" arguments comparing Windows vs. Linux security are. For those of you who don't know, these arguments compare how much time time from announcement of a vulnerability to the time that the patch comes out. The F/OSS community is big into full disclosure, and the MS community isn't, so, the MS Window of vunlerability is almost always smaller, hence leading to claims that it's more secure. That is, until someone finds a bug that's been swept under the rug for a couple years and uses it to make the next Nimda.
I used Gentoo for awhile, but the huge times it took to update the system started to get to me. Plus, Ubuntu is polished enough that I can recommend it to family for casual use.
Actually, if memory serves, MS *does* control these situations. If you are a Microsoft Partner (I don't know at which level this restriction starts, but I think it's just about any partner), then you are required to disclose the vulnerability to Microsoft, and cannot disclose it publically until Microsoft allows you to. Failure to adhere to this results in a loss of your favored status.
Aha! It is in there (I installed it for something else, it never occurred to me to check it for that behavior).
That said, it's still enabled by default, and most folks won't bother to change it.
I agree, TweakUI should be a control panel applet or something.
Yes, you are correct, but this is Slashdot, and most people don't draw the distinction between WM/DE, and when talking about the "features" of each, they're talking about the features of the DE's WM's and typically not the other features.
Also, where's the Rendezvous support? KDE added mDNSResponder support, but where's the same from the GNOME crew?