Listen to this week's podcast (February 6, 2012) psd.js psd.js is the beginnings of a Photoshop PSD parser in JavaScript! Right now it only essentially extracts metadata information - such as image size and layer information - but it's off to a good start! You can even drag and drop ...

(no podcast this week - Boo! Check back next week) Chrome for Android Google has just released a beta of Chrome for Android, which is available for those running Android Ice Cream Sandwich (aka "the 1%"). This isn't JavaScript-specific news per se, but it is HUGE news for web devs ...

  Node.js is by far the most popular platform for creating JavaScript applications. According to a recent infographic published by Statista, more than 49% of app developers frequently utilize Node.js, making it the platform of choice for mobile app development. That is because of the Node.js advantages.  This article will discuss the benefits of Node.js […]

The post Full guide on drawbacks and benefits of Node.js for making the perfect choice for your business appeared first on 404 Tech Support.

Looking to hire as an independent contractor a highly experienced backend software engineer with extensive experience with Node.js, and preferably with MongoDB as well. Familiarity with GCP would be a plus. This is a part-time, remote contract that will probably be for a minimum of three months and possibly a good bit longer. You must be a true high senior or expert level developer with extensive Node.js experience. A qualified candidate will most likely have at least ten years of solid software development experience. If you are not the right person but know somebody who might be, please feel free to have them contact me. Thank you.

Shim was developed within the Boston Globe’s media lab as a way to study how Web sites look on various devices and browsers. A laptop intercepts all wifi traffic – this is redirected to a custom node.js server – which inserts a javascript, or “shim,” at the head of each web page that is visited. Read the rest...

Node.js employs an event-driven architecture and a non-blocking I/O model, and it provides some blindingly fast performance to some types of data-intensive Web apps. It is about JavaScript on the server side. LinkedIn, Yahoo and eBay are among ardent Node.js users, and none other than Microsoft has discussed end-to-end JavaScript coverage on its Azure cloud. Read the rest...

Since the introduction of Node.js by Ryan Dahl at the European JSConf on 8 November 2009, it has seen wide usage across the tech industry. Companies such as Netflix, Uber, and LinkedIn give credibility to the claim that Node.js can withstand a high amount of traffic and concurrency. Armed with basic knowledge, beginner and intermediate developers of Node.js struggle with many things: “It’s just a runtime!” “It has event loops!

Node.js 14 is available now. We wanted to get more context and details about the state of Node, and why developers should care about Node.js 14. We talked with Bethany Griggs, Node.js Technical Steering Committee member and Open-source Engineer at IBM, to find out more. 

Bethany has been a Node Core Collaborator for over two years. She contributes to the open-source Node.js runtime and is a member of the Node.js Release Working Group where she is involved with auditing commits for the long-term support (LTS) release lines and the creation of releases. 

In this tutorial, you will learn about implementing scalable Node.js applications when you are using the App ID service. This IBM Cloud service allows you to add authentication to your mobile and web apps and protect your APIs and back-ends running on IBM Cloud. App ID provides authentication with email/password through a scalable user registry or you can add social login, so that users can sign in with their Facebook or Google credentials. With App ID, you can also host user profile info that you can use to build engaging experiences.

Passwords are not a complete security solution; they can be stolen or shared. In this tutorial, you learn how to use a random string delivered by email as a second authentication factor. I also discuss several methods for risk analysis, which is used by the application to decide whether a second factor is warranted.

In this article, you learn how to use the IBM Cloud to write a Node.js application for an organization’s front desk, which needs to log visitors in and out. Along the way you will learn how to use Node.js, the Express HTTP server library, and a Cloudant database. You will learn how to do this in the highly available IBM Cloud. This is a basic introduction to Node.js programming on the IBM Cloud platform.

In the first article in this series, you learned how to build a Node.js application on the IBM Cloud. However, that application was not very responsive or visually appealing. In this article you learn how to use the Bootstrap theme for your application to look better, and how to use the AngularJS library to make it more responsive.

Node.js is used by many companies for building performant backend services without sacrificing developer efficiency. In this hands-on guide, author Thomas Hunter II proves that Node.js is just as capable as traditional enterprise platforms for building services that are observable, scalable, and resilient. Intermediate to advanced Node.js developers will find themselves integrating application code with a breadth of tooling from each layer of a modern service stack.

  In this article I will be demonstrating how to create a basic Node.js application using Intel Mashery's JamBase API with Intel Edison and XDK. You will find accompanying GitHub source in the provi...

Online Resource

Online Resource

Online Resource

The panelists talk about Node.js.

The panelists talk to Glenn Block about Azure.

Check out RailsClips on Kickstarter!!

02:39 - Hongli Lai Introduction

• Twitter
• GitHub
• Blog
• Phusion

03:08 - Tinco Andringa Introduction

• GitHub

03:23 - Phusion Passenger

• [GitHub] passenger

06:13 - Automation

• nginx

08:37 - Parsing HTTP Headers

• Hooking

12:44 - Meteor Support

15:37 - Future Added Features?

17:12 - Passenger Enterprise

