But DTS does sound a lot better when played back through a decent sound-system. I seem to remember DTS is generally recorded at a higher bit-rate which would explain the difference
The short answer is that they're nothing to do with each other.
.net is the newest MS programming environment. Their marketing department originaly decided to brand everything.net, even if it wasn't strictly related. When they realised how confusing it was, they changed the product name from Server.net to Server 2003.
As far as.net in Windows 2003 goes, it simply comes preloaded instead of being installable - no biggie.
I think there is a world market for maybe five computers.
- Thomas Watson, chairman of IBM, 1943.
Hardly a foot-in-mouth moment! There probably was only a market for only five computers in 1943. I'd guess that the aircraft hangers required to house them were in short supply during WWII:)
That's why I don't know why people are embracing.net for other non-windows platforms. If you need a language to be dependant on vendor specific libraries that are difficult to implement, is your language really portable?
The libraries aren't vendor specific as per the poster's claims - from what I can tell (been using them a few months now), they are all high-level and nicely abstract. (Only a programmer could like something just because it's abstract!)
Maybe someone could pull my head out of me ass, and tell me honestly why a developer would want to write a.net program in Linux.
It's a cohesive development platform (unlike Java IMHO - with its multiple libraries and slightly incompatible application servers). It isn't perfect, but for a lot of applications it is the least worst solution out there
Hang on,.Net is essentially a replacement of COM! COM interop from C# is messy and feels like a hack at best
None of the functional areas you mention are actually ActiveX objects - they are in fact namespaces in the.Net framework. ADO (actually ADO.net is the replacement for ADO) is System.Data, DOM is System.Xml and the FSO (FileSystemObject) has been replaced by System.IO
It's a fair point, but there's a big difference between the x86 instruction set and the Windows API
The Intel instruction set is fully documented. The systems guys who cut OS code refer to the documentation in much the same way that I'm sure the Transmeta guys did
The Windows API on the other hand is famously not fully documented
... here in the UK and has always said 'beware the asthmatic, the overweight and the redhead!'
Apparently they also bleed more and have more laryngospasm (whatever that is!)
Slashdot Mirror
I use Windows mostly for work, and all of my friends use Windows exclusively. Are there any good Jabber clients for Windows?
Is there any facility for end-to-end encryption?
Does it work over port 80?
Selling out my rosy red ***. Running a site like this costs money
.. and you want that to be somewhere nice... The best option is to start your own business.
No Brit has any business calling themselves a citizen, they're subjects!
It returns an HTTP status of 404, so it is a proper 404
But DTS does sound a lot better when played back through a decent sound-system. I seem to remember DTS is generally recorded at a higher bit-rate which would explain the difference
The short answer is that they're nothing to do with each other.
.net is the newest MS programming environment. Their marketing department originaly decided to brand everything .net, even if it wasn't strictly related. When they realised how confusing it was, they changed the product name from Server.net to Server 2003.
.net in Windows 2003 goes, it simply comes preloaded instead of being installable - no biggie.
As far as
Is there any scope for distributed web page serving? That'd kill the Slashdot effect dead in one fell swoop. But wait... where's the fun in that? ;)
Duh, it isn't offtopic. Have you read the article? The guy who did the benchmarks shares the name with the guy who wrote the famous book
I want to know what it was like meeting Princess Diana!
Diana: Her True Story in Her Own Words by Andrew Morton
Picture messaging is the next mobile killer app. It is already huge in Japan. You (didn't) hear it here first!
The code behinds do help, but SQL shouldn't be in there either
:)
I couldn't agree more.. but you know it will
When was the last time you saw a select statement on a web page
.Net goes some way towards alleviating this as the code is usually placed in a paired class (codebehind).
Almost every ASP project I've seen has embedded SQL in the presentation pages (.asp files). Yuck.
... the slating that Simcity 4 has received. Good on them for having the courage to admit that it wasn't going to work.
I read it as 'steak-powered' :D
Dolby Digital or DTS, for example? If so, I'd certainly be interested
They work fine for me
I think there is a world market for maybe five computers.
:)
- Thomas Watson, chairman of IBM, 1943.
Hardly a foot-in-mouth moment! There probably was only a market for only five computers in 1943. I'd guess that the aircraft hangers required to house them were in short supply during WWII
Neither of whom is the chief at Intel.
Quite right. I have one, my brother has one, my father and many of my colleagues have one. None of them have had any problems that I know of
Funny. Everyone I know who bought one hates it. Besides, it isn't so much a smartphone as a regular phone with a colour screen
That's why I don't know why people are embracing .net for other non-windows platforms. If you need a language to be dependant on vendor specific libraries that are difficult to implement, is your language really portable?
.net program in Linux.
The libraries aren't vendor specific as per the poster's claims - from what I can tell (been using them a few months now), they are all high-level and nicely abstract. (Only a programmer could like something just because it's abstract!)
Maybe someone could pull my head out of me ass, and tell me honestly why a developer would want to write a
It's a cohesive development platform (unlike Java IMHO - with its multiple libraries and slightly incompatible application servers). It isn't perfect, but for a lot of applications it is the least worst solution out there
Hang on, .Net is essentially a replacement of COM! COM interop from C# is messy and feels like a hack at best
.Net framework. ADO (actually ADO.net is the replacement for ADO) is System.Data, DOM is System.Xml and the FSO (FileSystemObject) has been replaced by System.IO
None of the functional areas you mention are actually ActiveX objects - they are in fact namespaces in the
It's a fair point, but there's a big difference between the x86 instruction set and the Windows API
The Intel instruction set is fully documented. The systems guys who cut OS code refer to the documentation in much the same way that I'm sure the Transmeta guys did
The Windows API on the other hand is famously not fully documented
... here in the UK and has always said 'beware the asthmatic, the overweight and the redhead!' Apparently they also bleed more and have more laryngospasm (whatever that is!)