On 15.05.2011 19:36, Adam D. Ruppe wrote: > I think you'll feel differently once you see people abuse that option. It > becomes hard to follow what's going on.
Sure I will feel differently, that's why I've said "if used correctly" - and I do use it correctly :) > You're also not used to it. (When I write this for newbies, I often put a > comment in there: <!-- filled by program -->) That kind of a comment made me crazy many times - because then I had to dig inside the program to find the place where it was filled :) > It's an easy pattern though: an empty element with an ID is meant to be > filled in, and the ID should be descriptive enough > to make a good guess at what it's doing. If at some point I want to change output from table view to something else - then I've to change the application as well, as it generates series of tr/td elements, which I don't need anymore. To me, it is much easier to change it in place - i.e. where this is done actually. Bouncing from template to code is quite annoying, to be honest, especially when that code is not your own :) > After you see it used once, it's not a mystery anymore. It is not a mystery, just something that is blocking my productivity :) I just don't like it - and because of this I am less productive. From my point of view, it makes no sense to say "that is wrong" or "that is bad" - unless there is *objective* (and only) way to do something *right* - which is not the case in web development (and any software development in general). So, to some people (including myself) unless and until D may be embedded like PHP/ASP, it will be a show stopper. For some others - it will not, that's all. For this reason, I prefer to use D as a backend only (=performance critical), and frontends will be in PHP or ASP (=UI only). Though, currently I evaluate option to use D to host a server (HTTP) with dmdscript as server-side scripting language. What blocks me is the absence of good, robust and high-performance socket/file I/O framework for D2. /Alexander