• Ruby Rogues Episode #143: Passenger Enterprise with Tinco Andringa and Hongli Lai
• About Phusion Passenger
• Documentation & Support

20:03 - Concurrency and Multithreading  

• Multiprocessing
• The Cluster Module
• WebSockets
  • passenger_sticky_sessions

23:33 - Setting Up on a Server for a Node.js Application

• Debian Packages

25:06 - Union Station Monitoring Tool (Union Station Teaser)

• Introducing Union Station: our web app performance monitoring and behavior analysis service; now in open beta
• Using Google Polymer
  • JavaScript Jabber Episode #120: Google Polymer with Rob Dodson and Eric Bidelman
  • Polymer vs Facebook React

Picks

Emily Claire Reese: Playing Catch-Up (Jamison)
Jason Punyon: Providence: Failure Is Always an Option (Jamison)
Active Child: You Are All I See (Jamison)
FFmpeg (Chuck)
YouTube (Chuck)
Developers' Box Club (Chuck)
Ruby Remote Conf (Chuck)
DevChat.tv Kickstarter (Chuck)
Dash (Hongli)
In the Balance: An Alternate History of the Second World War by Harry Turtledove (Hongli)
phusion-mvc (Tinco)
Union Station Teaser (Tinco)
Radio 1's Live Lounge (Tinco)

This episode features Moving from Node.js to .NET and Raygun.io with John-Daniel Trask. John-Daniel is the Co-founder and CEO of Raygun, a software intelligence platform for web and mobile. He's been programming for many years, and is originally from New Zealand. Tune in and learn what prompted them to move to the .NET framework!

Panel:

• Aimee Knight
• AJ O’Neal
• Charles Max Wood

Special Guest: PJ Evans

In this episode, the panel talks with PJ Evans who is a course developer and an instructor through Manning’s course titled, “Node.js in Motion.” This course is great to learn the fundamentals of Node, which you can check out here! The panel and PJ talk about this course, his background, and current projects that PJ is working on. Check out today’s episode to hear more!

Show Topics:

0:00 – Advertisement: KENDO UI

0:36 – Chuck: Welcome and our panel consists of Aimee, AJ, myself, and our special guest is PJ Evans. Tell us about yourself and your video course! NODE JS in Motion is the title of the course. Can you tell us more?

1:29 – PJ: It’s a fantastic course.

2:25 – Chuck: You built this course and there is a lot to talk about.

2:36 – Aimee: Let’s talk about Node and the current state. 

2:50 – Chuck: Here’s the latest features, but let’s talk about where do you start with this course? How do you get going with Node? What do people need to know with Node?

3:20 – Aimee.

3:24 – PJ talks about Node and his course!

4:02 – PJ: The biggest headache with Node is the...

4:13 – Chuck.

4:19 – PJ: I am sure a lot of the listeners are familiar with callback hell.

4:50 – Aimee: Let’s talk about the complexities of module support in Node!

5:10 – PJ: It’s a horrible mess.

5:17 – Aimee: Maybe not the tech details but let’s talk about WHAT the problem is?

5:31 – PJ: You are talking about Proper Native ES6 right?

They are arguing about how to implement it. 

6:11 – PJ: My advice is (if you are a professional) is to stick with the LT6 program. No matter how tensing those new features are!

6:46 – Aimee: It could be outdated but they had to come back and say that there were tons of complexities and we have to figure out how to get there.

7:06 – PJ: They haven’t found an elegant way to do it.

7:15 – Panel: If it’s a standard why talk about it?

Seriously – if this is a standard why not implement THE standard?

7:38 – PJ.

8:11 – Panel.

8:17 – Aimee: I would love to talk about this, though!

8:24 – Chuck: I want to talk about the course, please.

8:30 – PJ.

8:54 – Chuck: We will keep an eye on it.

9:05 – PJ.

9:16 – PJ: How is it on the browser-side?

9:33 – Aimee: I don’t want to misspeak.

9:41 – Chuck: I don’t know how complete the forms are.

9:49 – Aimee: I don’t want to misspeak.

9:56 – PJ: I just found the page that I wanted and they are calling it the .MJS or aka the Michael Jackson Script. You can do an import from...

Some people think it’s FINE and others think that it’s a TERRIBLE idea.

10:42 – Chuck: “It sounds like it’s a real THRILLER!”

10:52 – Panel.

11:25 – Panel: When you start calling things the Michael Jackson Solution you know things aren’t well.

11:44 – Aimee: Just to clarify for users...

11:57 – Chuck: I want to point us towards the course: NODE.JS.

Chuck asks two questions.

12:34 – PJ: The concepts aren’t changing, but the information is changing incredibly fast. The fundamentals are fairly settled.

13:22 – Chuck: What are those things?

13:28 – PJ talks about how he structured the course and he talks about the specifics.

15:33 – Chuck: Most of my backend stuff is done in Ruby. Aimee and AJ do more Java then I do.

15:55 – Panel: I think there is something to understanding how different Node is. I think that Node is a very fast moving train. Node has a safe place and that it’s good for people to know about this space.

