10MB, 10MB, 30MBm, who knows, half of it could be comments! How many SLOC (source lines of code) is it? This is the most fundamental metric that can be used to measure the size of an application. can anyone run it through a counter?
They can already do it... just type the following into google search:-)
"find these lyrics" site:http://lyrics.astraweb.com/
I do agree with you however, they could start to analyse and index audio and video and make it searchable. I'm sure they have thought about it.
Watch this space for more acquisitions in this area.
They don't want to own the world, just own access to it:-)
They will provide an access to large amounts of data and digital assets and information. Don't think music is the end. They already demistyfied GIS with google maps. Now anyone can do GIS!
They will also distribute access tools to enable consumers to access this info. Either by creating the original access point as they do with search, or just by providing APIs for others to implement the access point, and then they will make money with network effects.
Watch them deliver service based APIs for every n-tier layer across their products, presentation/ui logic (maps), application logic (froogle), business logic (search) and data access (blogger).
G
Mainframe -> Client/Server
- The thin client is dead!
Client/Server -> Browser
- The thick client is dead! The client side o/s is dead!
- everyone decides to support Java, flash, plug-ins.. just so we can preserve thick client capabilities.:-)
thin client browser -> thick client browser
- the thin client is dead!
give it another 5-10 years and something else will come along and pronounce the thick client dead again. guaranteed.
Come on people, it is all about horses for courses. Choose the right technology for the application you are creating. Nothing is dead, it is all in the mix. Client, server and network technology is moving to increase capability, bandwidth etc all the time, so we will choose the right combination of technologies based on the app functionality, the deployment environment, the user's capabilities, the engineering team's capabilties and so on...
Cheers
El Gordo
I can't see how this could be patented, can you explain?
Even if it had the merit, I also believe there is a lot of prior-art.
1. Liberate Technologies (www.liberate.com) had developed a browser based on the Mozilla codebase back in the mid 90's. This had a number of extensions of which one was a js object called netRequest which is similar to AJAX's XMLHttpRequest. Along with dynamic table cells, this enabled you to develop primitive AJAX applications. Many of these applications are running today on closed interactive TV systems based in the UK and the Netherlands.
2. [Fat]Client/Server applications rely on the client making requests to the server to carry out a transaction or to request new datasets etc. The result of the transaction would be processed by the client and the interface updated accordingly. This core mechanism is no different to what AJAX achieves.
Slashdot Mirror
Dude, get the software localised for US English! It makes no sense not supporting it in your first version.
10MB, 10MB, 30MBm, who knows, half of it could be comments! How many SLOC (source lines of code) is it? This is the most fundamental metric that can be used to measure the size of an application. can anyone run it through a counter?
it's new if you haven't seen it before...
They can already do it... just type the following into google search :-)
"find these lyrics" site:http://lyrics.astraweb.com/
I do agree with you however, they could start to analyse and index audio and video and make it searchable. I'm sure they have thought about it.
Watch this space for more acquisitions in this area.
They don't want to own the world, just own access to it :-)
They will provide an access to large amounts of data and digital assets and information. Don't think music is the end. They already demistyfied GIS with google maps. Now anyone can do GIS!
They will also distribute access tools to enable consumers to access this info. Either by creating the original access point as they do with search, or just by providing APIs for others to implement the access point, and then they will make money with network effects.
Watch them deliver service based APIs for every n-tier layer across their products, presentation/ui logic (maps), application logic (froogle), business logic (search) and data access (blogger).
G
A raw or a frozen egg?
Sorry, AJAX is way too late, Java and the network computer already killed the o/s. :-)
Mainframe -> Client/Server - The thin client is dead! Client/Server -> Browser - The thick client is dead! The client side o/s is dead! - everyone decides to support Java, flash, plug-ins.. just so we can preserve thick client capabilities. :-)
thin client browser -> thick client browser
- the thin client is dead!
give it another 5-10 years and something else will come along and pronounce the thick client dead again. guaranteed.
Come on people, it is all about horses for courses. Choose the right technology for the application you are creating. Nothing is dead, it is all in the mix. Client, server and network technology is moving to increase capability, bandwidth etc all the time, so we will choose the right combination of technologies based on the app functionality, the deployment environment, the user's capabilities, the engineering team's capabilties and so on...
Cheers
El Gordo
I can't see how this could be patented, can you explain?
Even if it had the merit, I also believe there is a lot of prior-art.
1. Liberate Technologies (www.liberate.com) had developed a browser based on the Mozilla codebase back in the mid 90's. This had a number of extensions of which one was a js object called netRequest which is similar to AJAX's XMLHttpRequest. Along with dynamic table cells, this enabled you to develop primitive AJAX applications. Many of these applications are running today on closed interactive TV systems based in the UK and the Netherlands.
2. [Fat]Client/Server applications rely on the client making requests to the server to carry out a transaction or to request new datasets etc. The result of the transaction would be processed by the client and the interface updated accordingly. This core mechanism is no different to what AJAX achieves.
Cheers
El Gordo