Sawadee: sadly, once again, I find your comments both misleading and it really seems you've not made an effort to read what's been said.
I said I would not comment further on the issue right now, and what's the first thing you ask me?
As for the browser situation being "boggling", it shouldn't be - since the situation has been extensively documented - in the "RISC OS Browser Issue" and many other places. Unfortunate? Yes. Boggling? No.
"Pooling resources". What resources, precisely? I've already pointed out in the past that for example the NetSurf team make their own contribution to GCCSDK/Unixlib which is a crucial part of any port. And vice-versa, Netsurf probably would not have been possible (or at least very difficult) without my work.
Java. Why do people go on about Sun's JVM and licensing every time this is mentioned. Kaffe is a comprehensive version, and is free. More importantly, there's been a command line version on my website for around 2 years. The work now to complete it is relatively small.
Mart: precisely why wouldn't a firefox port have the "latest standards" and be continued to maintained? I really think you haven't read "The RISC OS browser issue" or you'd be saying something a bit different.