Google’s look, evolved

The “G” has a new style! Today Google announced a simplified logo that emphasizes its four major colors. The new logo is already in place on Google Drive and Google Search.

 

Today we’re introducing a new logo and identity family that reflects this reality and shows you when the Google magic is working for you, even on the tiniest screens. As you’ll see, we’ve taken the Google logo and branding, which were originally built for a single desktop browser page, and updated them for a world of seamless computing across an endless number of devices and different kinds of inputs (such as tap, type and talk).

It doesn’t simply tell you that you’re using Google, but also shows you how Google is working for you. For example, new elements like a colorful Google mic help you identify and interact with Google whether you’re talking, tapping or typing. Meanwhile, we’re bidding adieu to the little blue “g” icon and replacing it with a four-color “G” that matches the logo.

Read more from the source: Official Google Blog

React, JSX and ES6: The Weird Parts

Valid JSX complaints: overuse of element nodes and an ugly API for if statements, doctype, and comments

 

“I’ve spent a few days working with JSX and React and I have mixed feelings about them. React is pretty neat, but I find that they made some very unusual choices when it comes to their API design. Then there’s JSX, definitely the weirdest aspect of React – we’ll look into it as well. I’ve really enjoyed the ES6 and Babel experience, although I’ve noticed that there’s a learning curve where you start to decide whether using an ES6 feature is better than its ES5 equivalent or not, something we’ll explore towards the end of the article.”

Read more at Pony Foo

Introducing Four: It’s WebGL, but Easier

Develop 3D content for the web with low-level abstractions such as shaders, framebuffers and texture and enjoy higher-level APIs for camera, lighting, and materials

 

Jason Petersen writes:

Over the past three years working in the realms of web-based physics simulations using WebGL, I have realized the lack of a web-based physics engine. This is probably due to the large amounts of data manipulation required to do this. To address this problem, I started to develop Four.

Four is a framework to develop 3D content for the web. It lets you avoid the burden of repetition and complexity to speed up and simplify the development while exposing the flexibility of the WebGL API. This is done by exposing several layers, each built on the top of the previous one, that give you access to a different level of abstraction. Depending on your needs, you can access the most basic level or a higher one. This allows you, as the developer, to focus on what is important: getting something on the screen.

Read more at SitePoint

Samsung banks on JavaScript, Node.js for IoT

The Internet of Things is growing and Samsung for one is choosing Node.js for microcontrollers

 

Samsung looks to leverage JavaScript as a mechanism for IoT (Internet of things) development with its IoT.js project.

The recently unveiled IoT.js serves as a lightweight version of Node.js. “IoT.js aims to provide interoperable service platform in the world of IoT, based on Web technology,” the IoT.js website states. “The target of IoT.js is to run in resource-constrained devices [having] only few kilobytes of RAM available device. Thus it will supports very wide range of ‘Things.'”

Read more at InfoWorld

Unforked: io.js v3 sets stage for Node.js merger

io.js v3 is essentially a beta release of Node.js v4 with significant updates including many ES6 features

 

Paul Krill writes:

Compatible with npm, io.js was spawned as a fork of Node.js late last year after disagreements arose over Node’s direction. Everything was smoothed over this spring, and the two factions, which had many of the same participants, agreed to reunite. “The governance of io.js and Node.js have already converged, all that is left is the technical side, and io.js v3 is a significant step towards completing it,” said Mikeal Rogers, who has served as a spokesman for io.js, in an email.

“Developers need to know about io.js v3 because it’s a significant change to the native side of the platform they’ll need to understand in order to prepare for Node.js v4,” Rogers said. He also noted version 3.0.0’s status as the likely last release line for the platform.

Read more at InfoWorld