Ah, this is great, just down the road. I should be able to make it this year, this is nearly as accessible from the East Midlands as the Motorcycle Museum was. I've got no excuse not to be there! I shall probably use the unsignposted back way to the M40 junction from Rugby, which involves a few country roads but will be easier than M42/M40 or getting on the M40 from the A46 south of Coventry. If anyone else is interested in that route, I can provide directions!
Why do we need a faster Iyonix? What software is there that will take advantage of the extra speed? It is true that a faster processor might encourage the development of a media player for Iyonix (which probably can't happen because of licencing issues anyway), and Firefox would perhaps run a bit better, but apart from that, I can't think of anything I use that would benefit much from slightly more speed. I do a fair bit of digital photography, and faster display of JPEGS would be nice, but the main thing that that needs is a faster graphics card. I think the next jump in processor speed needs to be a big one, up to something like 2GHz or more, and accompanied by applications that use the extra power to make upgrading worthwhile.
All in all this is a very silly argument! Peter, if you have a good reason why Paul's tutorial is a bad thing, why not tell us. If you have laready told Paul, he clearly did not see it as a problem If it is wrong and will cause problems, we might then be able to make an informed decision, or perhaps Paul might be able to correct any errors.
I see nothing wrong with people working together, and I'm sure Paul's motives were trying to help Firefox users to get the software working. Developeers need to be prepared to work together is thebplatform is to survive.
The problem is that decent programmers are in short supply. I mean everywhere, not just in the RISC OS world. This means that they tend to be busy professionally, and probably aren't too keen to spend what little spare time they have doing even more programming. There are other things in life. At least that's my excuse.
So we ought to be thankful to professionals like Peter that are prepared to spend their spare time in this way. It takes a lot of dedication after a day at work to come home and do more of the same with little or no reward except the satisfaction of achievement.
It is also true that some programmers have a clause in their employment contract that states that any work that they do, even in their spare time, is the property of the company that trained and employs them. I had this myself at one time. We probably don't want any of our software base to be owned by organisations that might be unsympathetic to the platform.