Web 에서 배운 것들


pimon.com 이 왜 웹 애플리케이션인지 정확히 설명해주는 부분.
하지만, 아쉽게도 아래의 글은 웹의 가장 중요한 단점을 간과하고 있다
: 데이터의 소유인이 내가 아니라는 점. 서버가 다운 되었을 때 아무 것도 할 수 없다는 것.

일주일에 두세번씩 싸이에서 “지금은 사용자가 많이 서비스를 이용할 수 없습니다”라는
메세지를 보며 가슴아파할 때 마다 느끼는 점이다.

아래 포스트는 아마 지난 몇 달동안 읽어본 포스트 중에서 최고의 포스트인 것 같다.

What have we learned from the Web?

First and foremost, we have learned that it isn’t enough for something to be
possible. It must be easy, open and flexible
. The web predates HTML of course,
but until the advent of HTTP and HTML, it didn’t really explode. Why? The answer,
succinctly, is empowerment. Once HTML and HTTP arrived, more people could play
more easily. The solutions were not necessarily optimal from the point of view of
performance or even robustness. They were optimal from the point of view of ease of
getting started. In short, they were drop-dead simple. Many people point out the
deficiencies of HTML, especially because of the sloppiness of its grammar…

The lesson is that simplicity and flexibility beat optimization and power in a
world where connectivity is key.
There is a second lesson which is key. Applications
need to be constructed out of coarse-grained components that can be dynamically
loaded rather than single large monolithic blocks. In the HTML world, these
components are pages. In the applications world in general, however, this lesson
applies. The reason for this is simple. The application starts more quickly, only
consumes the resources it really needs, and most importantly can be dynamically
loaded off of the net. Why is this so important?

It is important because of deployment. Applications that can be dynamically
loaded in from a central place don’t require some massive, complex and difficult
installation process onto clients’ machines
. Note that Java per se doesn’t give
one this. It is easy, as anyone who has built a large and complex Java application can
testify, to build one, which requires literally hundreds of classes to run. That is
monolithic. HTML had the serendipitous effect of forcing application designs to partition
the application. To repeat, the lesson is that applications should be loaded in coarse-
grained chunks.


답글 남기기

아래 항목을 채우거나 오른쪽 아이콘 중 하나를 클릭하여 로그 인 하세요:

WordPress.com 로고

WordPress.com의 계정을 사용하여 댓글을 남깁니다. 로그아웃 / 변경 )

Twitter 사진

Twitter의 계정을 사용하여 댓글을 남깁니다. 로그아웃 / 변경 )

Facebook 사진

Facebook의 계정을 사용하여 댓글을 남깁니다. 로그아웃 / 변경 )

Google+ photo

Google+의 계정을 사용하여 댓글을 남깁니다. 로그아웃 / 변경 )

%s에 연결하는 중