Keeping things simple, the JavaScript front-end version

Keeping things simple, the JavaScript front-end version

Few days ago I had a short discussion about an idea for a webapp (publicly available, commercial, you know - all the usual stuff). As I am doing a lot of stuff in web nowadays & I've made few SPAs with different libs recently, I was asked: "Which SPA library / framework would you use today?" My interlocutor was utterly surprised with my answer: "The truth is, that in at least 80% of cases, I wouldn't use any. At least not to build a full-fledged SPA, maybe just to structure the code / handle events / manage dependencies / etc."…

Read More

Edging the edges - AngularJS 1.3 has been released

The waiting is over, it's already here. Maybe it doesn't resolve all the concerns (yes, concerns, I wouldn't even call them issues), but 1.3 is a major update that was supposed to prove that Angular.js is evolving & community's voice is being taken under consideration. What's new? If you want full list of changes, you have to check here. Below you can find the list of what was important for me personally: One-time bindings: finally a response to all of those who: were questioning the performance of digest loop in large applications evangalized simplicity of simple templated rendering…

Read More

I sense the storm coming, WebStorm it is. WebStorm 8.0

WebStorm 8.0 (http://www.jetbrains.com/webstorm/) is already here - it was officially released on 26.03.2014. The latest version of the best IDE for web devs brings some neat improvements. I'm still learning these, but to be frank - I already love most of the things I've found so far :) First things first: The feature I was especially waiting for - smooth Spy-JS integration. If you haven't heard about Spy-JS, check one of my archive posts or go straight to its website: http://spy-js.com/. The short version for the impatient, thanks to Spy-JS you can:…

Read More

Protractor - the PR0 way to do E2E tests for Angular.js

Why do we do SPAs (Single Page Applications)? For glory, gold and girls! Yea, sure, in the end it’s all of those things, BUT what are the low level, basic, crude and atomic reasons? There are few: because we don’t like to mix server tech with client-side tech because we want to truly separate presentation from business logic because we desire our front-end being TESTABLE Yes, SPAs are more testable than traditional approach to server-generated web apps. Same applies to my beloved angular.js - it supports automated testing by design and it promotes two different…

Read More