Programing in raspberry pi 2

[Geospan1]

What limits would you have programming on a raspberry pi2 (with all the peripherals you need of course).1)software limitations,and 2)hardware limitations.

[manikyath]

well, the two obvious things will be that you're on an ARM platform, meaning you cant use/make anything x86 or x86_64. and offcourse that you're limited to a gigabyte of ram (actually only about 850MB because of an addressing issue, its a whole another #ramgate i guess)

EDIT: should also mention that without powered usb hubs you're limited to a total of 5 watts for the pi, and its usb peripherals.

[Geospan1]

well, the two obvious things will be that you're on an ARM platform, meaning you cant use/make anything x86 or x86_64. and offcourse that you're limited to a gigabyte of ram (actually only about 850MB because of an addressing issue, its a whole another #ramgate i guess)

EDIT: should also mention that without powered usb hubs you're limited to a total of 5 watts for the pi, and its usb peripherals.

That's good,thank you.

[Azgoth 2]

Aside from what @manikyath mentioned, there aren't a whole lot of limitations.  Most all of the major programming languages will run on the Pi 2.  The GNU Compiler Compilarion comes pre-installed on Raspbian, Python has been ported to it (and runs very well), and some others I can't recall offhand right now.  Most of your limitations would be based on the available system resources: 4 core 900 MHz (base speed, extremely easily overclockable) ARM CPU, ~1GB of RAM, and the only permanent storage is a microSD card you insert (plus any USB storage).

 

But, as far as actually writing code or learning to code or whatever, you should be able to do most of what you need in most languages.  For some, like Python, you can even copy code to and from other machines and run it without issue (some compiled languages might be a different story, but I don't know enough about that use case to say definitively).

[manikyath]

4 core 900 MHz (base speed, extremely easily overclockable) ARM CPU.

if you'e gonna OC it, *please* get a heatsink for it. i'll be looking at my findings once i get my hands on a heatsink that fits the pi. (stock intel cooler didnt fit )

[Azgoth 2]

if you'e gonna OC it, *please* get a heatsink for it. i'll be looking at my findings once i get my hands on a heatsink that fits the pi. (stock intel cooler didnt fit )

Well, for general use, you can overclock it at the lowest setting (100MHz boost) and not have to worry, except for the nebulous "wear and tear" factor.  But if you plan on keeping it under a high CPU load for extended periods of time or overclocking at one of the higher settings, then yes, a heat sink is absolutely a must.  Heat sinks for the Pi are pretty dang cheap, too, so there's really no reason not to use one anyways if you can get one.

[manikyath]

Well, for general use, you can overclock it at the lowest setting (100MHz boost) and not have to worry, except for the nebulous "wear and tear" factor.  But if you plan on keeping it under a high CPU load for extended periods of time or overclocking at one of the higher settings, then yes, a heat sink is absolutely a must.  Heat sinks for the Pi are pretty dang cheap, too, so there's really no reason not to use one anyways if you can get one.

well, to give you an example, to compile all emulators in emulationstation/retropie it takes approx. 12 hours of 100% usage on the pi 2.

 

bettery safe than sorry

[Azgoth 2]

well, to give you an example, to compile all emulators in emulationstation/retropie it takes approx. 12 hours of 100% usage on the pi 2.

 

bettery safe than sorry

Oh, well, yeah, you should be using a heatsink for that.  That falls under "high CPU load for a long time", obviously

[LukeTim]

The biggest limitation on what you can program on the Raspberry Pi 2 will be your own imagination.