Re: [OT] node.js and express

[Bec C]

You're not alone Greg. It's like going back to spaghetti but everyone
around me doesn't agree. Hey just a few years ago I could create a a whole
web app in 10 minutes but now I have to go and get tens of packages in the
dependency chain and glue them together and become a plumber to make it all
work. Sure it can be done but is it an efficient use of my time?! Hey do
you want VS to do the setup and boring stuff for you? Nah I'd rather waste
my time and do it all myself manually. Yay... not! The web is dead to me.
Sorry a bit upset today

On Mon, Nov 21, 2016 at 9:01 AM, Greg Keogh  wrote:

> Folks, although I've been insulting JavaScript for years, I have always
> liked scripting. I decided to install node.js and run the tutorials on how
> to make a REST service. There are lots of tutorials, many of them
> contradictory or incomplete, or the documented steps don't work as
> expected. After confusion in the npm command when you need to *init* or
> *install* or use --save I got the express package installed. Then the
> express.cmd file which generates the app skeleton is not found, but later
> found two folders deep under .bin, and when you run it you don't know which
> folder should receive its output.
>
> I finished up with what might be a skeleton JS app web server comprising
> 403 files in 98 folders (and I haven't even installed all the packages they
> mention). It seems to have installed a *views* folder even though I have
> no "views" in a rest service, containing .jade files which I've never heard
> of, but searches reveal it's another JS library for templates. There a
> multiple templates libraries available and it looks like jade is now being
> phased out. I eventually run "node myserver.js" and it says it's listening
> on http://:::8081 but it's not responding and tcpview indicates that
> nothing is listening on that port.
>
> So after 3 hours of installing, reading, generating, fiddling and futzing
> I finished up with a gigantic morass of files and folders that don't even
> serve "hello world". I thought VS2015 might have JS project support, but it
> doesn't seem to (am I missing something?). Do I have to install another
> product like Code (or similar) to get a JS project IDE?
>
> I'm afraid all this has simply hardended my opinion that the whole
> JavaScipt culture and ecosystem is a lunatic asylum.
>
> *Greg K*
>

Re: [OT] node.js and express

[David Connors]

I think they use "Javascript" with cookies to serve you ads on teh
internets.

On Mon, 21 Nov 2016 at 11:01 Stephen Price 
wrote:

> What are you doing?! JavaScript hasn't passed the "Tested by Greg Keogh"
> certification. You shouldn't be in there touching that stuff!
>
> You've only yourself to blame. Don't poke the angry bear.
>
> On 21 Nov. 2016 6:01 am, Greg Keogh  wrote:
>
> Folks, although I've been insulting JavaScript for years, I have always
> liked scripting. I decided to install node.js and run the tutorials on how
> to make a REST service. There are lots of tutorials, many of them
> contradictory or incomplete, or the documented steps don't work as
> expected. After confusion in the npm command when you need to *init* or
> *install* or use --save I got the express package installed. Then the
> express.cmd file which generates the app skeleton is not found, but later
> found two folders deep under .bin, and when you run it you don't know which
> folder should receive its output.
>
> I finished up with what might be a skeleton JS app web server comprising
> 403 files in 98 folders (and I haven't even installed all the packages they
> mention). It seems to have installed a *views* folder even though I have
> no "views" in a rest service, containing .jade files which I've never heard
> of, but searches reveal it's another JS library for templates. There a
> multiple templates libraries available and it looks like jade is now being
> phased out. I eventually run "node myserver.js" and it says it's listening
> on http://:::8081 but it's not responding and tcpview indicates that
> nothing is listening on that port.
>
> So after 3 hours of installing, reading, generating, fiddling and futzing
> I finished up with a gigantic morass of files and folders that don't even
> serve "hello world". I thought VS2015 might have JS project support, but it
> doesn't seem to (am I missing something?). Do I have to install another
> product like Code (or similar) to get a JS project IDE?
>
> I'm afraid all this has simply hardended my opinion that the whole
> JavaScipt culture and ecosystem is a lunatic asylum.
>
> *Greg K*
>
>
> --
David Connors
da...@connors.com | @davidconnors | LinkedIn | +61 417 189 363

Re: [OT] node.js and express

[Stephen Price]

What are you doing?! JavaScript hasn't passed the "Tested by Greg Keogh" 
certification. You shouldn't be in there touching that stuff!

You've only yourself to blame. Don't poke the angry bear.

