KodeGeek

• So Disney acquires Marvel. All the sudden I see a crossover of Wolverine with Donald Duck #

java java, kodegeek, twitter

• @isalara you need to tell us what is it about in reply to isalara #

java java, kodegeek, twitter

• Trying to get my Android phone. Veronica cannot stand my $25 cheap old cell phone so I guess it is time to upgrade. Sorry Apple #
• It is official, I got my Android phone. Now is time to do some coding #
• @sd estoy buscando un cliente de Twitter bueno, saves de alguno in reply to sd #
• @sd Estoy nuevo con Android. ¿Como me lo bajo? (por cierto el cliente grátis de FaceBook apesta) in reply to sd #
• @sd http://www.swift-app.com/, también ¿no? Dejame probar. in reply to sd #
• Dowloading swift through Wi-Fi (T-mobile lagging behind in CT, no 3G until next month) #
• Using swift from my Android #
• New pastime: Blocking morons and spammers in Twitter. It is so cool, woo hoo! #

java java, kodegeek, twitter

Después de leer este articulo (con la ayuda del traductor de BabelFish de Yahoo) me quede pensando por un buen rato: ¿Es que todos los proyectos de código abierto necesitan de una dictadura?

Yo creo que si. Tiene que haber una mano fuerte, un general, que comande a las tropas a hacer cada una de las tareas. No importa si el proyecto es minúsculo (como StupidZombie) o inmenso (como el Núcleo de Linux) a la hora de la verdad tiene que haber alguien que tome ciertas decisiones difíciles.

Mis anécdotas en este caso se refieren a StupidZombie; Muchas de las personas que manifestaron interés en el proyecto querían tener accesos de escritura al repositorio de Software en Subversion.

La respuesta fué un rotundo no. En serio, esto es como una entrevista de trabajo. Usted se baja el código fuente, hace un ‘parche’ y lo entrega y así prueba que puede hacer el trabajo. De ninguna manera yo le daría acceso de escritura al código que tanto ha costado escribir a alguien que no está calificado (es distinto a tener una visión diferente del proyecto).

¿Suena demasiado serio para un proyecto pequeño? Bueno, usted siempre puede hacer un ‘fork’ (o rama) del proyecto, como es el caso de MySQL

java

• Have an inner battle between my SA and developer side. Don’t know which one is winning but surely feeling the pain #
• Math at work: http://www.wired.com/wiredscience/2009/08/zombies/ #

java java, kodegeek, twitter

• Working remotely today. #
• @sd I’m working from Starbucks but Stamford, CT. Weird coincidence (by the way, AT&T Wifii works really well). in reply to sd #
• @isalara Supongo que algo bueno salio de todo esto in reply to isalara #
• @ratonfilo Sip. No lo pudo decir mejor. in reply to ratonfilo #

java java, kodegeek, twitter

• @sd LOL in reply to sd #

java java, kodegeek, twitter

• @sd Todavia no. Estoy esperando a fin de año a que salgan más alternativas. Aún estoy con mi telefono de $20, LOL in reply to sd #

java java, kodegeek, twitter

• Nice webcast and practical workshop of developing with Android: http://training.oreilly.com/androidapps/. Thanks O’Reilly #

java java, kodegeek, twitter

Thanks to the O’Reilly Facebook group I got the chance to review the book ‘Even Faster Web Sites‘, by Steve Souders. Please read below to get an idea on what to expect about this new title from O’Reilly ($34.99).

Synopsis:

This book is a collection of practical tips and advice on how to optimize web pages, focusing in client side optimizations. It explains how to reduce downloading times through coding techniques, CSS and image optimization, speed up page rendering and code instrumentation so it will definitely will appeal developers and designers that work with Ajax or regular JavaScript sites.

The book is written by several authors (the main one is Steve Souders), and it was specially nice to read Tony Gentilcore (the author of the popular plugin ‘Fasterfox‘) writting about some gotchas of the use of Gzip to serve web pages, among other things.

How is it organized:

The book is organized in 14 chapters, each one of them can be read independently (more or less) from each other. They are packed with good examples that are brief but illustrate each technique, which makes this book a good reference guide. Also the appendix (which is so big it should be called the chapter 15) is loaded with really useful tools that can be used to detect and diagnose problems on a website (the majority of them are free).

Missing things:

Not everything is perfect. The book focus almost on Javascript optimizations and loading techniques but doesn’t mention what can be done with other important technologies like Flash, SilverLight or even Java Webstart (JavaFx is gaining traction these days).

Forgets to mention server side techniques like connection and thread pools, page caching (server side not client side), among others, or common tricks used in well known frameworks like Ruby & Rails, Java Servlets (PHP is mentioned briefly though).

Also missing is the coverage of server side tools like vmstat, mpstat, top, free, tcpdump or ethereal (Linux, Solaris, BSD or UNIX tools) which could be really useful to diagnose performance issues on the web application.

To be fair this is a book focused on client side techniques and talking about server side optimizations will make it pretty big, so maybe the tittle of the book should be changed to ‘Even Faster Web Sites, client optimizations’ (I am pretty sure the authors have tons of server side techniques to share as well, so maybe this could be a second book on the subject? )

Conclusion:

It is another solid title from O’Reilly that delivers concrete techniques that can be used to speed up websites that rely on Javascript, images and CSS to present the content to the end users. The lack of the mention of the existence of server side techniques is a minor glitch but still there is great value on each one of the chapters of this reference book (I am going through them to make this blog to load faster )

Kodegeek stars: 4 of 5.

opensource, programación ajax, book, faster, javascript, oreilly, tunning, web site