Drobe :: The archives
About Drobe | Contact | RSS | Twitter | Tech docs | Downloads | BBC Micro

Reply to thread

Julian wrote>"The reason I supported the Omega, was that in its finished state it would have offered a hell lot more processing power than any standard PC workstation (through the use of user-programmable FPGA-space)"

As it was never finished that would be a safe bet wouldn't it ? ;)

As to a hell of a lot of processing power the *actual* Omega out there in processing terms is not much better than a RISC PC (other than faster memory access and disk access). The Iyonix would have more processing power (and it too has an FPGA - albeit a simple one) - so why not support it?

Julian wrote>"The only way we can hope to get back to a state where RISC OS might be considered a fully-featured desktop/workstation computing platform, is by utilising the vast amount of open-source code out there and stick RISC OS frontends on it"

While I would have sympathy with that viewpoint it doesn't really address the glaring problem inherent in this. Most OSS code is pure C or C++ it is often written to be portable (in other words *not* optimised for any particular platform). The end result of this is the more complex OSS code when converted for the RISC OS environment is (sad to say) bloated and slow. While Firefox is a good advertisement of what *can* be acchieved it, subjectively, it appears slower to me than say Origano 2 (which itself is pretty slow even on an Iyonix).

The fastest, most useable applications on RISC OS tend to be a mix of C or BASIC and ARM Assembler. OSS from the Linux or BSD camps won't be that - it'll usually be pure C/C++ and designed for machines that run somewhat faster processors, have more RAM and less resource constraints.

Given the choice would you prefer to run Firefox on a RISC OS machine or a PC ? In short side by side people would (I believe) opt for running such Open Source code on a PC running Windows or Linux over a RISC OS machine running the same app.

The best solutions IMHO are either (a). Faster RISC OS machines that would allow "slow complex" code like that to be run effectively or (b). More "native" RISC OS application development - that makes use of OSS where possible but is optimised for ARM RISC OS use where required.

 is a RISC OS UserAMS on 20/08/06 5:21PM
[ Reply | Permalink | Report ]

Please login before posting a comment. Use the form on the right to do so or create a free account.

Search the archives

Today's featured article

  • Sharing files over a network with NFS
    RISC OS, Windows and Linux getting friendly [Updated]
     28 comments, latest by sa110 on 19/11/04 7:48PM. Published: 15 Sep 2004

  • Random article

  • UPP shares porting tools
    Sign up and be a serial porter
     17 comments, latest by jonix on 3/2/03 9:45AM. Published: 28 Jan 2003

  • Useful links

    News and media:

    Top developers:
    RISCOS LtdRISC OS OpenMW SoftwareR-CompAdvantage SixVirtualAcorn

    CJE MicrosAPDLCastlea4X-AmpleLiquid SiliconWebmonster


    RISCOS.org.ukRISCOS.orgRISCOS.infoFilebaseChris Why's Acorn/RISC OS collectionNetSurf

    Non-RISC OS:
    The RegisterThe InquirerApple InsiderBBC NewsSky NewsGoogle Newsxkcddiodesign

    © 1999-2009 The Drobe Team. Some rights reserved, click here for more information
    Powered by MiniDrobeCMS, based on J4U | Statistics
    "It burns my eyes!"
    Page generated in 0.0835 seconds.