use a browser on a Pi anyway? If you need to do graphical work just use a regular computer.
My Pi is running happily under my desk 24/7 and hasn't been connected to a display once.

We will not migrate everything to Pascal (Lazarus) as the executable with GUI on it are gigantic for a minimalist environment. Just for that.We have applications here Access Control, POS, financial control, bluetooth marketing, all made in PB. And we are having to migrate eg POS for Free Pascal (Lazarus), because we have an important client who wants to adopt the Raspberry Pi in its 135 checkouts (for energy savings, final cost, etc. - the sheet that he did convinced us - and are to exchange all PCs, as today's are older almost all Celerons)
The "look at my new toy" factor?Shield wrote:It isn't even really about the performance. The real question is: Why would you want to
use a browser on a Pi anyway? If you need to do graphical work just use a regular computer.
You made an incorrect assumption. PB outputs asm directly, and goes straight to an assembler, not another compiler. (FASM or NASM, depending on the o/s.)bbanelli wrote:Pardon me if I am being extremely stupid and ignorant on this one, but since PB actually uses gcc, could this potentially work?
http://hertaville.com/2013/07/19/cross- ... pberry-pi/
Oh! Thx for the explanation.Tenaja wrote:You made an incorrect assumption. PB outputs asm directly, and goes straight to an assembler, not another compiler. (FASM or NASM, depending on the o/s.)bbanelli wrote:Pardon me if I am being extremely stupid and ignorant on this one, but since PB actually uses gcc, could this potentially work?
http://hertaville.com/2013/07/19/cross- ... pberry-pi/
...and that is exactly why the PB dev team has said it will ever output ARM asm. Too much work, probably.
One could always hope. The biggest benefit would be the optimizations. The biggest drawback would be the slow compile times.Danilo wrote:They added a JavaScript target (SpiderBasic), so maybe they will do a C target one day.