Profile_bird

Hey there! gwoo is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving gwoo's tweets.

Already using Twitter
from your phone? Click here.

gwoo

  1. RT @pointlessjon: Screw black friday. How about rather than buying useless crap, you contribute to your favorite #opensource project? Li ...
  2. holidays are a great time for some #li3
  3. running siege benchmarks again. numbers seem to be much more reasonable this time around.
  4. @raisinbread pks is no way to win a championship ;)
  5. @kvz i just checked and xcache was not caching anything....oops
  6. running siege benchmarks on rackspace cloud with apache 2.2, php 5.3.1, xcache. php hello world 4600 req/s. html 4200 req/s. explanations?
  7. @misemono have you seen this? http://rad-dev.org/lithium/... it uses mongo, but the same code should work for mysql
  8. #php 5.3.1 compiled and working nicely. some vnice bug fixes in this release. keep up the good work guys.
  9. php 5.3.1 released http://www.php.net/releases... download http://www.php.net/download... #li3
  10. @ramsey checkout http://rad-dev.org/lithium_bin its probably the best example of using couchdb in #li3
  11. RT @raisinbread The new #li3 blog tutorial runs on the LAMP platform. Lithium Apache Mongo PHP.
  12. updated #li3 bot. http://rad-dev.org/li3_bot dogfood never tasted sooo goood
  13. removed the old #li3 branches. `git remote prune origin`
  14. RT @UnionOfRAD The RAD just got RADer. Lithium 0.2 is out.... now! http://bit.ly/2r0ZBk #Li3
  15. just packaged up the new #li3 release
  16. @pointlessjon what do you think of http://bit.ly/3KtdIZ
  17. RT @UnionOfRAD Hidden gem: type 'unicorn' into the CLI bar: http://li3.rad-dev.org/ #li3
  18. @busytoby javascript hacks? oh you mean the website. Well we are getting there and the 0.2 release will have some nice features.
  19. @thirtysix suggestions? choosing a font that pleases everyone is tough. we had to "settle" which didnt make anyone happy. Change is coming.
  20. running code coverage and profiler on all tests. Time 13.2995s, 2168 / 2168 passes, lots of lines covered...#li3