You may be right about the GPU for most people. For my applications, generally headless low-bandwidth network server and data acquisition stuff- the GPU is not a selling point. A system for $35 including ethernet, USB, I2C, SPI, 256 MB and running Linux on 2 W power, and with a growing user base and dev community, the Pi is still the best deal in town even with no GPU.babbage wrote:So, the strongest selling point of the Pi is it's GPU chip, which is only usable currently under a very small set of circumstances. The general answer is 'write your own, cos we're not'.
I think that's a little unfair. The Broadcom guys have no X Windows experience and there are plenty in the comunity that do. As long as they answer questions about what's going on under the hood when we get stuck then I think that's fair enough.babbage wrote:So, the strongest selling point of the Pi is it's GPU chip, which is only usable currently under a very small set of circumstances. The general answer is 'write your own, cos we're not'.
You may find that once you're out of school, your first job may not be primarily doing software implementation for precisely the reason you cited - lack of experience. Implementation should not be confused with mere programming - the former is part of a well-planned and executed software engineering process, and the latter is just ... well, not. Your first job may actually be in quality assurance (QA), where you would be tasked with conducting testing of your organization's software/hardware. You can help perform the same function with the X software and, while you may not comprehend how the code works (at least in detail), you should be able to understand how the software is supposed to work at a higher level of functionality.DBit wrote:I will be following it's progress closely and contributing what I can.
Users browsing this forum: klricks and 40 guests