Koreans Advised to "Avoid Vista" for Now
An anonymous reader writes "The Chosonilbo reports that several government ministries in South Korea are advising users not to install Windows Vista, at least until popular online services can be made compatible. The problem is that ActiveX is pervasive in the Korean webspace, employed by everyone from web games to online banking. Upgrading to Vista is expected to render many of these services unusable. Portions of the popular "Hangul" word processor, a major competitor to Office in that country, are also not functioning under Vista. The Ministry of Information is planning to publish compatibility information for popular websites, and urging users to carefully research the implications of upgrading."
I thought all businesses were avoiding Vista...I doubt that Korea needed to issue an advisory to get people to stay away.
Drink Microsoft's proprietary koolaid more heavily. Oh yea...
Online backup with Mozy, sounds like Ozzie, but more!
ummm, perhap you didn't get the memo, but TV's are CRT as well. There doesn't seem to be a rash of people with 'french fried' face wandering around.
Oh, and yeah there right on the edge of imploding, so WATCH OUT!
WHat do you do for a living, generate false fears for compteting companies.
I mean, your post is so stupid and tries to craete some ilusion of fear.
What next? a post on how the car can kill people?
Jeez dude, get an F'n life.
The Kruger Dunning explains most post on
I am not a "windows consultant", whatever that might mean. ... prophecies of doom and gloom about this "kludgy piece of crap" become true ...
It means that part of your income is derived from selling people on the Windoze monopoly. I'm not sure what kind of income you get off some $20 program, but it's all the more surprising that you would advocate an upsell to Vista. If your software resembles your comments, it too is a kludgy piece of crap dependent on specific versions of Windoze.
Friends don't help friends install M$ junk.
VB.Net's kiddie syntax:
:-)
Class MyClass
Private x As Integer
Public Property X() As Integer
Get
Return x
End Get
Set(ByVal Value As Integer)
x = value
End Set
End Property
End Class
C#'s concise syntax:
public class MyClass
{
int x;
public int X
{
get {return x;}
set {x = value;}
}
}
or if you like your code _really_ short:
public class MyClass { int x; public int X { get {return x;} set {x = value;} } }
I prefer the first C# example. A few lines here and there add up to
thousands on a medium to large project. I think it is silly to have all
these different end statements and Dim's and tons of other keywords in
VB.Net that are not needed. Anyone should be able to look at code and
tell if the code is declaring a variable or a method is returning a value
or void.
Thanks for playing moron.
General, you are listening to a machine! Do the world a favor and don't act like one.