16:34 – Aimee: Not everyone learns this way, but for me I like to understand WHY I would want to use Node and not another tool. For me, this talk in the show notes really helped me a lot. That’s the core and the nature of NODE.

17:21 – PJ: Yes, absolutely. Understanding the event loop and that’s aimed more towards people from other back ends. Right from the beginning we go over that detail: Here is how it works, we give them examples, and more.

18:08 – Aimee: You can do more than just create APIs.

Aimee mentions Vanilla Node.

18:50 – PJ: To get into frameworks we do a 3-line server. We cover express, and also Sequelize ORM.

19:45 – Advertisement – Sentry.io

20:43 – Chuck: I never used Pug.

20:45 – PJ: PUG used to be called JADE.

20:56 – Aimee.

21:14 – PJ: Express does that for you and I agree with you. I advocate a non-scripted approach, I like when frameworks have a light touch.

22:05 – Aimee: That’s what I liked about it. No offense, Chuck, but for me I didn’t like NOT knowing a lot of what was not happening under the hood. I didn’t want to reinvent the wheel, but I wanted to build at a lower level.

22:40 – PJ: I had the same experience. I wanted to figure out why something wasn’t working.

23:24 – Panel: I had a friend who used Rails...he was cautious to make a switch. This past year he was blown away with how much simpler it was and how fast things were.

24:05 – Aimee: I feel like if you want to learn JavaScript then Node might be easier on the frontend.

24:21 – Chuck: No pun intended.

No, but I agree. I like about Rails is that you had well-understood patterns. But the flipside is that you have abstractions...

To a certain degree: what did I do wrong? And you didn’t follow the pattern properly.

25:57 – Panel: With Node you get a little bit of both. To me it’s a more simple approach, but the downside is that you have 100’s of 1,000’s of modules that almost identical things. When you start reaching out to NPM that...

26:29 – PJ: Yes the module system of NPM is the best/worst thing about NODE. I don’t have an answer, honestly.

There is a great article written that made me turn white. Here is the article!

28:12 – Panel: The same thing happened with the ESLint. That was the very problem that he was describing in the article.

28:50 – PJ: Yep, I put that in the chat there – go ahead and read it! It’s not a problem that’s specific to Node, there are others. It’s the way we do things now.

29:23 – Chuck: We have the NODE Security project. A lot of stuff go into NPM everyday.

29:43 – PJ: We cover those things in the course.

29:53 – Chuck: It’s the reality. Is there a place that people get stuck?

30:00 – PJ answers the question.

30:23 – Aimee.

30:55 – PJ: I am coding very similar to my PHP days.

31:20 – Aimee.

32:02 – PJ: To finish off my point, I hope people don’t loose sight.

32:18 – Aimee.

32:20 – PJ: I am working on a project that has thousands of requests for...

32:53 – Chuck: Anything you WANTED to put into the course, but didn’t have time to?

33:05 – PJ: You can get pretty technical. It’s not an advanced course, and it won’t turn you into a rock star. This is all about confidence building. It’s to understand the fundamentals.

It’s a runtime of 6 hours and 40 minutes – you aren’t just watching a video. You have a transcript, too, running off on the side. You can sit there and type it out w/o leaving – so it’s a very interactive course.

34:26 – Chuck: You get people over the hump. What do you think people need to know to be successful with Node?

34:38 – PJ answers the question.

PJ: I think it’s a lot of practice and the student to go off and be curious on their own terms.

35:13 – Chuck: You talked about callbacks – I am thinking that one is there to manage the other?

35:31 – PJ answers the question.

PJ: You do what works for you – pick your style – do it as long as people can follow you. Take the analogy of building a bridge.

36:53 – Chuck: What are you working on now?

37:00 – PJ: Educational tool called SCHOOL PLANNER launched in Ireland, so teachers can do their lesson planning for the year and being built with Express.

Google Classroom and Google Calendar.

39:01 – PJ talks about Pi and 4wd. See links below.

40:09 – Node can be used all over the place!

40:16  - Chuck: Yes, the same can be said for other languages. Yes, Node is in the same space.

40:31 – PJ: Yep!

40:33 – Chuck: If people want to find you online where can they find you?

40:45 – PJ: Twitter! Blog!

41:04 – Picks!

41:05 – Advertisement – eBook: Get a coder job!

Links:

• JavaScript
• jQuery
• React
• Elixir
• Elm
• Vue
• ESLint
• Node.js
• Node Security Project
• Node Security Project - Medium
• Manning Publications: Course by PJ Evans
• PUG
• JSConf EU – talk with Philip Roberts
• Medium Article by David Gilbertson
• Hackster.io – Pi Car
• Pi Moroni
• Holding a Program in One’s Head
• PJ Evans’ Twitter

Sponsors:

• Kendo UI
• Sentry
• Cache Fly
• Get a Coder Job

Picks:

Aimee

• Paul Graham - Blog

AJ

• Rust

Charles

• Tweet Mash-up
• The Diabetes Code

PJ

• Music - Max Richter

Satheesh, Mithun, author