Ed Raket wrote:
Programming is the key, remember when programs where written in assembler? programs flew on a 386... never mind a 486 DX! Grafic cards where a joke these days. lazy programming coused huge liberaries for simple instructions, software bloated hardware specs for decades... if you can have a live cd of a complete (windows like) os distro only < 3Mb in sise, If they can make a 64k demo that last for 10 mins, and filles you with joy! Maybe we should forget the hardware specs, and learn to code again. A Pi has SO MUCH potencial with the right programs, that maybe we should relearn to code again. Maybe we should not WANT to use a 150Kb lib for a 3Kb instruction... Please tel me if im wrong, but i think it's time for a new way of thinking and coding. In the future we just cant use a ferrari to for groseries, we have to use a suzuki economicly to make sence. otherwise we keep falling behind on specs...
my 2 cnts, from a coding NooB
I cut my teeth on the early 8bit CPUs, and spent time in engineering the 128 and 512KB Macinstosh CPU's, given these were floppy based and had limited RAM and nowhere to have as a cache/scratch area the performance for a 16bit single tasking OS was usable still today, but compared to Windows 3, it was so far ahead, that it sparked MS OS's need/trend for ever more powerful CPUs and more memory in order to account for the CPU running TWO
operating systems, DOS and Windows. Windows was, in effect a DOS application.
When you start to develop and write device level components (memory, I/O, CPU et-al) in a high level language and then continue to write the OS in a similar high level language the best compilers on earth won't cut the code as tight as an engineer who knows the nuts and bolts of the hardware, registers and OS, not to mention which language is best for the job in hand and works with that.
I'm excited to see people, kids and us old hands, rediscover what we can achieve with a light OS, fairly handy CPU, limited RAM and tightly crafted code. That is NO excuse for undocumented code though!
As for the ARM devices coming from China, we're trying to compare raspberries with strawberries. The two go together well, but satisfy different pallets.
The RPi is aimed to get people 'hands on' with the code and close to the hardware, to inspire, spark the passion and deliver on imagination that comes from writing you own code, driving your hardware. The units coming from China with a pre-installed Android OS are ideal as set top boxes, or TV web browsers, a cordless keyboard/track pad, sit back and research the web from your armchair without a £500 web browser frying your thighs.
Now, if you took and Arm embedded CPU and integrated it with a MS Kinect so you could have gestures but not touch screen, well, wow, that I'd wouldn't still be sat here writing this! Providing the performance was good overall and the solution was stable (OS/software) the name or detail would be academic, to simply have a small box held on the back of the LCD with velcro, or on top of my AV switcher/amp must appeal to a lot of people, not for heavy web access, but for light web use, connection to the home media server and even to hosted office based apps and email. None of which need many horses to deliver.
I think both platforms can survive, the packaged, more expensive solution for the TV web boxes and the open and open source RPi with a choice of OS and that can be expanded and developed in many different ways, many only as limited as the users imagination. What is great is the sheer volumes that have already been shipped. I'm wondering what the total volume of C64, VIC20 and Beebs etc were each year. Oh, not forgetting the ZX Spectrum!
It will be interesting to see how many of us here have more than one RPi by the end of the year, indeed, how many of us will have three or more?