I'm glad you share my humble opinion.
I don't see clearly the link between the availability of a library for a given platform and the new structure for the libraries on the Arduino 1.5 specifications.
Some boards —as Teensy and Digispark— add plug-ins to the main Arduino IDE. How to proceed with the installation of the libraries included on a plug-in? What will happen when a plug-in provides a header specific to its platform when the header is already on the top folder —like the Servo example with servo.h?
Dealing with conditional pre-processing statement to deal with the different platforms / architectures is a nightmare I've been dealing with when I've developed the embedXcode
template for Xcode. The template currently supports Arduino, chipKIT MPIDE, Digispark, LaunchPad Energia, Maple, Teensy and Wiring.
I rather prefer today's de facto
approach with one folder per platform / architecture, with everything related to it: cores, variants, firmwares, libraries, system, bootloader.
See below the examples of
• Arduino 1.5.3 with avr and sam
• Energia 0101E009
with msp430 and lm4f, a fork of Arduino for Texas Instruments' LaunchPads
I'd appreciate some feedback from the Arduino team.