I'll side with the "there is no such thing as "ARM PROGRAMMING"" people. Embedded programming principles span architectures, ARM chip peripherals are vendor-dependent (so being familiar with "NXP ARM peripherals and libraries" is not very applicable to "Atmel ARM chips"), AND "ARM" has become so broad a term as to not be very useful (Programming an STM CM0 embedded chip being much different from programming programming a multi-core 64bit ARM with Mali Graphics accelerator (and the latter being divided up into applications, os, libraries, and bare metal...))
Totally agree. I'm a C programmer who avoids assembly like the plague (sorry, don't want to relive my C5000 DSP assembly programming days), so it's all basically the same to me. You basically just end up learning peripherals -- both when you're switching between ARM MCUs, and when you're switching between ARM and 8/16 bit architectures.
And actually, I think ARM is easier to learn C programming on than most 8-bit architectures -- especially when using ARM MCUs with really simplistic peripherals.
Other than the AVR stuff, (nice core, but really shitty chips), most 8-bit MCUs have quite a few peculiarities that come up rather quickly when writing C. I just started playing around with Silicon Labs' new EFM8 MCUs (which uses the ancient 8051 architecture) and about 15 minutes into programming, I was out of RAM. "Huh? How?" Oh, because on 8051, you only get 256
bytes of fast IRAM -- everything else must be explicitly placed in XRAM (at least when compiling with Keil's C51 compiler, which I assume must be good, because it's $2200).
On ARM, you just write C code and compile it and it just works, and it doesn't do anything screwy.
Now, onto which ARM microcontroller you should learn. Anyone who's read my posts knows I'm a hardcore Freescale Kinetis fanboy -- I love the peripherals, and my pocketbook loves the prices. Kinetis Design Studio is beautiful, and Kinetis SDK gives you the same low-level control you get with CMSIS, without being nearly as verbose. And MQX is a really wonderful RTOS that's highly underrated.
...Having said all that, ironically, while a lot of people give NXP shit for not being a friendly platform for beginners, I think NXP's Cortex-M0 stuff is a great "first platform" for people looking to get into ARM. Having never touched their stuff before, it took me all of 15 minutes to get Code Red (err, "LPCXpresso IDE") downloaded, installed, and configured. In another 15 minutes, I imported their peripheral library and wrote a SysTick-based blinky project from scratch that I was debugging off-chip to an LPC1114 (in a DIP package!). 15 minutes after that, I got the UART printing "hello, world." Granted, I know my way around ARM MCUs, but there was not a single "gotcha" -- which is rare, even in this day and age! I didn't even have to crack open the datasheet or reference manual, or read the peripheral library documentation to figure out how to use it (you gotta love peripheral libraries that take more time to learn how to use then just writing your own HAL from scratch -- "wait, do I call gpio_init() before I pass the config structure to gpio_set_config()? What is gpio_start()? Does the GPIO library control the peripheral clock gating, or do I have to use the timer library to do that?")
While I'd never use NXP's stuff in a commercial project (shitty pricing), I think I'd probably recommend it to a beginner if asked.