However, backing C# the language is not really very interesting at all unless they would also back IL, the intermediate language C# is compiled into. As far as I know that is not being sumitted to a standards body so Microsoft can change IL however it likes with each upgrade to C#, making sure everyone else
c# is compiled. The IL is most likely part of the standardised process, but it doesn't matter so much, since its easily reverse engeneeringalbe, and just like Java 1.2 needs a new JRE, so would MS common language runtime 1.1.
What is outside the standard process is this common language runtime. Its what needs the most porting effort. c# is basically c++ with vbrun700.dll architecture.
I don't own any USB devices because the spec was too slow. ( I could have gotten some joysticks or MIDI instruments, but I didn't)
Now (2.0) there is some major headroom. This can be a platform to network homes. Its fast enough to have a network display device, and send images from a sat receiver or vcr to any pc or other tv.
Well the story said it was true in the first line, so it must be, right?
There's lots of reason to do this as a contingency plan for MS. An interesting reason to leak the news is that its FUD that might cause the big players supporting linux to back off. Its in their interest to spread this rumour, whether or not the project is actually being run by a couple of coop students.
Linux on the desktop makes a lot of sense for supported business users who barely understand how to install something in windows, and so don't.
MS Office.net haveing a linux client available would be pretty big in letting them gouge everyone's money though. Only way it can charge its megabucks and still compete with staroffice.
I do believe this approach is the future. I don't think the state of FPGA's and cores are there yet to allow this to take place on the desktop for another 10 years. There's a good chance that these guys are an investmnet scam, but better use of transistors, is how we will keep up with moore's law until 2030 without nanotech/photonics/quantum computing.
The only reason we have integrated caches in processors is that the engineers have more transistors than they know what to do with. and memory is the easies thing to use them up with.
I'd say the colour accuracy is closer to 10-11 bits than 8. about 1500 bues.
VHS quality though has no standard, and is a marketing term. It is meant to be a description of sufficient quality to replace the VHS experience. It is extremely vague, and since the technology proponents wish to glorify their products, you should assume that their definition of VHS quality is a cheap vcr with dirty heads playing a 20th generation tape for the 100th time.
Analog artifacts are very different than digital ones. To me, and probably most viwers though, they are less irritating than digital artifacts.
I'd rather have less colour and sound depth with a smooth 30fps, than high res that skips and pauses, or occasional blocks where motion is occurring.
actually... this is a clause in rogers@home as well. However, all they are saying is that they will not support proxys and NAT. Not that they will refuse your money as customers.
I have a proxy. Its ok by them. They just won't answer support questions about it.
The benefit to u, of the sledgehammer is not the 64bitness. Its the dual cores on a single chip that will do it. Should be Cheaper (chip and MB) and faster than dual processors.
One option if to borrow TT fonts might be to make a format that uses the same parameters, but simply switches the ordering, and/or compresses the data. Then make a utility that converts from TT to freeTT. Freetype may already be doing something similar, I don't know.
The legalities of this may be shaky, but the risks of being successfully sued aren't that high.
.net, c#, and common language run times are all great ideas, but MS may still price them out of the market.
MS Office is probably the closest thing to being priced too high for MS's own good, and their trying to pry more $ then ever out of people for using it. Also, people won't be able to re-interpret their EUL into what seems fair to them.
>>
Choosing a language because of trifling syntactical details ("I don't like;'s") is inane. If we want to talk about syntax, why the hell does VB require a "_" every time you want to extend a command over more than one line.
>
and 95%+ of vb3 code will compile in vb6. For commerical or otherwise important software its not an issue. For 5 year old software that you'd like to update 50 lines or fewer of code, its a major cost and hassle getting new versions of compatible components.
Binary compatibility in components has the same serious flaw as allowing programmers to do pointer arithmetic. You can shoot yourself in the foot with it. As proven innumerable times by MS with its windows common controls, they will eventally break some program relying on an older verison of it. Its in fact a much worse flaw, as binary compatibity cannot be proven, no one is accountable for past versions of software failing, and no one can see through all the ways consumers of the component might rely on its behaviour.
the CLR is going to have more versioning problems than Java, and much more so than straight c++
VB is a better language than C++ on many levels. Much of its ridicule here, is short sighted.
MS's common runtime is going to bring the vb's debugging advantages to C++. Many VB developers who can stand;'s will switch. Probably many Delphi coders too.
The huge disadvantage with vb and Java, is that your code gets locked in to the version of the runtime you're using, upgrades seem mandatory, and its a trap many c++ people may fall into.
MS still has a few people convinced that they should only care about developing for win32.
There's pretty much no reason to develop new stuff in C++ if you only care about win32. It will compile your old code, and can do anything you can with c++ with an #inline statement.
It has more features than Java, and their IDE will probably be favoured by many.
The only way to stop the virus is to not use outlook express.
They are trying to make it sound less bad than it is by saying that default IE5.5 or 5.01sp installation is safe. That's cause the default installation doesn't install OE. The story even said something like most corporate networks with Outlook are safe, because they don't use pop3 or IMAP4, but i'm sure more than one does.
Maybe my ISP went down today to fix this major crap.
Slashdot Mirror
ur again showing your uninformednednessedthingyess
.net is not certificate based like current activeX controls on the web.
safe code under
its a VM. One mode of VC7 will allow c++ to target code for this vm (called managed code).
Thats a good guess, then.
The CLR provides common data formats to all languages using it, so you can do stuff like
myVbobj.name = yourCobj.name
If I were a music pirate, I would hope that SDMI gets approved and launched, and the RIAA relies on it as its sole copy management system.
Consumers won't accept it. Demand for alternative harware will overwhelm it.
c# is compiled. The IL is most likely part of the standardised process, but it doesn't matter so much, since its easily reverse engeneeringalbe, and just like Java 1.2 needs a new JRE, so would MS common language runtime 1.1. What is outside the standard process is this common language runtime. Its what needs the most porting effort. c# is basically c++ with vbrun700.dll architecture.
As the poster above me mentioned, will putting a usb1.x hub on one port, and a 2.0 hub on the other port solve the downspeeding problem?
I don't own any USB devices because the spec was too slow. ( I could have gotten some joysticks or MIDI instruments, but I didn't)
Now (2.0) there is some major headroom. This can be a platform to network homes. Its fast enough to have a network display device, and send images from a sat receiver or vcr to any pc or other tv.
Well the story said it was true in the first line, so it must be, right?
There's lots of reason to do this as a contingency plan for MS. An interesting reason to leak the news is that its FUD that might cause the big players supporting linux to back off. Its in their interest to spread this rumour, whether or not the project is actually being run by a couple of coop students.
Linux on the desktop makes a lot of sense for supported business users who barely understand how to install something in windows, and so don't.
MS Office.net haveing a linux client available would be pretty big in letting them gouge everyone's money though. Only way it can charge its megabucks and still compete with staroffice.
I do believe this approach is the future. I don't think the state of FPGA's and cores are there yet to allow this to take place on the desktop for another 10 years. There's a good chance that these guys are an investmnet scam, but better use of transistors, is how we will keep up with moore's law until 2030 without nanotech/photonics/quantum computing.
The only reason we have integrated caches in processors is that the engineers have more transistors than they know what to do with. and memory is the easies thing to use them up with.
I'd say the colour accuracy is closer to 10-11 bits than 8. about 1500 bues.
VHS quality though has no standard, and is a marketing term. It is meant to be a description of sufficient quality to replace the VHS experience. It is extremely vague, and since the technology proponents wish to glorify their products, you should assume that their definition of VHS quality is a cheap vcr with dirty heads playing a 20th generation tape for the 100th time.
Analog artifacts are very different than digital ones. To me, and probably most viwers though, they are less irritating than digital artifacts.
I'd rather have less colour and sound depth with a smooth 30fps, than high res that skips and pauses, or occasional blocks where motion is occurring.
actually... this is a clause in rogers@home as well. However, all they are saying is that they will not support proxys and NAT. Not that they will refuse your money as customers.
I have a proxy. Its ok by them. They just won't answer support questions about it.
The benefit to u, of the sledgehammer is not the 64bitness. Its the dual cores on a single chip that will do it. Should be Cheaper (chip and MB) and faster than dual processors.
It's less technically innovative, and the theoretical performance is lower than IA-64, but its not inferior.
Ease of transition is an important aspect. Its what will make it far more likely for any of us to buy x86-64 long before we touch ia-64.
From what I understand ME doesn't parse autoexec.bat anymore. Sun's JDK, and many apps ported from unix want to set the path in autoexec.bat.
Does this mean we'll have to launch them from batch files now?
One option if to borrow TT fonts might be to make a format that uses the same parameters, but simply switches the ordering, and/or compresses the data. Then make a utility that converts from TT to freeTT. Freetype may already be doing something similar, I don't know.
The legalities of this may be shaky, but the risks of being successfully sued aren't that high.
.net, c#, and common language run times are all great ideas, but MS may still price them out of the market.
MS Office is probably the closest thing to being priced too high for MS's own good, and their trying to pry more $ then ever out of people for using it. Also, people won't be able to re-interpret their EUL into what seems fair to them.
If its any consolation,
Typical java apps tend to have memory leaks or otherwise cause eventual reboots of the os when used with IE.
>> ;'s") is inane. If we want to talk about syntax, why the hell does VB require a "_" every time you want to extend a command over more than one line.
Choosing a language because of trifling syntactical details ("I don't like
>
and 95%+ of vb3 code will compile in vb6. For commerical or otherwise important software its not an issue. For 5 year old software that you'd like to update 50 lines or fewer of code, its a major cost and hassle getting new versions of compatible components.
Binary compatibility in components has the same serious flaw as allowing programmers to do pointer arithmetic. You can shoot yourself in the foot with it. As proven innumerable times by MS with its windows common controls, they will eventally break some program relying on an older verison of it. Its in fact a much worse flaw, as binary compatibity cannot be proven, no one is accountable for past versions of software failing, and no one can see through all the ways consumers of the component might rely on its behaviour.
the CLR is going to have more versioning problems than Java, and much more so than straight c++
VB is a better language than C++ on many levels. Much of its ridicule here, is short sighted.
;'s will switch. Probably many Delphi coders too.
MS's common runtime is going to bring the vb's debugging advantages to C++. Many VB developers who can stand
The huge disadvantage with vb and Java, is that your code gets locked in to the version of the runtime you're using, upgrades seem mandatory, and its a trap many c++ people may fall into.
MS still has a few people convinced that they should only care about developing for win32.
There's pretty much no reason to develop new stuff in C++ if you only care about win32. It will compile your old code, and can do anything you can with c++ with an #inline statement.
It has more features than Java, and their IDE will probably be favoured by many.
It would be cool if more games supported dual head. Maybe now that the nvidia mx does, it will catch on more.
Especially in quake. The best use would be to have 2 rear mirror views on the 2nd monitor, option to put stats, ammo, msg queue, scores etc there too.
If you read the MS page closer you would have noticed that both 5.01 and 5.5 are vulnerable if you install Outlook Express.
All versions of OE past 4.0 are vulnerable.
Common...
although this bug has a huge impact, i wouldn't call OE's developers or QA team incompetent over it.
not much text in here
moderate this up
Actually that complete BS.
The only way to stop the virus is to not use outlook express.
They are trying to make it sound less bad than it is by saying that default IE5.5 or 5.01sp installation is safe. That's cause the default installation doesn't install OE. The story even said something like most corporate networks with Outlook are safe, because they don't use pop3 or IMAP4, but i'm sure more than one does.
Maybe my ISP went down today to fix this major crap.