Go ahead, you can do it. Login and vote now.
By bloid
via arcanesentiment.blogspot.com
Published: Jul 10 2008 / 07:22
In any significant program, a great deal of code is spent on two activities that have very little intrinsic interest: I/O and error handling. This makes them good targets for language design. If a language can make these two areas easier, it can remove a significant part of the accidental complexity of programs. Conversely, a language in which either is difficult is a language in which effort is wasted on uninteresting problems.
SaveShareSend
Tags: other languages
-
Quick Tip: Invoke A URL From SQL Server Agent
-
Implementing SNMP4J Decoder for Apache MINA
-
jBlogMvc : part 2 Editing, Deleting, Paging Posts and Rss feeds
-
Scalable Real-Time Web Architecture, Part 2: A Live Graph with Orbited, MorbidQ, and js.io
-
Factor Web Framework Example
-
Parallel Extensions are part of the .NET Framework 4.0
Comments
paul_houle replied ago:
There's an interesting and controversial concept here, the idea of I/O operations that read a whole file.
"Big" languages like Java and C# require the creation of several objects to access a file, and require access to be done in a streaming mode. PHP and arc, on the other hand, let you do something like file_get_contents()
Streaming mode access is certainly better than whole-file access when files are large, but I often end up finding problems in C# and Java programs where people make mistakes with the more complex API's.
Voters For This Link (8)
Voters Against This Link (0)