Sony are holding a big event in Las Vegas on Saturday the 6th of December, 2014, dubbed Playstation Experience. While Street Fight V has already leaked, very little else is known about what to expect.
What I think is going to be the showcase piece is Project Morpheus. We might get a release date, it is already known that attendees will get to experience the headset at the event. Sony wouldn’t allow the general public and judgemental game blogging media to get their hands on it if it were not close to completion.
There is some confusion around what the difference between Google Polymer and AngularJS is. Both being Google supported initiatives, lets clear up the misconceptions and explain the differences.
Google Polymer Essentially Google Polymer is for creating Web Components. Self contained modules written in HTML and used similarly to AngularJS directives using the type of “E” for element.
Web Components are a W3C standard, although not finalised or fully implemented in all browsers, Polymer is a set of polyfills for implementing cross-browser Web Components.
One of the biggest bottlenecks in Angular 1.x is the $digest cycle. Essentially what the $digest cycle does is keeps track of two-way bindings, watchers and other parts of your Angular application that can be updated.
For example if you have a text field using an ng-model, whenever you type in a value into this field, it will trigger a $digest cycle causing Angular to update all watchers and bindings in the app to see if anything has changed. This is because of the lack of object.observe() in ECMAScript 5 (although it is in ECMAScript 2016 (ES7) and planned for Angular 2.0).
For newbies and even developers who have been working with AngularJS for a while, there is some confusion around services and factories in AngularJS. Behind the scenes they are very similar, how they are instantiated however, is another story.
The first thing to realise is that services, factories and just about everything else (except directives and controllers) are singletons. Using a factory or service is just managing a singleton. This means the same instance of a factory or service is used everywhere.
After a recent petition on Change.org filed by some single-minded feminists requesting that Target Australia stop selling GTA V because it encourage violence against women, Target Australia have caved and removed the game from their shelves.
The petition hit just over 41k signatures (relatively small compared to other petitions and the population itself).
As an Australian adult it sickens me that a small minority of feminists even started this petition, but even more-so that Target Australia caved into the pressure and removed the game.
Looking back on the last couple of years in web development, things have dramatically changed. We have gone from an industry with a heavy dependence on Photoshop to favouring actual working prototypes and products.
As we march into 2015, I thought it would be worth taking a look what we can expect in 2015 (besides a continuation on the mammoth year that was 2014) for web development.
Goodbye Photoshop While Photoshop is not going to die over night and still be used by many designers, 2014 saw the rise of alternative software products to Photoshop being accepted into the mainstream, the main one being Sketch by a little company called Bohemian Coding. Completely vector based and built for developing modern websites and applications.
In AngularJS when it comes to communicating between controllers, one would naturally assume to reference another controller you can simply inject it into another controller and call its methods: however, you cannot do that.
Method 1: Shared service One such method of communicating and sharing methods betweens multiple controllers is a shared service. Here you might put in a method for closing a overlay or redirecting the browser somewhere or checking the state and value of a variable.
If you have used AngularJS, or EmberJS and any other front-end Javascript based framework, then you would be familiar with the concept of data binding. Essentially being able to watch a Javascript object for changes and then call a function when this takes place.
Currently without using a third party library which implements a non-native method for observing changes in a object like Angular or a polyfill, there is no cross-browser method for observing objects for changes which doesn’t involve some kind of hack at the expense of performance.
Since the recent announcement of HTML5 being finalised, we can finally talk about all of the awesome additions to HTML5 without fear of them changing. Once such addition to HTML5 is the FileReader API which allows you to work with files locally on a hard drive.
The FileReader API is seriously undervalued and surprisingly a few developers I have spoken with who know about it, have not used it or assumed that it was not really supported and thus, ignored it. And some others have not heard about it at all.
When it comes to Javascript, there are many ways you can skin a cat as they say. When it comes to inserting HTML into a page, unless you are using a Javascript library like jQuery or something like React.js or AngularJS, you most likely are using innerHTML.
Even the html() method in jQuery internally uses the innerHTML property to insert HTML into your element(s), as do many other libraries and frameworks.