Ivo Jansch’s profile

Egeniq.com founder and CEO, PHP/iPad/Android/iPhone developer, Entrepreneur, Book Author, Speaker, Interested in Mobile and Web

Latest Comments

1

Although you did mention that you werent going to discuss the why, I can't think of a single valid reason to force ids to be sequential, so out of curiosity I hope you can give an example.

Posted in Auto Increment with MongoDB.

Thu, 29 Jul 2010 at 21:27:50 GMT


2

Good luck with whatever it is that you are going to do next, I'm sure OmniTI will not be the same without you!

Posted in Goodbye, OmniTI.

Sun, 19 Jul 2009 at 06:40:10 GMT


3

Although I do not agree entirely that rev=canonical is the way to go (rel=alternate shorter is more flexible for the intended purpose of shortening urls), until there is something better/more final, I've added support for it to http://flackr.net. All event pages (e.g. http://flackr.net/s/d2al ) contain the rev=canonical header).

Posted in Save the Internet with rev="canonical".

Thu, 30 Apr 2009 at 08:08:23 GMT


4

If twitter is one of the reasons we need short urls, maybe we should ask ourselves what the reason is these urls need to be short. Bandwidth isn't the problem, but screen real-estate is. You want urls to be short because in a 140 char message, it leaves more for actual content.

What strikes me as odd is that noone has suggested that twitter should implement simple <a href="long url">short word</a> support. This would mean that under the hood, it can use a larger limit, while on the surface, it can have a 140 character limit and still be perfectly readable. Hide the url completely from the user just like we do in normal html content.

Posted in Save the Internet with rev="canonical".

Wed, 15 Apr 2009 at 20:49:52 GMT


5

Congratulations with the achievement! I've always looked at OmniTI as an example. Basically we are very similar in terms of PHP activities, but we're on the other side on the ocean. Maybe we can at some point in time cooperate with eachother. I bet we have very similar philosophies.

Posted in OmniTI Turns 10.

Thu, 27 Sep 2007 at 13:13:56 GMT


6

I'm trying to introduce 'test first' in our company (as part of an attempt to put XP to practice). For some it's easy to do it, others are having difficulty with this approach, being not used to it. I have to put significant effort in teaching the testing framework and the methodology.

But most find it a very useful way of working, once they get the gist. Tests may not always drive the design (in my opinion, you do design first, then tests, finally coding), but it sure helps validating it. Also, testable code helps in keeping it reusable, by reducing (cross)dependencies. I think I can safely say: "If you are unable to test it, the design must be flawed".

Posted in Who Practices Test-Driven Development (TDD)?.

Tue, 28 Mar 2006 at 06:24:34 GMT


7

Sorry, I meant to say 'advantages and disadvantages' where I said 'disadvantages'

Posted in Gosling Didn't Get the Memo.

Mon, 13 Mar 2006 at 17:29:41 GMT


8

I think the 'scripting language' is not so much about 'to compile or not to compile', but the major thing here is 'persistence'.

In a java environment, be it a Swing application or servlets or beans, you have native persistence. Objects persist over requests, and this has its own set of disadvantages.

The major drawback of PHP is in its very nature that for each request, a script is reexecuted. Ofcourse we have sessions, of course we can serialize stuff, but those are basically workarounds for the lack of object persistency. (not to mention that persisting objects in sessions only works per user).

PHP5 has better OO support than PHP4, but in my opinion, true OO is only useful when the objects persist after a page completes.

Posted in Gosling Didn't Get the Memo.

Mon, 13 Mar 2006 at 17:28:40 GMT


9

Isn't that kind o fa leak? Apparently, my php sites can output stuff that I'm either not aware of and also that maybe unwanted.

Posted in PHP Easter Eggs.

Sun, 05 Feb 2006 at 09:01:54 GMT


10

Mind you that you are focussing a lot on the ajax side of Rails. This is just 'one of the features' of rails. They use the 'prototype' library for all the nifty dhtml/ajax features. All the sites you mention are examples of how prototype can make your apps flashy, but this could also be done using prototype in combination with other (php even) frameworks.

Posted in Ruby on Rails Fans.

Thu, 02 Feb 2006 at 08:19:13 GMT


About

  • Twitter: @ijansch
  • Location: Netherlands
  • Joined: August 2005
  • Comments: 18