Rupert Murdoch vs. The Web
Are the fights that matter just the ones between giant companies? Doesn't the health of the Net and the Web matter more than any commercial battles?
These questions came to mind when I read How Murdoch Can Really Hurt Google And Shift The Balance Of Power In Search in TechCrunch recently. In that piece Mike Arrington supported Jason Calacanis' suggestion that Murdoch stick it to Google by cutting an exclusive search deal with rival search engine Bing. Even Jay Rosen took the same side. (Though perhaps in jest.)
Find more background at TechCrunch, from Dan Kennedy and in this New York Times piece, which makes the necessary distinction between wars among businesses on one hand, and what's good for the Net on the other. On the matter of the latter, the Times sources Craig Newmark, but still frames Craig's remarks in support of Google's side. In other words, the Times is still covering vendor sports here.
Defending the Web and the Net from collateral damage are Tim O'Reilly, Chris Messina, Anil Dash — and Dave Winer, whose whole oeuvre is thick with warnings about subordinating the Web and the Net to narrow personal or corporate interests. (He also offers positive advice: "Ask not what the Web can do for you, ask what you can do for the Web".)
But most of us aren't listening. We're Pompeians, Krakatoans, Montserratans, building cities and tilling farms on the slopes of active volcanoes. Always suckers for stories, we'd rather take sides in wars between competing volcanoes than build civilization on more flat and solid ground where there's room enough for everybody.
Google and Bing are both volcanoes. Both grace the Web's landscape with lots of fresh and fertile ground. They are good to have in many ways. But they are not the Earth below. They are not what gives us gravity.
They also create enormous dependencies. Much as I appreciate them, I am especially concerned about all the free graces we enjoy (maps, docs, books, etc.), thanks to Google's abundant success in the advertising business. What happens when that business goes away? Or what happens when we wake up and realize that we don't need search engines?
Let's face it: search engines are excellent kluges, invented to deal with a flaw in the Web's original design: the lack of an easy way to make sense of its many directory paths. Since everything to the right of the first single / in every URL comprises a giant disorganized haystack, ways were found to locate needles there. Those ways, however, are extremely complex and now entirely in private hands. One can look at this and accept it, or come up with a sane public solution. This is what free and open source developers are good at. I'm betting that one or more of ya'll will come up with a solution eventually.
Meanwhile, we need to get our priorities straight.
Here's one of mine. Soon as Rupert Murdoch and company do a deal to keep their "content" out of anybody's search engine, I'll cease renewing my subscriptions to the Wall Street Journal — both online and in print.
[Later...] Just added some more context over here.
Doc Searls is Senior Editor of Linux Journal
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide