Skip to main content

javascript and long strings

I have not been a fan of NodeJS but recently I have been writing a lot of JavaScript. As a result of this bias I found myself passing on perl, python and ruby in order to "template" a SQL script in favor of NodeJS. (I suppose if I had to use a single callback I would have a different opinion but I did like the utility nature of the experience.)

Installing node and the necessary dependencies was pretty simple:

# install NVM (nodejs version manager)
curl | sh

# install nodejs
nvm install 0.8.16

# I'm not certaint if this is required but I USE and set this version of nodejs as default.
nvm use 0.8.16
nvm alias default 0.8.16

# install the mustache template library 
npm install mustache

# install the sprintf library because it's simple
npm install sprintf

That's it. The rest of the project was my code. Initially I was looking for some "javascript long string" help in google and I did find some useful examples, however, some did not work with NodeJS. Like

  1. var string = (<r><![CDATA[ 
  3.    The text string goes here.  Since this is a XML CDATA section, 
  4.    stuff like <> work fine too, even if definitely invalid XML.  
  6. ]]></r>).toString();
(snipped from here)

This example might work in a browser but it does not seem to work in NodeJS. As an aside there was a  CoffeeScript version that I liked but I was not going to install CoffeeScript as a dependency for this little trinket.

Ultimately I implemented this:

function hereDoc(f) {
return f.toString().
(/^[^\/]+\/\*!?/, '').
(/\*\/[^\/]+$/, '');
You can have here-documents like this:
var tennysonQuote = hereDoc(function() {/*!
Theirs not to make reply,
Theirs not to reason why,
Theirs but to do and die

and it worked great. I put the rest of the bits together and I'm generating SQL like I had hoped. By the time I have to run this script again I hope to clean it up and automate it so I never have to run it again.


Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…