The Register
At last, somebody is implementing this idea! Always seems strange that people used to moan about the hard time that musicians got; or they'd grumble about how exploitative & commercial pop music had become. These two apparently oxymoronic grumbles alone should convince us that something is wrong in the music biz, but still we buy. Then technology comes along to work in our favour. The exploitative industry lashes out indiscriminately - suing kids in the name of musicians, for god's sake! Not even a trace of irony. Finally, the model starts to evolve. After all, it should be about the music: those who make it being rewarded by those who choose to listen to it.
Tuesday, February 03, 2004
Friday, November 28, 2003
Working In A Wired World
Working In A Wired World:
“Here is the very heart and soul of the matter of leadership: If you seek to lead, invest 50% of your time (attention) leading yourself — your own purpose, ethics, principles, motivation, conduct. Invest at least 20% leading those with authority over you, and 15% leading your peers ... Use the remainder to induce those you “work for” to understand and practice the theory ... If you don’t understand that you should be working for your mislabeled “subordinates,” then you know nothing of leadership. You know only tyranny ... Lead yourself, lead your superiors, lead your peers, and free your people to do the same. All else is trivial.”
Dee Hock Founder of Visa
“Here is the very heart and soul of the matter of leadership: If you seek to lead, invest 50% of your time (attention) leading yourself — your own purpose, ethics, principles, motivation, conduct. Invest at least 20% leading those with authority over you, and 15% leading your peers ... Use the remainder to induce those you “work for” to understand and practice the theory ... If you don’t understand that you should be working for your mislabeled “subordinates,” then you know nothing of leadership. You know only tyranny ... Lead yourself, lead your superiors, lead your peers, and free your people to do the same. All else is trivial.”
Dee Hock Founder of Visa
Saturday, November 22, 2003
Wired News: Record Label Sings New Tune
Now this is more like it! The recording studio of the future...
Now this is more like it! The recording studio of the future...
Monday, November 17, 2003
ZDNet UK - Insight - Lifting the lid on Longhorn
The desktop is where Microsoft rule. They didn't get there through robust, flexible systems, or efficient code. They got there through ease of use - both to programmers and end-users. It's like an inverse telecoms model: they own the 'last mile' but not the bulk of the infrastructure. But the last mile is where the money is, and it's where change is most expensive, effective and visible (nobody gives a poo if the transatlantic backbone doubles in size, or if Unix Oses are 5x faster and 2x cheaper, except for sys admins, and most of them don't want the desktop config hassle on 5000 desktops).
They want the internet to be their new OS. It's quite clever the way they're going about it - by exploiting the desktop peer model. As long as the guy at the other end has the same handset make as me, we can do all sorts of clever & fun things, regardless of what's in the middle.
Where they may come unstuck is the underlying presumption that everyone will want to upgrade their handset. But even in that instance, they could give it away (but not opensource it). Could you imagine if M$ gave away the next client version of their OS? Which Intel users *wouldn't* have it on their desktop? They could still make their lucrative money out of bolt-on modules: want video IM? Rent it. Want peer-to-peer music sharing? Rent it.
I particularly liked this quote:-
'The XML programming model is separate from Windows and is not packaged with desktop systems, but WinFX will be integrated into Longhorn, according to Microsoft. Once that happens, "it will be like Microsoft taking one hand from behind its back in its boxing match with Java companies," said Rob Helm, an analyst at Directions on Microsoft. "Potentially every PC will ship .Net-ready, which will make it much more interesting" for application developers, he added.'
A fine example of M$ suppressing end-user expectations. Mac OS has always shipped with an excellent dev environment. Also, OSX supports XML-SOAP natively - you can make SOAP calls from Applescript!
I also like the ClickOnce approach: rather than just the OS bugging you with updates every time you look at the machine, all of your applications will do it. Again, MacOS can do this already - many apps, even trivial ones, have a 'Check for Update' option on the menu. It's just a SOAP call after all. The key is discretion: OSX has it, M$ controls it and rents it to the highest bidder.
The desktop is where Microsoft rule. They didn't get there through robust, flexible systems, or efficient code. They got there through ease of use - both to programmers and end-users. It's like an inverse telecoms model: they own the 'last mile' but not the bulk of the infrastructure. But the last mile is where the money is, and it's where change is most expensive, effective and visible (nobody gives a poo if the transatlantic backbone doubles in size, or if Unix Oses are 5x faster and 2x cheaper, except for sys admins, and most of them don't want the desktop config hassle on 5000 desktops).
They want the internet to be their new OS. It's quite clever the way they're going about it - by exploiting the desktop peer model. As long as the guy at the other end has the same handset make as me, we can do all sorts of clever & fun things, regardless of what's in the middle.
Where they may come unstuck is the underlying presumption that everyone will want to upgrade their handset. But even in that instance, they could give it away (but not opensource it). Could you imagine if M$ gave away the next client version of their OS? Which Intel users *wouldn't* have it on their desktop? They could still make their lucrative money out of bolt-on modules: want video IM? Rent it. Want peer-to-peer music sharing? Rent it.
I particularly liked this quote:-
'The XML programming model is separate from Windows and is not packaged with desktop systems, but WinFX will be integrated into Longhorn, according to Microsoft. Once that happens, "it will be like Microsoft taking one hand from behind its back in its boxing match with Java companies," said Rob Helm, an analyst at Directions on Microsoft. "Potentially every PC will ship .Net-ready, which will make it much more interesting" for application developers, he added.'
A fine example of M$ suppressing end-user expectations. Mac OS has always shipped with an excellent dev environment. Also, OSX supports XML-SOAP natively - you can make SOAP calls from Applescript!
I also like the ClickOnce approach: rather than just the OS bugging you with updates every time you look at the machine, all of your applications will do it. Again, MacOS can do this already - many apps, even trivial ones, have a 'Check for Update' option on the menu. It's just a SOAP call after all. The key is discretion: OSX has it, M$ controls it and rents it to the highest bidder.
Saturday, November 15, 2003
SecurityFocus HOME Infocus: Banking Scam Revealed
Interesting article (well, cyber-anthropologically speaking) on the real, human effects of spam, as discovered by a bunch of investigative hackers.
Interesting article (well, cyber-anthropologically speaking) on the real, human effects of spam, as discovered by a bunch of investigative hackers.
Wednesday, November 05, 2003
ZDNet UK - News - Media industry quietly co-opts P2P
Finally, some firms get the right idea. Just as when Records and tapes came out, the companies moaned & sued, then adapted & cornered the new market. The difference this time is that we are dealing with pure IP - intellectual property in infinitely replicable (digital) form. In a distribution system that is virtually perfect. So what will distributors add? How will they control a frictionless medium?
Finally, some firms get the right idea. Just as when Records and tapes came out, the companies moaned & sued, then adapted & cornered the new market. The difference this time is that we are dealing with pure IP - intellectual property in infinitely replicable (digital) form. In a distribution system that is virtually perfect. So what will distributors add? How will they control a frictionless medium?
Saturday, November 01, 2003
How To Become A Hacker
Above doc is in a similar vein to the original Hacker's Manifesto, albeit more instructive and a little tongue in cheek.
Above doc is in a similar vein to the original Hacker's Manifesto, albeit more instructive and a little tongue in cheek.
Friday, October 31, 2003
Slashdot | Microsoft's new CLI
Microsoft going back to the command line. It's the 3 ages of technology again, isn't it?
Stage 1: a prototype, effectively - barely fulfilling design criteria, and certainly not robustly.
Stage 2: over-design. They've got the hang of it, they've got a market, so they pack it full of features until it becomes cumbersome.
Stage 3: just right - removal of extraneous features.
To a unix-head stage 3 is the command line. I'm no unix head, but I do appreciate the elegant simplicity of Unix: everything is in a file. So, all the settings are in a file, which you can tweak either through some pretty GUI screens with checkboxes and tabs, or through the CLI by editing the file directly. Non-Unix people say, "but unix is so user-unfriendly. Who wants a command line? It's so indecipherable." My response, as one who is not a techie but has a sincere respect for techies and technology, is simply if you're playing with settings you should explicitly know what they do.
The other advantage of a file-based system (as in, you tweak files directly, rather than use wizards that give no indication of which file you're tweaking), is that you can make changes easily reversible by the use of comments - something woefully lacking in GUIs. Finally, it also means you just need Telnet to tweak any online server in the world. None of this Remote Windows Desktop foolishness. Mind you, whether this degree of tweakability is healthy in an OS with Windows' security record is questionable.
Microsoft going back to the command line. It's the 3 ages of technology again, isn't it?
Stage 1: a prototype, effectively - barely fulfilling design criteria, and certainly not robustly.
Stage 2: over-design. They've got the hang of it, they've got a market, so they pack it full of features until it becomes cumbersome.
Stage 3: just right - removal of extraneous features.
To a unix-head stage 3 is the command line. I'm no unix head, but I do appreciate the elegant simplicity of Unix: everything is in a file. So, all the settings are in a file, which you can tweak either through some pretty GUI screens with checkboxes and tabs, or through the CLI by editing the file directly. Non-Unix people say, "but unix is so user-unfriendly. Who wants a command line? It's so indecipherable." My response, as one who is not a techie but has a sincere respect for techies and technology, is simply if you're playing with settings you should explicitly know what they do.
The other advantage of a file-based system (as in, you tweak files directly, rather than use wizards that give no indication of which file you're tweaking), is that you can make changes easily reversible by the use of comments - something woefully lacking in GUIs. Finally, it also means you just need Telnet to tweak any online server in the world. None of this Remote Windows Desktop foolishness. Mind you, whether this degree of tweakability is healthy in an OS with Windows' security record is questionable.
Monday, October 13, 2003
silicon.com - ITU 03 - Microsoft wants to make Wi-Fi hotspots more secure
I would say 'about bloody time', but instead I have to say that network security should stay on the network, not as part of some OS somewhere.
Part of the problem with the microsoft OS paradigm is that the OS is treated with such a degree of profundity, rather than the basic enabler between software and hardware that it should be. Most non-technical people actually believe the OS is the graphical bit, the user interface. And this suits Microsoft perfectly. Even those banes of M$ strategy, Linux users, tend to play into their hands by playing up the OS wars, rather than changing the argument and putting OSes in their place as merely the bit of software that gets hardware to talk to software.
If there's a problem with the network (eg. it's not secure), it should stay a network problem and the network kit vendors should solve their problem. But software is cheaper than hardware, and evolves faster - that's why we have it - so invariably the hardware people leave it to the software people to set their standards and pick the most viable one to implement in hardware. Unfortunately, this leads to a self-perpetuating lead for the prominent OS vendor, since, more often than not, the most viable standard is the most popular, as implemented in the most popular OS, rather than the best technology.
I would say 'about bloody time', but instead I have to say that network security should stay on the network, not as part of some OS somewhere.
Part of the problem with the microsoft OS paradigm is that the OS is treated with such a degree of profundity, rather than the basic enabler between software and hardware that it should be. Most non-technical people actually believe the OS is the graphical bit, the user interface. And this suits Microsoft perfectly. Even those banes of M$ strategy, Linux users, tend to play into their hands by playing up the OS wars, rather than changing the argument and putting OSes in their place as merely the bit of software that gets hardware to talk to software.
If there's a problem with the network (eg. it's not secure), it should stay a network problem and the network kit vendors should solve their problem. But software is cheaper than hardware, and evolves faster - that's why we have it - so invariably the hardware people leave it to the software people to set their standards and pick the most viable one to implement in hardware. Unfortunately, this leads to a self-perpetuating lead for the prominent OS vendor, since, more often than not, the most viable standard is the most popular, as implemented in the most popular OS, rather than the best technology.
Sunday, September 28, 2003
The Register, 26/08/2003: Microsoft: a threat to global IT and job security?
V interesting article speculating about a piece of security research slating Microsoft, for which the author lost his job. Interesting discussion - esp. about possible remedies.
V interesting article speculating about a piece of security research slating Microsoft, for which the author lost his job. Interesting discussion - esp. about possible remedies.
Subscribe to:
Posts (Atom)