![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
I've been reading about JavaScript as a counterpoint to what I'm learning about Perl. It helps me to chew over what I've just learned by learning how another language approaches or cannot approach an issue.
The biggest lesson I've had so far is that JavaScript is shiny but Perl gets work done. I could play with something like this JavaScript page for a good while, making it go from color blocks to blue letters to orange binary to lines to green crosses over and over. JavaScript lets you run tiny applications inside a user's web browser without having to make calls back to the server. Once it loads, it's on.
( Yeah, it's only gonna get geekier from here... )
These dual paths of learning will let me make exactly the presentation system I desire for you, my readers. While I may be giving myself a long-term project, I feel I am ready for it. I tell people "Tolstoy made his own pencils, so why shouldn't I build my own writing tools?" I don't even like Tolstoy, although I appreciate that "War and Peace" shrank by 31 pages after the Soviets took five characters out of Cyrillic and dumped the excess tvyordi znak at the ends of most words.
I see the process of making all of my equipment as the foundation of my craft. I am not a victim of publishers or interlopers unless I know I can get a specific reward from the transaction. I will understand each step of the process intimately. I have built and configured the computers which let me type and store that work, installed the operating systems and keep them in good order, and now I am learning the languages which can process my words so that I don't waste time doing it manually. I write about each step that I take, thus fueling the creative process perpetually.
As I take that time and continue to document as I learn, I will be able to type up crap from anyway, send it to my machinery and let my scripts make it available to you. I will fix the problems and understand when my own tools are obsolete.
-should I even bother capitalizing the middle S? Dante
The biggest lesson I've had so far is that JavaScript is shiny but Perl gets work done. I could play with something like this JavaScript page for a good while, making it go from color blocks to blue letters to orange binary to lines to green crosses over and over. JavaScript lets you run tiny applications inside a user's web browser without having to make calls back to the server. Once it loads, it's on.
( Yeah, it's only gonna get geekier from here... )
These dual paths of learning will let me make exactly the presentation system I desire for you, my readers. While I may be giving myself a long-term project, I feel I am ready for it. I tell people "Tolstoy made his own pencils, so why shouldn't I build my own writing tools?" I don't even like Tolstoy, although I appreciate that "War and Peace" shrank by 31 pages after the Soviets took five characters out of Cyrillic and dumped the excess tvyordi znak at the ends of most words.
I see the process of making all of my equipment as the foundation of my craft. I am not a victim of publishers or interlopers unless I know I can get a specific reward from the transaction. I will understand each step of the process intimately. I have built and configured the computers which let me type and store that work, installed the operating systems and keep them in good order, and now I am learning the languages which can process my words so that I don't waste time doing it manually. I write about each step that I take, thus fueling the creative process perpetually.
As I take that time and continue to document as I learn, I will be able to type up crap from anyway, send it to my machinery and let my scripts make it available to you. I will fix the problems and understand when my own tools are obsolete.
-should I even bother capitalizing the middle S? Dante
