> Whereas the regexp thing, I don't think that decision was likely made 
> after the code was already released. It might have been "we don't have 
> time" or "we don't think it'll help enough people" or even "if I bring it 
> up, I'll wind up having to do it", all of which I'd classify as "lazy". 
> But I think a manager telling the programmer not to program something 
> isn't "laziness".

Reading several MS blogs it becomes obvious (if it wasn't already) that they 
have a limited amount of resource.  There are many things the developers 
would love to do, but they (or rather their managers) simply have to make a 
choice what to work on.  And of course they have to release software, 
because if they don't more people complain than if they release it with some 
feature not implemented or buggy.

Post a reply to this message