On 21 Nov. 2016 6:01 am, Greg Keogh  wrote:
Folks, although I've been insulting JavaScript for years, I have always liked 
scripting. I decided to install node.js and run the tutorials on how to make a 
REST service. There are lots of tutorials, many of them contradictory or 
incomplete, or the documented steps don't work as expected. After confusion in 
the npm command when you need to init or install or use --save I got the 
express package installed. Then the express.cmd file which generates the app 
skeleton is not found, but later found two folders deep under .bin, and when 
you run it you don't know which folder should receive its output.

I finished up with what might be a skeleton JS app web server comprising 403 
files in 98 folders (and I haven't even installed all the packages they 
mention). It seems to have installed a views folder even though I have no 
"views" in a rest service, containing .jade files which I've never heard of, 
but searches reveal it's another JS library for templates. There a multiple 
templates libraries available and it looks like jade is now being phased out. I 
eventually run "node myserver.js" and it says it's listening on http://:::8081 
but it's not responding and tcpview indicates that nothing is listening on that 
port.

So after 3 hours of installing, reading, generating, fiddling and futzing I 
finished up with a gigantic morass of files and folders that don't even serve 
"hello world". I thought VS2015 might have JS project support, but it doesn't 
seem to (am I missing something?). Do I have to install another product like 
Code (or similar) to get a JS project IDE?

I'm afraid all this has simply hardended my opinion that the whole JavaScipt 
culture and ecosystem is a lunatic asylum.

Greg K

Re: [OT] node.js and express

[Craig van Nieuwkerk]

If you are doing a Javascript centric project (Node, Angular) you will be
better suited using Visual Studio Code.

Craig

On Mon, Nov 21, 2016 at 9:01 AM, Greg Keogh  wrote:

> Folks, although I've been insulting JavaScript for years, I have always
> liked scripting. I decided to install node.js and run the tutorials on how
> to make a REST service. There are lots of tutorials, many of them
> contradictory or incomplete, or the documented steps don't work as
> expected. After confusion in the npm command when you need to *init* or
> *install* or use --save I got the express package installed. Then the
> express.cmd file which generates the app skeleton is not found, but later
> found two folders deep under .bin, and when you run it you don't know which
> folder should receive its output.
>
> I finished up with what might be a skeleton JS app web server comprising
> 403 files in 98 folders (and I haven't even installed all the packages they
> mention). It seems to have installed a *views* folder even though I have
> no "views" in a rest service, containing .jade files which I've never heard
> of, but searches reveal it's another JS library for templates. There a
> multiple templates libraries available and it looks like jade is now being
> phased out. I eventually run "node myserver.js" and it says it's listening
> on http://:::8081 but it's not responding and tcpview indicates that
> nothing is listening on that port.
>
> So after 3 hours of installing, reading, generating, fiddling and futzing
> I finished up with a gigantic morass of files and folders that don't even
> serve "hello world". I thought VS2015 might have JS project support, but it
> doesn't seem to (am I missing something?). Do I have to install another
> product like Code (or similar) to get a JS project IDE?
>
> I'm afraid all this has simply hardended my opinion that the whole
> JavaScipt culture and ecosystem is a lunatic asylum.
>
> *Greg K*
>

[OT] node.js and express

[Greg Keogh]

Folks, although I've been insulting JavaScript for years, I have always
liked scripting. I decided to install node.js and run the tutorials on how
to make a REST service. There are lots of tutorials, many of them
contradictory or incomplete, or the documented steps don't work as
expected. After confusion in the npm command when you need to *init* or
*install* or use --save I got the express package installed. Then the
express.cmd file which generates the app skeleton is not found, but later
found two folders deep under .bin, and when you run it you don't know which
folder should receive its output.

I finished up with what might be a skeleton JS app web server comprising
403 files in 98 folders (and I haven't even installed all the packages they
mention). It seems to have installed a *views* folder even though I have no
"views" in a rest service, containing .jade files which I've never heard
of, but searches reveal it's another JS library for templates. There a
multiple templates libraries available and it looks like jade is now being
phased out. I eventually run "node myserver.js" and it says it's listening
on http://:::8081 but it's not responding and tcpview indicates that
nothing is listening on that port.

So after 3 hours of installing, reading, generating, fiddling and futzing I
finished up with a gigantic morass of files and folders that don't even
serve "hello world". I thought VS2015 might have JS project support, but it
doesn't seem to (am I missing something?). Do I have to install another
product like Code (or similar) to get a JS project IDE?

I'm afraid all this has simply hardended my opinion that the whole
JavaScipt culture and ecosystem is a lunatic asylum.

*Greg K*