berzniz

We've developed (and keep developing) a rather big application in Backbone.js - it holds up and works perfectly.

We are setting a move from it since it lacks in some areas (no POJOs, no nested, manual binding, lots of extra backbone-mini-libs required), but it does hold well at any scale.

I wouldn't direct new comers to backbone.js anymore, new trends with 10x more contributors wins over anything. I wrote about it being the C++ of JS MVC frameworks (http://berzniz.com/post/66372634868/backbonejs-is-the-c-of-j...)

Go Oz!

Styleguides are a matter of taste and there are probably no two people in the world with the same taste. Was there a voting of this?

It's on GitHub, issue a pull request with a fix

I actually work for people who I consider to be good friends. It's just something I tell people of how this industry works and why it's an awesome job.

Yes, it's only saved on your browser (LocalStorage)

This is such a bad idea that I had to comment here:

1. Doesn't scale. You do not want to hand pick text all over your site/web-app. 2. It's not semantic. 3. It's very confusing to new people who looks at your code. 4. If you ever change a single char in that sentence, you will have to re-break it yourself.

var getJSON = function(callback) { // did async work to get the JSON data and now I want to call the callback function, but is it there? callback && callback(data); };

getJSON(); // See how I don't care about the result

Tell a novice JS developer to concatenate a list of strings: "first", "middle" and "last" into "first, middle, last".

You'll probably get a solution using loops and a check if adding a comma is needed or not.

I know, I asked my friends. Ask your new teammates.

While introducing new developers to work on the JS part of our codebase (node & client side) - I noticed some puzzled looks here and there.

Not everyone understands why && and || are used outside of if statements. Not everyone knows about joining strings using an array.

This summarises the things you'll have to know to read code in our codebase.

Reactjs is very interesting as well. The thing that looks weird there is the HTML inside the JavaScript code.

At least 2 generalists, from then on specialists are better.

Tumblr. You could have your blog up within 10 minutes

Maybe the first tip should have been "use Chrome".

I've used Firebug and Firefox tools, but they don't add much. Firefox has a nice 3D feature that only helps "WOW" your friends.

Chrome is the only real tool today for developing and debugging web-apps.

It just can't be the same under Facebook. It's a matter of time until my whatsapp entity and my Facebook entity (I don't have one today) will merge.

Same thing as Google tries to do with Youtube users. It just doesn't make sense to have two types of users in your system.

It helps me keep in touch with people I really want to be in touch with: friends, family, co-workers, my soccer group.

It just works perfectly without ads, slowness, UI changes.

It's simple to use, my mom & dad uses it easily (>60).

I wish they didn't sell. Love the product, FB will ruin it.

Love this wish list! Some great points you got there.

About videos: I rather if they'll allow animated gifs instead. Indie developers just don't have enough money to spend on videos and we'll lose to the bigger companies.

When you introduce new people to the development team, less code means less issues.

Old code had nasty things like traversing the UIView hierarchy and removing unwanted UIViews.

Old code had deprecation warnings.

Old code is not optimized. Apple are doing a much better job at creating great working UIKit controls for us.

Any day that I delete code is a good day.

Our app is iPhone only, but this is a great point to remember for anyone thinking about dropping the non-retina image.

Yeah, that's a great feature.

One open issue is that from time to time a breaking change to our API is needed and a force-upgrade is forced on the app users. We try to avoid it, but it happens.

The next time this happens, it's really goodbye iOS 6 users.

Thanks. I didn't know them. Pretty impressive.

Clutch was great! I've used it myself, but you had to create the A/B tests while coding.

I'm going for a tool that lets you define the test after it was coded. Is that a big enough differentiator?

I actually like the way nil is treated. I'm not a big fan of writing code with guards all the time like this:

// As in C#/Java if (obj != null) { obj.doSomething(); }

At least in javascript it's easier with the && operator:

str && str.doSomething();

In Obj-C you can just:

[str doSomething]; // If you really care if it happened or not, then introduce a check for nil

Once you get used to the idea that nil doesn't break your code, you start writing your methods accordingly.

For me, a lot of the stuff you write about (ARC, Blocks, literals) are the great improvements to the language.

Before ARC you had C/C++ like control of the memory and you could do some crazy stuff like an object holding on to itself and then committing suicide (pretty useful actually). With ARC you only have to care about retain cycles and declaring weak/strong pointers. It's an awesome feature for a non-GC environment.

Blocks are truly the biggest change in Obj-C and made the code much easier to develop. Any async task is now easy to deal with. Alongside GCD, multi-threading is made simple.

What I'm really trying to say is that from the first iPhone OS to iOS7, we've seen some major improvements to the language. If it continues at the same pace, you'll might like it more in your next year's review.

Can't provie it, but I'm seeing this for my own app (It's in Hebrew and quite successful in Israel http://bitly.com/DriveModeHeb ) and other previous apps.

There is one hack that seems to work.

Keeping the app free for its first week on the store. This gets the app in the hands of the right people, the "early adopters". If the app is good, they'll use it and recommended it to friends long after the promotion week is over.

People are not afraid to pay when the trial was confirmed as a success by their friend (who is an iPhone genius).