- About Scala
- In the Enterprise
- Scala Community
- Language Research
- In the Press
- The Scala Team
- Scala's Prehistory
- Contact Us
- Learning Scala
- Tour of Scala
- Scala API
- Setup & Getting Started
- Programming Guides
- Other Guides
- Code Examples
- Scala Developers
what is scala.io.File?
Tue, 2009-09-08, 01:20
I have read this thread
with great interest. At the beginning. Then I have confused: what is this
Not being involved in the language development process I don't feel rights to
join that discussion - [scala-user] is my place :-) Please, excuse me for
opening parallel (in some sense) thread. I'll be happy to catch raw Scala
users to that discussion.
About my confusion. From my humble user's point of view, any attempts to
generalize too different islands (regular file, pipes, network sockets, unix
sockets, attributes related to different operation systems, acl/rbac,
symlinks, cryptography, ram, REST, ... continue, please) result in hardly-
Probably more simple way (in learning, using and maintaining) is to keep all
these different ... well, things with their own rights (attributes,
operations). Just make these islands friendly to Scala collections and create
a way to communicate (streams).
But, well, a common view to different artefacts is a good thing! Aha-aha, I
see. And agree. But here we have a *view*. Last one (say, URI) can be added
at current context by hand, or, probably, some most common views may be added
to the library. But, at any case, all these views are based on self-contained,
clean and light artefacts.
I dream scala.io.File to be a file.
(you see, my English is ugly, but I hope you will believe me: I have not any
claims in my mind - just sharing opinion)
(Paul, revert reversion!)