Comments on NonBlocking.io - Malte Ubl's Asynchronous Identity Disorder: Unsolvable Problems – Why micro libs suck.

@Anonymous Which documentation are you referring t...

2011-05-11T17:28:04.379-07:00

@Anonymous Which documentation are you referring to? Oh wait, I forgot, Anonymous users are stateless...

If they want people to use TAP freely, why is all ...

2011-05-11T09:37:00.204-07:00

If they want people to use TAP freely, why is all the documentation under a restrictive license instead of a permissive one? That is only gonna cause people to avoid it; I know I will.

@Malte Yep, I agree. I was just explaining my conc...

2011-05-11T09:14:04.702-07:00

@Malte Yep, I agree. I was just explaining my concern of using microlibs (esp for an app's core) and the compatibility issues that may result.

John, cool that you agree with my points. The thin...

2011-05-11T09:03:23.475-07:00

John, cool that you agree with my points. The thing is that this isn't really a debate of micro lib Vs. macro lib. Any given toolkit will never solve all known problems that are worth putting in their own module. Thus even if you use MajorToolkit2.0 you will always need extra modules on the side which again shows the need for the infrastructure described above.

I'm glad you mentioned the "jQuery plugin...

2011-05-11T08:59:00.019-07:00

I'm glad you mentioned the "jQuery plugin" quality problem. That is exactly the same issue devs face with microlibs. Each have different quality/features/support priorities. This puts the burden on devs to wade through the muck to find quality microlibs. The burden is even heavier when using microlibs to compose your app's core (events, dom, ajax, selector engine).

In my screencast, Microlibs: The FUD Challenge, I suggest that consistent cross-browser support is easier to achieve by using a modular/buildable framework instead of a bunch of independent microlibs. I believe this is true, in part, because mainstream/mature libs have lots and lots of unit tests :D

The world still has to end because of smaller, com...

2011-05-11T08:50:44.912-07:00

The world still has to end because of smaller, composable libraries. *cough*

In node land everything is fine due to the excellent dependency management of npm 1.0 (again, we’re not sure yet but it seems to be working pretty well so far).

The only big thing that’s different in browser land is the inconsistent underlying platform but I’m sure we will learn (if we even need to) and adjust.

I mean let’s go back to static typing. Just kidding.