I think that the point is so that the program can "provide a snappy, high-quality UI experience even when the program is performing tasks that are inherently slow."
The big problem I have with Ruby is that people always focus on Ruby on Rails, rather than the language itself.
News Flash! Rails is not Ruby. It is the current "killer app" (actually a set of libraries) written in Ruby, and you can find similar libraries available for other languages as well.
BUT, what is really impressive is that Wine actually managed to run all the tests. The compatibility is indeed impressive. This benchmark would have been very credible had it not played with the numbers and colors.
It didn't manage to run all the tests. FTA:
Wine or XP aborted on 18 tests
The breakdown for that is 3 for Windows and 15 for Wine.
Not only are the marks of less than 1% thrown into the green category, so are the 0 difference marks. That's right, Wine is marked as a winner if they perform exactly the same.
There was no business case for the transition from ARPANET's old NCP protocol to TCP/IPv4 in the 1980s - but there were technically compelling reasons. Luckily the ARPANET pioneers realized that a new protocol was needed to easily integrate the new services and applications they were thinking of deploying.
To be exact, ARPANET switched from NCP to TCP/IP on January 1, 1983. NCP had a few shortcomings
Like UDP, NCP had no way of handling lost packets. TCP introduced packet acknowledgement to fix this.
NCP had no real routing. TCP/IP introduced the concept of gateways, routers, and independant networks/subnets.
The difference between IPv4 and IPv6? The size of the address space and the human representation of the addresses (hexadecimal instead of decimal).
While we're on the subject, it took over 8 years from the publication of Vint Cerf and Robert Kahn's A Protocol for Packet Network Interconnection (May 1974), which described TCP, for ARPANET to incorporate TCP/IP.
It's also important to note that the size of the Internet in the 1980s was nothing like it is today. The Internet only had 562 hosts in August 1983, 8 months after the changeover. The same source states that the Internet had 353,284,187 hosts in July 2005. (Source: Hobbes' Internet Timeline, with data taken from Mark Lottor's zone program reports, and the
ISC)
You are correct that I had misinterpreted some of the things listed on that page, though. It's been some time since I've read the entire spec, and the last time I read the entire thing, img had been pulled out. The Major Differences with XHTML 1 section still implies that it is gone, in the following text, emphasis added by me.
Images: the HTML img element has many shortcomings: it only allows you to specify a single resource for an image, rather than offering the fallback opportunities of the object element; the only fallback option it gives is the alt text, which can only be plain text, and not marked up in any way; the longdesc attribute which allows you to provide a long description of the image is difficult to author and seldom supported.
XHTML 2 takes a completely different approach, by taking the premise that all images have a long description and treating the image and the text as equivalents...
h7 was a typo, and my understanding (based on an article I read quite some time ago) was that h1-h6 were already pulled from the spec. I probably should have looked that up, but it's too late now.
I would love to go back and edit the original list, or even clarify that some of these are just "best practices," but Slashdot's commenting system prevents me from doing that.
P.S. I checked all the other tags, and the comments on them are correct.
Since they have experiences from different games, I'll do something different: combine elements from several different MMOs together into a single experience.
One day, I was out fightning kobolds in Antonica, when suddenly I was ambushed by the Horde. I managed to get away from them, but I then got stopped by an Imperial patrol, who discovered that I was a Rebel.
They were much more powerful than I was, so I fled for my Mog House. Unfortunately, my distaff still hadn't finished, so I went back out to Antonica...
Bad examples, for your point. Stage Coaches, horse drawn carriages, and Model T's can operate on current roads.
That's funny, because I'm pretty sure that changing to XHTML 2.0 would still use the same Internet connection I already have, as well as the same protocol (HTTP 1.1). XHTML 2.0 has a different mime-type, so you can tell whether XHTML or HTML is being used.
Before you say it, yes, XHTML 1.x does work with text/html, but you'll also notice that XHTML 1.x has not removed support for any tags, unlike XHTML 2.x.
To be exact, XHTML 2.0 does away with the following tags:
br
hr
h1-h7
img (all elements will now support src=)
form, input, textarea
ins, del
script
frame functions - Has been relegated to XFrames
It adds
nl - Navigation List
l - A container tag that replaces br.
section - For dividing a document into sections, works with h.
h - context-aware header tag, replaces h1-h7.
separator - hr renamed. It still isn't a container tag.
script has been replaced by handler, which uses XML Events instead of classic HTML listener events.
XForms - Replaces HTML forms
src attribute - Any element can now have an image replace it. No more futzing around with img alt=
href attribute - Any element can now have a linking attribute. a has been retained in the language, even though its functionality is now gone.
role attribute - You can now mark the purpose of particular elements.
Not that I ever use IE by choice, but it appears that XP SP2 added exactly what you're describing above, as well as blocking ActiveX by default in the Internet Zone. A bar similar to the Popup blocker shows up at the top, the system makes a blat sound, and you have to click "Install ActiveX control" (or something like that) on that bar before you even get the "Do you want to install this ActiveX control?" (another paraphrase) dialog.
Windows likes the name quartz, too. For instance, quartz.dll on Windows is the name of the DirectShow runtime Library. DirectShow is part of Windows Media Player's 2D graphics acceleration.
Slashdot Mirror
I think that the point is so that the program can "provide a snappy, high-quality UI experience even when the program is performing tasks that are inherently slow."
You can also use the ADODB to make database code more portable, or if you have a new enough version of PHP, PDO.
News Flash! Rails is not Ruby. It is the current "killer app" (actually a set of libraries) written in Ruby, and you can find similar libraries available for other languages as well.
Operating systems?
Office suites?
Web browsers?
Really? OK, I agree with the great-grandparent, then. A 16-octet address is just ridiculous.
It didn't manage to run all the tests. FTA:
The breakdown for that is 3 for Windows and 15 for Wine.
Not only are the marks of less than 1% thrown into the green category, so are the 0 difference marks. That's right, Wine is marked as a winner if they perform exactly the same.
3DMark 06 is out now, too.
IPv4 has 2**32 (4294967296) addresses (4 8-bit numbers).
IPv6 only has 2**48 (281474976710656) addresses (6 8-bit numbers), nowhere near the 2**128 you're quoting.
To be exact, ARPANET switched from NCP to TCP/IP on January 1, 1983. NCP had a few shortcomings
The difference between IPv4 and IPv6? The size of the address space and the human representation of the addresses (hexadecimal instead of decimal).
While we're on the subject, it took over 8 years from the publication of Vint Cerf and Robert Kahn's A Protocol for Packet Network Interconnection (May 1974), which described TCP, for ARPANET to incorporate TCP/IP.
It's also important to note that the size of the Internet in the 1980s was nothing like it is today. The Internet only had 562 hosts in August 1983, 8 months after the changeover. The same source states that the Internet had 353,284,187 hosts in July 2005. (Source: Hobbes' Internet Timeline, with data taken from Mark Lottor's zone program reports, and the ISC)
So, on Tue, 19 Jan 2038 03:14:08 GMT?
One company does not an industry make.
Technically, wasn't it Sierra that published most of Valve's games, back before they were swallowed by Vivendi?
Not unless you invent a time machine and go back in time to warn yourself to not watch it. That's what I did, or so I told myself!
You are correct that I had misinterpreted some of the things listed on that page, though. It's been some time since I've read the entire spec, and the last time I read the entire thing, img had been pulled out. The Major Differences with XHTML 1 section still implies that it is gone, in the following text, emphasis added by me.
h7 was a typo, and my understanding (based on an article I read quite some time ago) was that h1-h6 were already pulled from the spec. I probably should have looked that up, but it's too late now.
I would love to go back and edit the original list, or even clarify that some of these are just "best practices," but Slashdot's commenting system prevents me from doing that.
P.S. I checked all the other tags, and the comments on them are correct.
I was looking at the latest draft, the Backwards Compatibility section to be exact.
One day, I was out fightning kobolds in Antonica, when suddenly I was ambushed by the Horde. I managed to get away from them, but I then got stopped by an Imperial patrol, who discovered that I was a Rebel.
They were much more powerful than I was, so I fled for my Mog House. Unfortunately, my distaff still hadn't finished, so I went back out to Antonica...
Wash, rinse, repeat...
That's funny, because I'm pretty sure that changing to XHTML 2.0 would still use the same Internet connection I already have, as well as the same protocol (HTTP 1.1). XHTML 2.0 has a different mime-type, so you can tell whether XHTML or HTML is being used.
Before you say it, yes, XHTML 1.x does work with text/html, but you'll also notice that XHTML 1.x has not removed support for any tags, unlike XHTML 2.x.
To be exact, XHTML 2.0 does away with the following tags:
- br
- hr
- h1-h7
- img (all elements will now support src=)
- form, input, textarea
- ins, del
- script
- frame functions - Has been relegated to XFrames
It addsThis letter is dated November 25, 2005. It's January 26, 2006. Do you see the problem here?
Because of Pac-man, I eat pills and hallucinate that I eat ghosts.
Actually, there's only two in a row. A post was made to the Games category between the second and third.
Security Zones are still a bit of a mess, though.
The scary part is... it's still more secure than XP is. There were a few NT 4/2000/XP only holes.
Windows likes the name quartz, too. For instance, quartz.dll on Windows is the name of the DirectShow runtime Library. DirectShow is part of Windows Media Player's 2D graphics acceleration.
Now, if only they could fix the Firefox memory leak...