This issue was originally filed by demis.b...@gmail.com
Introducing an interim Path type to manipulate string paths is an un-necessary friction given the dart:io File and Directory classes only work with strings. It's also a good show-case on how over-typing SDK API's are less re-usable, composable and overall harder to work with.
We should remove the Path type from the SDK given that better and redundant options (also made by the Dart Team) exist including pathos: http://pub.dartlang.org/packages/pathos
Ideally Dart SDK APIs should have a minimal and flexible API surface with special care taken when converting what is commonly else-where a string API behind types which as a side-effect can create friction and reduce interoperability. IOTW there should be a clear and visible benefit to typing string APIs in the SDK. When they exist they should be balanced against the ease-of-use and imposed friction compared with the existing node.js APIs:
It's always an option for external higher-level libs to provide a typed API layer over it, that way their use is isolated to those who prefer and see value in it.
Original discussion: https://groups.google.com/a/dartlang.org/d/topic/misc/H7XG_KB6oZQ/discussion
Added Area-IO label.
Path is now deprecated, will be removed at the 11th of August.
An email will be sent out later today or tomorrow with instructions.
This comment was originally written by demis.b...@gmail.com
Cool! If there's any functionality in Path that you find pathos lacks, please don't hesitate to throw patches at me to get that moved over.
Added this to the M6 milestone.
The Path class was removed from dart:io in https://code.google.com/p/dart/source/detail?r=26181.
Added Fixed label.
Removed Area-IO label.
Added Area-Library, library-io labels.