I’ll praise integration
Hopefully I’ll have got my twitter integration sorted out by now so I’d better test it!. This post should get tweeted -so I’d better say something about integration.
Happily, a recent entry in the IET Gen Development Blog about integration (of a different kind) caught my eye.
Whilst its true that Gen is great for back end development (batch and server components) it’s (allegedly) not good at GUI development.
I disagree, and therefore agree with IET’s viewpoint – Gen can “do” servicable front and back end development – especially with products like IETeGUI out there.
But isn’t it about choice ? I SHOULD (and CAN) do all my GUI developement within Gen and the eco-system partners’ products, but it I want to “do” the UI in another product then I should be able to. It IS all about choice, but not the simple choice of “ease of use” – it comes down to many other factors – such as the level of code reuse between the UI and back end components; what the application is for – is it purely a service application with limited GUI; or does it need a rich AJAX-based interface ?
Factors like these will guide you to whether you need pure Gen; Gen + a product like IETeGUI (or OCX controls); or a third-party tool.
