Not only can google's chrome browser decode h.264, but google's youtube site already has 100% of all their videos encoded to it as well. So in short, I can guarantee you that many free browswers already include it, and google has already paid the extremely small licensing fee. As has Microsoft and apple. The only significant hold out, Mozilla, and they are holding back progress on the web (as usual lately).
Copy paste from google owned youtube:
* Firefox 4 (WebM, Beta available here)
* Google Chrome (WebM and h.264)
* Opera 10.6+ (WebM, Available here)
* Apple Safari (h.264, version 4+)
* Microsoft Internet Explorer 9 (h.264, Beta available here)
* Microsoft Internet Explorer 6, 7, or 8 with Google Chrome Frame installed (Get Google Chrome Frame)
Apparently you don't understand that there are/were already 10x as many iPhones on the market before Android started to take off, but also that iPhones sold more units than Android last quarter. So I wouldn't say google is *owning*. They are far far behind, and they are falling even further behind. That said, #2 in smart phones is still a nice place to be.
It was probably easier to record the WiFi and store it as it is than try and outfit all 50,000 vehicles with enough computing power to be able to actually analyze the signal and pull out the MACs and SSIDs. More like it was just recorded on a tape and brought back to a computer center where the tape was then analyzed in a central location.
I see. We are probably just very lucky out here then that Comcast isn't overselling their local capacity by enough to affect us.
BTW, I do believe that I swapped out my modem for a DOCSIS 3.0 one not too long ago as I think they said that was required for a 50Mb/s connect. I just didn't have to swap it back to the older modem when I downgraded back to 16Mb/s.
Currently where I am, they consider 16Mb/s down, 5Mb/s up as the entry level. Noone has lower than that. All older connections got bumped up to that as it became available, with options for 20,25,30, 50Mb and supposidly 100Mbs as well.
DOCSIS 2.0 supports 30Mb/s upstream PER CHANNEL, and either 42 or 55Mb/s downstream PER CHANNEL. The channels aren't shared between users that I know of.
For example, my Comcast is capped at 16Mb/s (my choice, they also offer 25, 30 and 50Mb service), and my upstream will peak at 30Mb/s in short bursts (First 10MB or so) then settle back to 10Mb/s. A year ago I had completely uncapped service and was able to download at the full 42Mb/s rate (although I could swear it was 52-55Mb/s), and I saturated the line for a week with no issues, no slowdowns, and my neighbors were completely unaffected.
No, I never owned the Falcon, but I did have a 520ST, a 1040ST, and a modded 520STe all of which had 4MB of ram. The original 520ST could display 64,000 colors in the screen at one time through the use of changing the pallette every 16 pixels. At the beginning this took a considerable amount of CPU time, but better techniques were eventually developed, and lower color amount (19200 or 4k) took significantly less CPU time.
Please reference wikipedia, this was pretty well known, although it states only 19200 colors I am fairly certain that it was actually 64,000 (You could display any of 65,536 colors in any pixel location, but because there was only 64,000 pixels on the screen, it's technically just 64000 but you will see references to 64k color mode).
BTW, it was the YF chip that was in the original ST line (which was replaced in the newer models), however, the shifter chip was what gave the ST it's audio prowess. By using the shifter, you could radically change the output from the YF chip, and it was capable of outputting and sampling audio at 128KHz, which was decades ahead of its time. As I said, the YF did only have 3 channels compared to the Amiga's 4, but the amiga had nothing similiar to the shifter in its audio so it was completely dependent on it singular audio chip to do anything -- again, very limited in comparison. It was fairly trivial to take multiple virtual sound channels and software mix them into the 3 hardware channels, and apply shifter effects to each of those. The midi support was unparalleled by either the amiga or PC platforms and you would often see professional musicians using the ST in their sound rooms, or in live performances (I worked right next to a sound studio for a number of years).
From wikipedia: The ST's low cost, built-in MIDI ports, and fast, low-latency response times made it a favorite with musicians:
* The Fatboy Slim album You've Come A Long Way, Baby has an Atari ST in the large foldout picture of Fatboy Slim's studio.
* Highly acclaimed electronic music artists Mike Paradinas and Luke Vibert started out writing music on Atari STs.
* Mike Oldfield's album Earth Moving's album notes state that it was recorded using an Atari ST and C-Lab MIDI software.
* In the Paris performance of Jean-Michel Jarré's album Waiting for Cousteau, musicians have attached Atari ST machines with unidentified MIDI software to their keyboards, as could be seen in the TV live show and video recordings.
* White Town's "Your Woman", which reached #1 in the UK singles charts, was created using an Atari ST.
* All the drums MIDI files for The Berzerker's eponymous debut album were written on an Atari.
Never seen a program fill up disk because it just doesn't stop writing? Yes, was easy to delete. Never seen a program delete local files that it has permission to? Sure, but local files were either it's own code, or files in a temporary directory that did no harm. Never seen a program probe hardware that it was perfectly allowed to but somehow manages to bugger things up? Not since DOS days.
Have you ever filled up your Windows so much that it can't find space for swap and hence crashes, and on reboot can't start up, requiring command-line removal of the overgrown files in order to make the system work again? Yes I've seen the disk get filled, no to no space for swap because I always set my swap to a fixed size that is big enough to accommodate 99% of all my usage, and allow it to temporarily expand to triple that if needed.
What about a program that deletes your savegames, or deletes files in your home directories, or modifies the registry in perfectly innocent (but unmonitored) ways that cause buggy programs to run at startup, or destroys your file associations, or just causes Windows to go nuts when you read those entries? Not since I started using NTFS, but back in the FAT/Windows 95/XP days, sure. I just rolled back the registry.
In all honesty I haven't seen these catastrophic crashes that you seem to experience in quite a few years (8 years maybe?). I'm guessing if you are still seeing these it has more to do with the user than the software. Try not overclocking everything beyond it's limits, and making "speed tweaks" that some website says is great that you don't understand fully. Don't open emails about naked girls/singers/goats ever, nor open.exe/.bat/.htc/.com files from anyone. Don't visit the red light scum district on the internet. Don't run everything as admin. Hope that helps.
The original routines to do the color pallette switching did take a considerable amount of cpu and did flicker alot but only when you were trying to do the 64k colors in low res. However there were quite a few games and programs that used that technique to a more limited extent. There was a paint program that did 512 in medium res. Another did 4k. Alternate reality also used 256 colors I believe.
I used to sell (and repair) the atari and amigas way back then. I'm also the author of one of the most popular BBS packages at the time -- especially in the midwest. Second most popular terminal program (solaterm). The only known disk defragment program. The most used YmodemG downloader. Along with a few other utilities (wardialer. Mickeydialer)
I have to say that's a pretty ridiculous question. Because the registry is where all the application settings are supposed to be stored. Funny how an application needs access to change things in the registry when that's what it's designed to do.
Yes, the amiga had 4 channels vs the 3 in the atari, but it was more limited. Not sure where you got the idea the sound chip came from amstrand. It was from yamaha... The same one powering yamahas keyboards at the time.
That and I already said that the atari was capable of displaying 64k colors vs the amigas 4k. The atari was able to change the color palette every 16 pixels giving it complete access to all 64k colors on one screen in low res (the same resolution the amiga did 4k colors) or 256 colors in high res -- that wasnt even touchable by the later amigas.
Those specs were misleading as the graphics chip was able to change palletes every 16 pixels. This gave the ST the ability (coupled with a few other tricks) into supporting any pixel color on any pixel from an extended pallette of 65,536.
Hardly. It was difficult to even boot the machines , which required swapping floppies without the thing crashing. At the time the Amigas were out, Atari's had better graphics (up to 65,536 colors vs Amigas 4096), were more stable, had better sound support, and came standard with midi ports for interfacing to professional sound devices.
The initial releases of GEM were pretty bad compared to todays OS's too. It had no multitasking at all. The GDI had some pretty small resolution constraints. No networking support at all. No process separation at all. One rogue program and the whole system would crash.
Unless I am mistaken, then 2003 revision included C# 2.0, and the 2006 version I linked to includes C# 3.0. Yes, WPF as far as I know is not. But then again, WPF/WinForms is a presentation/windowing library and can use QT or any of the other open source window libraries with it and skip WPF/WinForms if that really is your concern. Missing ADO.NET and ASP.NET are pretty big, but mono implements them anyhow. MySQL has it's ADO.NET provider that should work just fine on any CIL implementation as well.
And of course, you are more than welcome to implement any provider you so choose as well. The System.IO library that is standard in ECMA should be adequate to allow anyone to write whatever database driver necessary, or to implement an ASP.NET alternative.
I think the OP was referring to a small interview done back in September in which Gosling was talking about Oracle, Sun, and Microsoft, and he said that the.NET framework runtime violated a bunch of Sun patents, not C#.
That is because you aren't involved with actually making them, financing them, and trying to make money from them. Anyone that actually is in the business of making stuff or investing cares about RoI and risk, not so much total sales, profit, gross, etc.
Microsoft doesn't/didn't pay Sun for licensing java for c#, they have had some licensing issues with J#, but the whole point of C# was to get away from Suns licenses.
You may not write (or be able to write) C# in notepad, but many can and do quite well. The same can be said about any language in which there already exists a good integrated development environment.
I agree, there is sometimes merit in using open languages. I would suggest starting with ISO/IEC 23270:2006. Oh wait, that's C#.
Actually Avatar is like #14 most profitable film ever when adjusted for inflation. First goes to Gone with the wind by a HUGE margin that it will probably remain there until some really new ground breaking thing happens in the movie industry. Reference here: http://boxofficemojo.com/alltime/adjusted.htm note that if you want to use worldwide adjusted gross, you will find Gone with the wind brought in ~3.2 billion 2010 USD, using simple maths from http://boxofficemojo.com/alltime/world/?pagenum=2&p=.htm shows worldwide gross was approximately double it's domestic (1.6b * 2 =3.2b) and comparing it to the worldwide adjusted Avatar at 2.7b.
If you are using ROI as the metric, then Paranormal Activity stomps the hell out of Avatar (as does Star Wars, and a dozen other movies). One reference here: http://www.cnbc.com/id/39083257?slide=1
Using just about any metric shows Avatar did extremely well, but usually not first.
1080p encoded with mpeg4/h.264 isn't anywhere near 12GB per movie for most movies using typical compression. It's typically more like 1/3rd of that or less.
Netflix HD (720p) additionally is encoded at ~3800kbps, running 1.7GB per hour, or 2.5GB for your typical 1 hour 30 minute movie.
Your estimates from Hulu are extremely low. Netflix HD streams are encoded at ~3800Kbps or 1.7GB per hour. Now recalculate:
That 36GB per month (and I'm assuming its GBytes and not Gbits that the limit is measured in), would translate to ~21 hours of Programming barring other uses, which I understand is unrealistic.
Assuming you only watch 90 hours of programming a month (a ~4.5 weeks a month that translates to 20 hours a week), you went over your cap by 117GB before any "other" traffic (music, web, chat, VoIP (which should be less than VoD)).
For a single person, or a house where there is are two or more, but only one person is stressing the network at once, this would already be a problem (actually it started to be an issue after the first week of the month)...
Slashdot Mirror
Double fail even.
Not only can google's chrome browser decode h.264, but google's youtube site already has 100% of all their videos encoded to it as well. So in short, I can guarantee you that many free browswers already include it, and google has already paid the extremely small licensing fee. As has Microsoft and apple. The only significant hold out, Mozilla, and they are holding back progress on the web (as usual lately).
Fail. Chrome already supports h.264.
Copy paste from google owned youtube:
* Firefox 4 (WebM, Beta available here)
* Google Chrome (WebM and h.264)
* Opera 10.6+ (WebM, Available here)
* Apple Safari (h.264, version 4+)
* Microsoft Internet Explorer 9 (h.264, Beta available here)
* Microsoft Internet Explorer 6, 7, or 8 with Google Chrome Frame installed (Get Google Chrome Frame)
Apparently you don't understand that there are/were already 10x as many iPhones on the market before Android started to take off, but also that iPhones sold more units than Android last quarter. So I wouldn't say google is *owning*. They are far far behind, and they are falling even further behind. That said, #2 in smart phones is still a nice place to be.
It was probably easier to record the WiFi and store it as it is than try and outfit all 50,000 vehicles with enough computing power to be able to actually analyze the signal and pull out the MACs and SSIDs. More like it was just recorded on a tape and brought back to a computer center where the tape was then analyzed in a central location.
I see. We are probably just very lucky out here then that Comcast isn't overselling their local capacity by enough to affect us.
BTW, I do believe that I swapped out my modem for a DOCSIS 3.0 one not too long ago as I think they said that was required for a 50Mb/s connect. I just didn't have to swap it back to the older modem when I downgraded back to 16Mb/s.
Currently where I am, they consider 16Mb/s down, 5Mb/s up as the entry level. Noone has lower than that. All older connections got bumped up to that as it became available, with options for 20,25,30, 50Mb and supposidly 100Mbs as well.
DOCSIS 2.0 supports 30Mb/s upstream PER CHANNEL, and either 42 or 55Mb/s downstream PER CHANNEL. The channels aren't shared between users that I know of.
For example, my Comcast is capped at 16Mb/s (my choice, they also offer 25, 30 and 50Mb service), and my upstream will peak at 30Mb/s in short bursts (First 10MB or so) then settle back to 10Mb/s. A year ago I had completely uncapped service and was able to download at the full 42Mb/s rate (although I could swear it was 52-55Mb/s), and I saturated the line for a week with no issues, no slowdowns, and my neighbors were completely unaffected.
No, I never owned the Falcon, but I did have a 520ST, a 1040ST, and a modded 520STe all of which had 4MB of ram. The original 520ST could display 64,000 colors in the screen at one time through the use of changing the pallette every 16 pixels. At the beginning this took a considerable amount of CPU time, but better techniques were eventually developed, and lower color amount (19200 or 4k) took significantly less CPU time.
Please reference wikipedia, this was pretty well known, although it states only 19200 colors I am fairly certain that it was actually 64,000 (You could display any of 65,536 colors in any pixel location, but because there was only 64,000 pixels on the screen, it's technically just 64000 but you will see references to 64k color mode).
BTW, it was the YF chip that was in the original ST line (which was replaced in the newer models), however, the shifter chip was what gave the ST it's audio prowess. By using the shifter, you could radically change the output from the YF chip, and it was capable of outputting and sampling audio at 128KHz, which was decades ahead of its time. As I said, the YF did only have 3 channels compared to the Amiga's 4, but the amiga had nothing similiar to the shifter in its audio so it was completely dependent on it singular audio chip to do anything -- again, very limited in comparison. It was fairly trivial to take multiple virtual sound channels and software mix them into the 3 hardware channels, and apply shifter effects to each of those. The midi support was unparalleled by either the amiga or PC platforms and you would often see professional musicians using the ST in their sound rooms, or in live performances (I worked right next to a sound studio for a number of years).
From wikipedia:
The ST's low cost, built-in MIDI ports, and fast, low-latency response times made it a favorite with musicians:
* The Fatboy Slim album You've Come A Long Way, Baby has an Atari ST in the large foldout picture of Fatboy Slim's studio.
* Highly acclaimed electronic music artists Mike Paradinas and Luke Vibert started out writing music on Atari STs.
* Mike Oldfield's album Earth Moving's album notes state that it was recorded using an Atari ST and C-Lab MIDI software.
* In the Paris performance of Jean-Michel Jarré's album Waiting for Cousteau, musicians have attached Atari ST machines with unidentified MIDI software to their keyboards, as could be seen in the TV live show and video recordings.
* White Town's "Your Woman", which reached #1 in the UK singles charts, was created using an Atari ST.
* All the drums MIDI files for The Berzerker's eponymous debut album were written on an Atari.
Never seen a program fill up disk because it just doesn't stop writing? Yes, was easy to delete.
Never seen a program delete local files that it has permission to? Sure, but local files were either it's own code, or files in a temporary directory that did no harm.
Never seen a program probe hardware that it was perfectly allowed to but somehow manages to bugger things up? Not since DOS days.
Have you ever filled up your Windows so much that it can't find space for swap and hence crashes, and on reboot can't start up, requiring command-line removal of the overgrown files in order to make the system work again? Yes I've seen the disk get filled, no to no space for swap because I always set my swap to a fixed size that is big enough to accommodate 99% of all my usage, and allow it to temporarily expand to triple that if needed.
What about a program that deletes your savegames, or deletes files in your home directories, or modifies the registry in perfectly innocent (but unmonitored) ways that cause buggy programs to run at startup, or destroys your file associations, or just causes Windows to go nuts when you read those entries? Not since I started using NTFS, but back in the FAT/Windows 95/XP days, sure. I just rolled back the registry.
In all honesty I haven't seen these catastrophic crashes that you seem to experience in quite a few years (8 years maybe?). I'm guessing if you are still seeing these it has more to do with the user than the software. Try not overclocking everything beyond it's limits, and making "speed tweaks" that some website says is great that you don't understand fully. Don't open emails about naked girls/singers/goats ever, nor open .exe/.bat/.htc/.com files from anyone. Don't visit the red light scum district on the internet. Don't run everything as admin. Hope that helps.
The original routines to do the color pallette switching did take a considerable amount of cpu and did flicker alot but only when you were trying to do the 64k colors in low res. However there were quite a few games and programs that used that technique to a more limited extent. There was a paint program that did 512 in medium res. Another did 4k. Alternate reality also used 256 colors I believe.
I used to sell (and repair) the atari and amigas way back then. I'm also the author of one of the most popular BBS packages at the time -- especially in the midwest. Second most popular terminal program (solaterm). The only known disk defragment program. The most used YmodemG downloader. Along with a few other utilities (wardialer. Mickeydialer)
I have to say that's a pretty ridiculous question. Because the registry is where all the application settings are supposed to be stored. Funny how an application needs access to change things in the registry when that's what it's designed to do.
Take your link, then scroll up 3 sections to "Applications" and read it. Although wikipedia says 19200 colors, it went to 64k.
Yes, the amiga had 4 channels vs the 3 in the atari, but it was more limited. Not sure where you got the idea the sound chip came from amstrand. It was from yamaha... The same one powering yamahas keyboards at the time.
That and I already said that the atari was capable of displaying 64k colors vs the amigas 4k. The atari was able to change the color palette every 16 pixels giving it complete access to all 64k colors on one screen in low res (the same resolution the amiga did 4k colors) or 256 colors in high res -- that wasnt even touchable by the later amigas.
Those specs were misleading as the graphics chip was able to change palletes every 16 pixels. This gave the ST the ability (coupled with a few other tricks) into supporting any pixel color on any pixel from an extended pallette of 65,536.
Hardly. It was difficult to even boot the machines , which required swapping floppies without the thing crashing. At the time the Amigas were out, Atari's had better graphics (up to 65,536 colors vs Amigas 4096), were more stable, had better sound support, and came standard with midi ports for interfacing to professional sound devices.
The initial releases of GEM were pretty bad compared to todays OS's too. It had no multitasking at all. The GDI had some pretty small resolution constraints. No networking support at all. No process separation at all. One rogue program and the whole system would crash.
You are right. C# 3.0 spec has also been published here http://download.microsoft.com/download/3/8/8/388e7205-bc10-4226-b2a8-75351c669b09/CSharp%20Language%20Specification.doc, but it wasn't ECMA certified yet.
Thanks for the quote that proves my point, it was regarding the .NET framework, not C#.
Unless I am mistaken, then 2003 revision included C# 2.0, and the 2006 version I linked to includes C# 3.0. Yes, WPF as far as I know is not. But then again, WPF/WinForms is a presentation/windowing library and can use QT or any of the other open source window libraries with it and skip WPF/WinForms if that really is your concern. Missing ADO.NET and ASP.NET are pretty big, but mono implements them anyhow. MySQL has it's ADO.NET provider that should work just fine on any CIL implementation as well.
And of course, you are more than welcome to implement any provider you so choose as well. The System.IO library that is standard in ECMA should be adequate to allow anyone to write whatever database driver necessary, or to implement an ASP.NET alternative.
I think the OP was referring to a small interview done back in September in which Gosling was talking about Oracle, Sun, and Microsoft, and he said that the .NET framework runtime violated a bunch of Sun patents, not C#.
That is because you aren't involved with actually making them, financing them, and trying to make money from them. Anyone that actually is in the business of making stuff or investing cares about RoI and risk, not so much total sales, profit, gross, etc.
Microsoft doesn't/didn't pay Sun for licensing java for c#, they have had some licensing issues with J#, but the whole point of C# was to get away from Suns licenses.
You may not write (or be able to write) C# in notepad, but many can and do quite well. The same can be said about any language in which there already exists a good integrated development environment.
I agree, there is sometimes merit in using open languages. I would suggest starting with ISO/IEC 23270:2006. Oh wait, that's C#.
Actually Avatar is like #14 most profitable film ever when adjusted for inflation. First goes to Gone with the wind by a HUGE margin that it will probably remain there until some really new ground breaking thing happens in the movie industry. Reference here: http://boxofficemojo.com/alltime/adjusted.htm note that if you want to use worldwide adjusted gross, you will find Gone with the wind brought in ~3.2 billion 2010 USD, using simple maths from http://boxofficemojo.com/alltime/world/?pagenum=2&p=.htm shows worldwide gross was approximately double it's domestic (1.6b * 2 =3.2b) and comparing it to the worldwide adjusted Avatar at 2.7b.
If you are using ROI as the metric, then Paranormal Activity stomps the hell out of Avatar (as does Star Wars, and a dozen other movies). One reference here: http://www.cnbc.com/id/39083257?slide=1
Using just about any metric shows Avatar did extremely well, but usually not first.
Our electric company charges less per KWh as usage increases.
1080p encoded with mpeg4/h.264 isn't anywhere near 12GB per movie for most movies using typical compression. It's typically more like 1/3rd of that or less.
Netflix HD (720p) additionally is encoded at ~3800kbps, running 1.7GB per hour, or 2.5GB for your typical 1 hour 30 minute movie.
Your estimates from Hulu are extremely low. Netflix HD streams are encoded at ~3800Kbps or 1.7GB per hour. Now recalculate:
That 36GB per month (and I'm assuming its GBytes and not Gbits that the limit is measured in), would translate to ~21 hours of Programming barring other uses, which I understand is unrealistic.
Assuming you only watch 90 hours of programming a month (a ~4.5 weeks a month that translates to 20 hours a week), you went over your cap by 117GB before any "other" traffic (music, web, chat, VoIP (which should be less than VoD)).
For a single person, or a house where there is are two or more, but only one person is stressing the network at once, this would already be a problem (actually it started to be an issue after the first week of the month) ...