That's simple : DivX is a video software, not a video format. It always has been. DivX 4-6 is based on one standard format : MPEG-4 Part 2 (aka MPEG-4 Visual, aka MPEG-4 ASP). So they are just updating their software to support the latest standard format, H.264 (aka MPEG-4 part 10, aka MPEG-4 AVC).
The question should be which container are the using. If they are using the AVI container then I have to ask why? Surely the MPEG4 container is doing the job just fine? When Divx first came out I could understand the need, since they were dealing with a codec which wasn't officially available, with a container which wasn't officially available, which isn't the case right now with H.264 & MPEG 4.
I have just installed Windows 7 in Virtual Box, on my Mac, and I am getting OS2 Warp Flash backs. The UI feels rushed, non-uniform and difficult to use, when compared to Windows XP or any other non-Microsoft OS. In terms of graphics presentation something went wrong:
- The icons: Looking at the task bar the first thing I notice is an inconsistent style of icons, almost as a programmer hacked something together in his/her spare time, looking as if they were designed for Windows 95, or grabbed from a random selection of desktop themes.
- The start menu: fancy but I get lost as things quickly disappear and start feeling claustrophobic
- Windows Explorer: The folders on the left look very boxy and the arrangement does not look natural
I have just scratched the surface here, but I really get the feeling that the UI team was fired before the project started, or at least if they are still around need to get fired now. When I compare this to KDE or Gnome, which has been done by many dedicated developers in their spare time, I have to ask myself how Windows could look this bad with a full-time salaried staff?
I am being hard on Windows 7 since it is meant to be fixing what Vista got wrong. Sure I probably don't have Aero activated, but the design issues are fundamental ones.
Sorry to have to break it to you. But much of the flash in Vista and Windows 7 is borrowed from Mac OS X, which is currently eating away at Windows market share.
Customers seem to like bling. So of course MS is going to offer it.
Customer like bling, aka eye candy, but don't like paying the cost of the hardware need to support it. All OSs borrow off each other, so there is not point saying x copied y, since the chances are that if it worked well then they probably did. The key is not simply offering eye candy, but making sure it doesn't complicate the operation it is meant to beautify.
So... the summary is basically saying that the problems everyone complained about with Vista, seem to be basically still there with Windows 7?
I am wondering whether they did a few small tweaks, sat on their asses and then did what the Vista advert did: call it something else and see if people thought it was better. Of course I am being cynical and only side by side testing will reveal how much has changed.
Certainly, but I see nothing on D-Link's site. If it is not documented on their site, then it is not supported, ie I wouldn't be able to complain that the feature is broken, since their support team would claim their hardware doesn't support it. Remember the difference between capable and supported.
Or is that list of ipv6 capable ISPs depressingly short?
You must be in North America, like me. Providers in Europe, Asia and Africa seem to be leaving us in the dust here. Then again when I check what free.fr is offering their customers in general, I feel we are being left in the dark ages in North America.
I am not sure there is much benefit in pinging the localhost;)
Joking aside, the colon form is probably a pain the butt, but it is one of the side-effects of more available addresses. You should learn to deal with it. At the same time, I would like to see stuff like 'Bonjour' become more common, so that local networks don't even need to use numbers. For example if your router supports Bonjour, then you would simply need to point your browser to router.local, or something of the sort.
Sweet, so I have Google doing IPv6, my OS doing IPv6, yet there are still a finger full of gateway/routers, targeted at the home market, providing IPv6 support. The only router claiming IPv6 support in their specifications is the Apple Airport. Linksys and D-Link apparently have plans, yet nothing in the user documentation. For me, if the manufacturer doesn't document IPv6 in its user document or specification on its web site, then it is as good as not supporting IPv6 - after all I doubt their support team would be any more clued in.
Don't get me wrong, I am all for IPv6, its just that I am fed up having to deal with tunnels because certain parties are dragging their feet.
I have version 8.00.5 of the Firmware installed on this model and there is no evidence of IPv6 support. I double checked and if it is there it is either not activated or hidden from the UI. Last time I asked Linksys, which was about a couple of months back, they told none of their routers supported IPv6. If the company claims they don't have support for it and it is not available to the user, then it is not available.
Hopefully they will get IPv6 in as a standard feature. I get annoyed at being told I need to start getting ready for IPv6, only to find out that the Apple Airport is more or less the only one offering this feature out of the box.
In certain places, such as in France, there are already ISPs that offer IPv6 to their customers. Living in Canada I would like this to be the case too, but even apparently tech oriented ISPs such as Tech Savvy fail to do so.
The other problem is there are still a lot of companies not selling IPv6 capable routers. Example of router manufactures who seem to be doing an effort are Apple and Buffalo. D-Link apparently has a road plan, but other companies such as Linksys are missing in action.
I have tried discovering and trying to understand IPv6 to the best of my ability, but in doing so realise that there is still work to be done to make it appear as straight forward as IPv4. While there is radvd, DHCPv6 needs to be made available in all operatings. Either that or radvd needs to provide support for discovering of the DNS server and other services. There is Bonojour, but until this is made a standard on all operating systems, then DHCPv6 is the best way to go. MacOS X is one OS not yet supporting DHCPv6, and I hope that it is provide to Snow Leopard and made available to Leopard.
If you look at the libsdl project page then you will see plenty of games. If you look elsewhere you see old games being ported to Linux. The problem is this whole attitude of wanting stuff for free. Games, especially good ones, cost lots of money to make and expecting them for free is like asking Mercedes to give you a free car. Until people can accept that paying for stuff you like helps make more of the stuff you like, then you will only see a trickle of new stuff. I hate to say it, but this is the way things are.
Add to the list:
- Network devices that have never been connected warn you they aren't connected.
- Notifications of systems updates, even though you haven't been connected for the past week!?
Isn't Slashdot all about reading the articles and discussing them in a civilised manner?
You must be new here. Based on the experience of the past three years:
1. Read Summary and then comment on summary, assuming it is correct interpretation of article. 2. Correction is posted 300 posts later, from the one person who read the article. 3. Correction gets moderated positive on the condition the moderators actually read the article.
When I hear this I worry about seeing Windows CE style applications being pushed to the iPhone. Then again I imagine if the applications don't fit the user experience guidelines Apple will simply prevent them from coming to the store.
The other problem is that the proposed approach essentially is such a mess that it actually shoot itself in the foot. By creating so many new TLDs confusion created, rather that eliminated and we potentially end up in a situation when where TLDs are useless.
This is why interpreted or semi-interpreted programming languages make so much sense, especially for stuff such as web applications. Here you can scale to what ever the best hardware is, even changing CPU, without worrying that you will need to recode, or recompile. The same can't generally be said for languages such as C++. Its ironic that you would have to choose a approach that is probably less optimal to get cheaper long term improvements in performance.
Slashdot Mirror
That's simple : DivX is a video software, not a video format. It always has been. DivX 4-6 is based on one standard format : MPEG-4 Part 2 (aka MPEG-4 Visual, aka MPEG-4 ASP). So they are just updating their software to support the latest standard format, H.264 (aka MPEG-4 part 10, aka MPEG-4 AVC).
The question should be which container are the using. If they are using the AVI container then I have to ask why? Surely the MPEG4 container is doing the job just fine? When Divx first came out I could understand the need, since they were dealing with a codec which wasn't officially available, with a container which wasn't officially available, which isn't the case right now with H.264 & MPEG 4.
I have just installed Windows 7 in Virtual Box, on my Mac, and I am getting OS2 Warp Flash backs. The UI feels rushed, non-uniform and difficult to use, when compared to Windows XP or any other non-Microsoft OS. In terms of graphics presentation something went wrong:
- The icons: Looking at the task bar the first thing I notice is an inconsistent style of icons, almost as a programmer hacked something together in his/her spare time, looking as if they were designed for Windows 95, or grabbed from a random selection of desktop themes.
- The start menu: fancy but I get lost as things quickly disappear and start feeling claustrophobic
- Windows Explorer: The folders on the left look very boxy and the arrangement does not look natural
I have just scratched the surface here, but I really get the feeling that the UI team was fired before the project started, or at least if they are still around need to get fired now. When I compare this to KDE or Gnome, which has been done by many dedicated developers in their spare time, I have to ask myself how Windows could look this bad with a full-time salaried staff?
I am being hard on Windows 7 since it is meant to be fixing what Vista got wrong. Sure I probably don't have Aero activated, but the design issues are fundamental ones.
Sorry to have to break it to you. But much of the flash in Vista and Windows 7 is borrowed from Mac OS X, which is currently eating away at Windows market share.
Customers seem to like bling. So of course MS is going to offer it.
Customer like bling, aka eye candy, but don't like paying the cost of the hardware need to support it. All OSs borrow off each other, so there is not point saying x copied y, since the chances are that if it worked well then they probably did. The key is not simply offering eye candy, but making sure it doesn't complicate the operation it is meant to beautify.
So... the summary is basically saying that the problems everyone complained about with Vista, seem to be basically still there with Windows 7?
I am wondering whether they did a few small tweaks, sat on their asses and then did what the Vista advert did: call it something else and see if people thought it was better. Of course I am being cynical and only side by side testing will reveal how much has changed.
Will this card support OpenCL?
Thanks for the info.
D-Link and Cisco support IPv6.
Certainly, but I see nothing on D-Link's site. If it is not documented on their site, then it is not supported, ie I wouldn't be able to complain that the feature is broken, since their support team would claim their hardware doesn't support it. Remember the difference between capable and supported.
Or is that list of ipv6 capable ISPs depressingly short?
You must be in North America, like me. Providers in Europe, Asia and Africa seem to be leaving us in the dust here. Then again when I check what free.fr is offering their customers in general, I feel we are being left in the dark ages in North America.
Can these glasses be worn over prescription glasses?
I am not sure there is much benefit in pinging the localhost ;)
Joking aside, the colon form is probably a pain the butt, but it is one of the side-effects of more available addresses. You should learn to deal with it. At the same time, I would like to see stuff like 'Bonjour' become more common, so that local networks don't even need to use numbers. For example if your router supports Bonjour, then you would simply need to point your browser to router.local, or something of the sort.
Sweet, so I have Google doing IPv6, my OS doing IPv6, yet there are still a finger full of gateway/routers, targeted at the home market, providing IPv6 support. The only router claiming IPv6 support in their specifications is the Apple Airport. Linksys and D-Link apparently have plans, yet nothing in the user documentation. For me, if the manufacturer doesn't document IPv6 in its user document or specification on its web site, then it is as good as not supporting IPv6 - after all I doubt their support team would be any more clued in.
Don't get me wrong, I am all for IPv6, its just that I am fed up having to deal with tunnels because certain parties are dragging their feet.
I have version 8.00.5 of the Firmware installed on this model and there is no evidence of IPv6 support. I double checked and if it is there it is either not activated or hidden from the UI. Last time I asked Linksys, which was about a couple of months back, they told none of their routers supported IPv6. If the company claims they don't have support for it and it is not available to the user, then it is not available.
Hopefully they will get IPv6 in as a standard feature. I get annoyed at being told I need to start getting ready for IPv6, only to find out that the Apple Airport is more or less the only one offering this feature out of the box.
In certain places, such as in France, there are already ISPs that offer IPv6 to their customers. Living in Canada I would like this to be the case too, but even apparently tech oriented ISPs such as Tech Savvy fail to do so.
The other problem is there are still a lot of companies not selling IPv6 capable routers. Example of router manufactures who seem to be doing an effort are Apple and Buffalo. D-Link apparently has a road plan, but other companies such as Linksys are missing in action.
I have tried discovering and trying to understand IPv6 to the best of my ability, but in doing so realise that there is still work to be done to make it appear as straight forward as IPv4. While there is radvd, DHCPv6 needs to be made available in all operatings. Either that or radvd needs to provide support for discovering of the DNS server and other services. There is Bonojour, but until this is made a standard on all operating systems, then DHCPv6 is the best way to go. MacOS X is one OS not yet supporting DHCPv6, and I hope that it is provide to Snow Leopard and made available to Leopard.
If you look at the libsdl project page then you will see plenty of games. If you look elsewhere you see old games being ported to Linux. The problem is this whole attitude of wanting stuff for free. Games, especially good ones, cost lots of money to make and expecting them for free is like asking Mercedes to give you a free car. Until people can accept that paying for stuff you like helps make more of the stuff you like, then you will only see a trickle of new stuff. I hate to say it, but this is the way things are.
Add to the list:
- Network devices that have never been connected warn you they aren't connected.
- Notifications of systems updates, even though you haven't been connected for the past week!?
Turns out the closest Ubuntu project is http://www.mumbles-project.org/
Another team has started a port of Growl to MS-Windows:
http://code.google.com/p/growl-for-windows/
Given the way things are, maybe Growl should simply be port to Linux, so that the same themes can be used?
I have 60 petabyte of songs downloaded
Is there that much recorded music in the world?
Are we talking MP3 or uncompressed? If we are talking the latter, then it is very possible.
Isn't Slashdot all about reading the articles and discussing them in a civilised manner?
You must be new here. Based on the experience of the past three years:
1. Read Summary and then comment on summary, assuming it is correct interpretation of article.
2. Correction is posted 300 posts later, from the one person who read the article.
3. Correction gets moderated positive on the condition the moderators actually read the article.
Why am I still here? Baaaaah ;)
When I hear this I worry about seeing Windows CE style applications being pushed to the iPhone. Then again I imagine if the applications don't fit the user experience guidelines Apple will simply prevent them from coming to the store.
If you otherwise like Google Chrome, then SRWare Iron is the browser you should be checking out: http://www.srware.net/en/software_srware_iron.php
tlds largely are useless, anything other than .gov or .edu is a mess
Part of the problem is domain parking. I thought ICANN was meant to crack down on this, but once again money has continued the corruption.
The other problem is that the proposed approach essentially is such a mess that it actually shoot itself in the foot. By creating so many new TLDs confusion created, rather that eliminated and we potentially end up in a situation when where TLDs are useless.
This is why interpreted or semi-interpreted programming languages make so much sense, especially for stuff such as web applications. Here you can scale to what ever the best hardware is, even changing CPU, without worrying that you will need to recode, or recompile. The same can't generally be said for languages such as C++. Its ironic that you would have to choose a approach that is probably less optimal to get cheaper long term improvements in performance.