Comments on: DOMAssistant 2.7 released with unicode support http://frontendbook.com/domassistant-27-released-with-unicode-support UX, Mobile, Web and Product Development Sat, 17 Dec 2011 10:07:30 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Robert Nyman http://frontendbook.com/domassistant-27-released-with-unicode-support#comment-227 Robert Nyman Wed, 09 Apr 2008 13:26:23 +0000 http://snofs.com/blog/?p=116#comment-227 While milliseconds might seem of academic interest, it does matter for the end user when a lot of queries are run as soon as a page has loded. How fast is interaction etc added to the web page in an unobtrusive manner. However, community and documentation is vital to survive and to build a following. The DOMAssistant community is so far quite small, but it's wonderful to see the dedication of the ones involved and how helpful they are. Not because they're evangelists or anything similar, but only out of liking the product. The next step? It's a good question. :-) For us this time around, Unicode and Chinese documentation was one of those things: to look outside the box and see an entire world. :-) Next time? We'll see. :-) While milliseconds might seem of academic interest, it does matter for the end user when a lot of queries are run as soon as a page has loded. How fast is interaction etc added to the web page in an unobtrusive manner.

However, community and documentation is vital to survive and to build a following. The DOMAssistant community is so far quite small, but it’s wonderful to see the dedication of the ones involved and how helpful they are. Not because they’re evangelists or anything similar, but only out of liking the product.

The next step? It’s a good question. :-)
For us this time around, Unicode and Chinese documentation was one of those things: to look outside the box and see an entire world. :-)

Next time? We’ll see. :-)

]]> By: Mattias Hising http://frontendbook.com/domassistant-27-released-with-unicode-support#comment-226 Mattias Hising Wed, 09 Apr 2008 12:56:04 +0000 http://snofs.com/blog/?p=116#comment-226 I am with you on alternatives, such as Ext and jQuery do not compete for the same solutions, but I think that either jQuery or Prototype will prevail as the most commonly used (and documented, and supported etc etc) javascript library for a long time. As I see it all javascript libraries now focus on size and performance. Whether or not a function takes 1 ms or 3 ms is just of academic interest and things such as community and documentation is a much bigger and more important decision when choosing your library. But I do think that DOMAssistant is a good library, and it would be interesting to see it in action on a big site. What I am looking for now is someone who takes the libraries to a higher level. Now the abstraction level is set for DOM-manipulation through CSS Selectors and the possibility to create plugins. What is the next step? I am with you on alternatives, such as Ext and jQuery do not compete for the same solutions, but I think that either jQuery or Prototype will prevail as the most commonly used (and documented, and supported etc etc) javascript library for a long time. As I see it all javascript libraries now focus on size and performance. Whether or not a function takes 1 ms or 3 ms is just of academic interest and things such as community and documentation is a much bigger and more important decision when choosing your library.

But I do think that DOMAssistant is a good library, and it would be interesting to see it in action on a big site.

What I am looking for now is someone who takes the libraries to a higher level. Now the abstraction level is set for DOM-manipulation through CSS Selectors and the possibility to create plugins. What is the next step?

]]> By: Robert Nyman http://frontendbook.com/domassistant-27-released-with-unicode-support#comment-225 Robert Nyman Wed, 09 Apr 2008 11:41:35 +0000 http://snofs.com/blog/?p=116#comment-225 Thanks for the kind words. Regarding adding to an existing library vs. building one of your own, I think it's about mind-sets. Different people have different priorities and opinions on what's important about a JavaScript library. With DOMAssistant, for example, performance and small file size are a couple of the most important factors for us. I also think that no one JavaScript library is the best for every possible scenario, but rather that each JavaScript library have certain criteria to meet where they work best. Therefore, I'm a strong promotor of alternatives, hence developing DOMAssistant. :-) Thanks for the kind words.

Regarding adding to an existing library vs. building one of your own, I think it’s about mind-sets. Different people have different priorities and opinions on what’s important about a JavaScript library.

With DOMAssistant, for example, performance and small file size are a couple of the most important factors for us.

I also think that no one JavaScript library is the best for every possible scenario, but rather that each JavaScript library have certain criteria to meet where they work best.

Therefore, I’m a strong promotor of alternatives, hence developing DOMAssistant. :-)

]]>