Friday, February 28, 2014

Adventures in Node.js - Using NPM on Windows

The following still needs to be more carefully verified but I'm making this public now to help someone and hopefully do just that....

We'll call this installment #2 of "Adventures in Node.js" even though my previous Node entry didn't have this in mind.

I'm short on time today so I can't elaborate so much but in short:

One time on your machine:

  1. Install Python 2.7 and add the python.exe folder location to your PATH environment variable.
  2. Either 1 or 2 depending on your setup:
    1. If you don't have Visual Studio 2008 installed (which provides vcbuild.exe):
      1. install the Windows SDK (to provide vcbuild.exe). Good reference at then ensure that the path to vcbuild.exe is in your PATH environment variable
      2. npm install -g --msvs_version=2012
    2. If you DO have VS installed, run the following to setup your environment properly:
      1. Add the path to vcbuild.exe to your PATH environment variable then run the following
      2. npm install -g node-gyp
      3. node-gyp configure --msvs_version=2012
      4. node-gyp build
      5. npm install -g --msvs_version=2012

Once for your project:
  1. npm install
Now your project should be ready for you to use npm in general. My purpose today was to check out grunt, grunt-cli and grunt-devtools thanks to recommendations from Paul Irish both at Google I/O 2013 and a couple weeks ago at the Chrome Dev Summit.

Now that I have npm working it was as simple as (from
  1. npm install -g grunt-cli
  2. npm install grunt --save-dev
  3. npm install grunt-devtools
Next I try to setup and use Yeoman (another framework he suggested that relies on Grunt).

Tuesday, February 25, 2014

How We Can Begin to Fix the Government and Your Responsibility and Right as a Juror

One way we have to begin to get our government back in check 100% legally, without any violence

WARNING: If you continue reading, you will likely ruin your ability to serve on any jury that is well managed OR you will forfeit your ability to use this knowledge without being guilty of perjury. This is no joke and you better research this yourself because I'm not responsible for your actions, your interpretation of this information, or any consequences. On the other hand, it is YOUR RESPONSIBILITY as an American to know this.


Scroll down to read....

Pushed down so you must scroll to read and won't be exposed without that effort......

*Jury Nullification*: Ultimately, it's the jurors RIGHT and RESPONSIBILITY to make a guilty judgement not ONLY based on the facts and law, but ALSO on what you think is right; thereby judging the law itself as well as the "crime". It is a mechanism very intentionally built into the core of our legal system.

This is not my interpretation either, this is our founding forefathers design:

John Adams wrote, “_It is not only the juror’s right, but his duty to find the verdict according to his own best understanding, judgment and conscience, though in direct opposition to the instruction of the court._”

Thomas Jefferson wrote, “_I consider trial by jury as the only anchor yet imagined by man by which a government can be held to the principles of its constitution._”

This video and the following link help explain but beware because jury selection includes questions worded very carefully to eliminate people who understand their full responsibility and power as a juror and those questions are typically worded in a way that if you use jury nullification, you will likely find yourself guilty of perjury. This is because the people who run the legal system as as susceptible to this power as criminals and your ignorance of it gives them tyrannical power. As long as they can keep you off a jury, they can manipulate the legal system rather than have it manipulated by the people who should be doing so, "THE PEOPLE".

The only real way to address this abuse is spread the knowledge so far that they cannot reasonably assemble an otherwise fair jury without allowing jurors who know their full responsibilities and rights as a juror.

Tuesday, February 11, 2014

How to KILL Performance in Chrome 34 dev channel with one CSS rule

I just accidentally discovered a sure-fire way to KILL performance in Chrome 34 dev. I mean, going from a decent 30-60 fps to 0.25-1 fps.

See link below for sample code.

On a page with a good number of input elements (like a management dashboard I'm working with), apply "border: dotted 1px rgba(200, 200, 200, 0.9);" to input elements. It's the combination of the INPUT, element, border-style:dotted and border-color:rgba(). Remove the dotted (use solid) or remove the alpha channel and use rgb() instead and performance returns.

Even after the page is fully rendered and I scroll a few times, which causes things to smooth out a bit, dev-tools is rendered useless.

A sample page can be found here: