Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

some typos; some cleaning

  • Loading branch information...
commit 749e35bef7985b788b5ec113decc931492cce294 1 parent 928701c
Zbigniew Lukasiak authored
Showing with 18 additions and 19 deletions.
  1. +18 −19 webnano_article.html
View
37 webnano_article.html
@@ -63,7 +63,7 @@
the clutter of repeatable parameter passing - I believe that putting object into
their natural scope will fix a lot of the widely recognized <a
href="http://jjnapiorkowski.vox.com/library/post/does-anyone-else-hate-the-stash.html">problems
- with the Catalyst stash and data passed through it</a>. In procedural
+with the Catalyst stash and data passed through it</a>. In procedural
programming it is not a controversial rule to put your variable declarations
into the narrowest block that encompasses it's usage - the same should be true
for objects. Sure using the same controller to serve multiple request is a bit
@@ -86,9 +86,9 @@
The reason why WebNano is the fastest framework is probably that it just does
not do much. WebNano is really small, in it's 'lib' directory it currently has
-just 232 lines of code (as reported by sloccount) and <a
- href="http://deps.cpantesters.org/?module=WebNano;perl=latest">minimal
- dependencies</a>. There are CPAN libraries covering all corners of web
+just 232 lines of code (as reported by <a href="http://www.dwheeler.com/sloccount/">sloccount</a>)
+and <a href="http://deps.cpantesters.org/?module=WebNano;perl=latest">minimal
+dependencies</a>. There are CPAN libraries covering all corners of web
application programming - what the framework needs to do is provide a basic
structure and get out of the way.
<p>
@@ -106,9 +106,9 @@
similar way for all kinds of programs and the library that does that job does
not need to know anything about the web stuff. At CPAN there are such
libraries. For my limited experiments <a
- href="http://search.cpan.org/dist/MooseX-SimpleConfig/">MooseX::SimpleConfig</a>
+href="http://search.cpan.org/dist/MooseX-SimpleConfig/">MooseX::SimpleConfig</a>
was very convenient, for more complex needs <a
- href="http://search.cpan.org/dist/Bread-Board/">Bread::Board</a> seems like
+href="http://search.cpan.org/dist/Bread-Board/">Bread::Board</a> seems like
a good choice. This initialization layer needs to know how to create all the
objects used by the application - but you don't need any kind of WebNano adapter
for them.
@@ -128,7 +128,7 @@
complex when you try to write a dispatching model that would work for every
possible application. I prefer to write a simple dispatcher covering only the
most popular dispatching scenarios - and let the users of my framework write
-their own specialized dispatching code for ther specialized controllers. With
+their own specialized dispatching code for their specialized controllers. With
WebNano this is possible because these specialized dispatchers don't interfere
with each other.
<p>
@@ -139,7 +139,7 @@
I like the way Catalyst structures your web related code into controller
classes - this is a step forward from the <a
- href="http://search.cpan.org/~markstos/CGI-Application-4.31/lib/CGI/Application.pm">CGI::Application</a>
+href="http://search.cpan.org/~markstos/CGI-Application-4.31/lib/CGI/Application.pm">CGI::Application</a>
way of packing everything into one class. I don't have any hard data to
support that - but the granularity of packing a few related pages into one
controller class feels just about right. It gives room for expansion by adding
@@ -153,7 +153,7 @@
app. It passes all the original tests and could be completely empty if I did
not want to test the overriding of the inherited parts. I have seen many times
a need for such behaviour, from 'branding' websites, through SAAS to reusable
-intrenet tools - most of the time this was solved by copying the code.
+intranet tools - most of the time this was solved by copying the code.
Inheritance has it's problems but it would fit well this ad-hoc reuse and it is
still better then 'cut and paste' programming. The key point here is that you
need to override much more than just methods. The experiment I am doing with
@@ -199,12 +199,11 @@
<h2>Conclusions</h2>
It is early to say if WebNano will live to the promise of facilitating the
development of web application components. There is a first component at CPAN:
-<a
- href="http://search.cpan.org/dist/WebNano-Controller-CRUD/">WebNano::Controller::CRUD</a>.
+<a href="http://search.cpan.org/dist/WebNano-Controller-CRUD/">WebNano::Controller::CRUD</a>.
It still bears the label 'experimental' - but I used it in <a
- href="https://github.com/zby/Nblog">Nblog</a>. When I compare it to my
+href="https://github.com/zby/Nblog">Nblog</a>. When I compare it to my
first similar product <a
- href="http://search.cpan.org/~wreis/Catalyst-Example-InstantCRUD-0.037/lib/Catalyst/Example/Controller/InstantCRUD.pm">Catalyst::Example::Controller::InstantCRUD</a>,
+href="http://search.cpan.org/~wreis/Catalyst-Example-InstantCRUD-0.037/lib/Catalyst/Example/Controller/InstantCRUD.pm">Catalyst::Example::Controller::InstantCRUD</a>,
there aren't many differences. As predictable the methods have one less parameter
(<code>$c</code>), and I think it's inheritable templates are
nice at deployment - you don't need to write your own templates to see it working,
@@ -221,15 +220,15 @@
<p>
Recently I discovered that many of my design choices are echoed in the
publications by the Google testing guru <a
- href="http://misko.hevery.com/">Miško Hevery</a>. My point of departure
+href="http://misko.hevery.com/">Miško Hevery</a>. My point of departure
for the considerations above were general rules - like decoupling,
encapsulation etc - his concern is testability - but the <a
- href="http://misko.hevery.com/2008/08/21/where-have-all-the-singletons-gone/">resulting
- design</a> is remarkably similar. There is a lot of good articles at his
+href="http://misko.hevery.com/2008/08/21/where-have-all-the-singletons-gone/">resulting
+design</a> is remarkably similar. There is a lot of good articles at his
blog, some were similar to <a
- href="http://misko.hevery.com/2009/04/15/managing-object-lifetimes/">what I
- already had thought over</a>, <a
- href="http://misko.hevery.com/2009/04/08/how-to-do-everything-wrong-with-servlets/">others</a>
+href="http://misko.hevery.com/2009/04/15/managing-object-lifetimes/">what I
+already had thought over</a>, <a
+href="http://misko.hevery.com/2009/04/08/how-to-do-everything-wrong-with-servlets/">others</a>
were completely new to me. I recommend them all.
</body>
</html>
Please sign in to comment.
Something went wrong with that request. Please try again.