Skip to main content


Showing posts from September, 2011

Git in Windows

There is new application for Git that works on Windows and Linux (using Mono).

This application is interesting because looks stable, and have very friendly installer (msysGit is included).
I saw it on Windows and this works pretty stable.

Book Review: NetBeans IDE 7 Cookbook

NetBeans IDE 7 Cookbook by Rhawi Dantas is book for developers who want to start using NetBeans. Book can be both for students and those more experienced but not familiar with NetBeans.
Most chapters are specific to Java, but there are couple more language agnostic, like using version control systems. I read this book from beginning to end, but this book was created to user when needed. I want to create JavaEE project, check out index, find chapter about it, read while creating and done!

Tips for other readers: Do not read chapter about JavaFX - this is about 1.3 version, even Oracle created version 2.0 for Java. Creating JavaME application is supported only on Windows.Feel free to start reading wherever You want. Links to book:
Book: Table of contents: Sample chapter:…

TodoMVC - Examples of MVC for JavaScript

Searching for MVC library for JavaScript can be difficult, they all are different. How to chose based only on documentation. You can end up with something that not fits You, but has nice looking site ;)

Addy Osmani created repo with Todo Examples written in most popular libraries:

With this it can be really easy to try and see how these libraries are really working in more serious app than hello world.

Backbone is interesting but I must admit that most of them are rather new to me.

YUILibrary and Sproutcore are rather not for me.

Anyone is using one of :


Any recommendations? I rather don't want to use something heavy.

Semantic Versioning

Idea is not new, similar approach can be found in many places but now it has nice name.

Lately I read Node Web Development and Node.js modules in npm used this approach to make npm so awesome.

Read more at website:

In a brief:

There is API, it can be code or whatever but this is treated like API.Use 3 numbers: 1.2.3 - <major>.<minor>.<patch>Patch - bugifex - API comatibleMinor - new or compatible API changesMajor - any incompatible API changes How this can help? By using "strict" convention this can be used by tools (like npm) to make it easier to You to update dependencies. If You use library in version 1.2.0, then You can update easily it up to 2.0.0! Of course it is better co confirm it by developer that this really works, but if library developer uses semver like You, it should!
There are many other rules, if You can't use it, at leas show it to You's co-workers, it would be great to really standardize this, at low level. 
But …

Vim for JavaScript

On reddit there is interesting movement to create list of all Vim command that are especially useful for JavaScript development.

I do not copy this list, just see it at reddit:

Some of them are new to me and I will try to use them like:

gf - open file whose name is under the cursor:3 - go to line by numberyy, p - yy copy current line, p - pastes it below:vsp file - open file in vertical new windowCtrl-ww - switch between windows<Ctrl-v><number>jI#<ESC>- comments lines (inserts #), number - of lines (arrows doesn't work for me, but you can insert many number of numbers eg. <5><2> = 7), then j nad UPPERCASE i, last text to insert.<ctrl-v><number>jx - deletes column - undo commentgg=G - format entire buffer (gg - beginning of file, = - auto indent, G - end of file)

Pollyfilling and Performance

Consider this post more like stream of thought, rather than complete manifesto, or whatever this looks like.

Today I read

This article is just about problem, maybe about problems our industry has with older browsers.
Progessive enhancement is awesome, but how in "real life" really make it working, how to convince you'r boss that this is good, how to convince customer? Sometimes You just CAN'T.

On the other side we have pollyfils, we make it working in older browsers. Add hacks, more html, even more CSS. Code is ugly but finally works everywhere! Everyone is happy besides You. After some time they want to change something on site, and You tell them ridiculously long estimation. Why, because this is nightmare to maintain, to test again and again if this little tiny images for shadows works as supposed in IE6. And what tell You them when this site is really slow in this old browsers? Impossible to fix. Google ran…

Slicebox - 3D image slider

Slicebox - Awesome slidebox!

Book Review: Node Web Development

Node Web Development by David Herron is book written for those who want to start using Node.js for real Web Applications. Book is short and written for purpose of practical examples. Of course if it will be longer it would be even better but this is very good starting point for learning Node.js.
Book is rather short, and to be honest when I sow it I was thinking: This is too short! But just after first chapter I realize that maybe short, but chapters are full of examples and explanations. I was impressed how reading it changed my opinion.
Tips for other readers: Use Node.js from 0.4 tree, mostly because of modules, most of them are not ported yet to 0.5.If You want to create apps as fast as possible read chapter 5 at the end (except of those that want to use HTTPClient)Install Databases before installing npm modules.Links to book:
Book: Table of contents: Sample c…

Progressive Enhancement 2.0

New post on Paul Irish blog is answer for a question: Do websites need to look exactly the same in every browser?

The best analogy is to explain it like old black&white TV's and new HD ones. Do any TV station still use  only blask&white to serve exactly the same to all users? Of course no!

To read more about how to explain it to customers, and why you should think how to make your site fast, not identical:

Most of ideas are from Nicholas Zakas presentation:

Progressive Enhancement 2.0 (Conference Agnostic)
View more presentations from Nicholas Zakas