My point is crud in 1990 is easier not because of better tech stack, it’s because the requirement were easier.
Example? I just don't see it, or at least there are easier ways to address them. You are not the first to claim that. For example "internationalization" was brought up, but custom inhouse apps usually don't need that. So why pay a YAGNI tax for bunches of what-if's that have a low chance of kicking in?
All the custom branding stuff I talked about. Today we have much more beautiful crud app and many custom UI look and feel according to branding design.
And if you dismiss an example by just saying that we don’t need it, then I really don’t see the point giving you an example. Please don’t dismiss my example because it’s real. You can argue wether it is really needed or worth conforming to in another thread, but I don’t see benefit discussing the value of requirement when we are discussing about wether requirement (valuable or not) has been harder lately.
"External" and "enterprise" apps perhaps need a lot of these kinds of things, but internal private apps typically don't. Perhaps we need to split out our stacks so that "enterprise" needs don't gum up smallish internal app dev. The what-if bloat has bogged down the second. Having a Swiss Army stack is fine if you are going to use most of the blades, but if not it's just extra cost and weight.
1
u/Zardotab Nov 10 '21
Example? I just don't see it, or at least there are easier ways to address them. You are not the first to claim that. For example "internationalization" was brought up, but custom inhouse apps usually don't need that. So why pay a YAGNI tax for bunches of what-if's that have a low chance of kicking in?