|
|
|
|
|
by tabtab
2343 days ago
|
|
The same internal or custom CRUD app done with 90's tech was much quicker and much less code than current web stacks. Is it too much distraction with fads and JavaScript UI gizmos, CRUD-unfriendly web standards, a combo, or something else? Something is wrong. It's good for IT worker employment, but customers are paying an ARM chip and a leg (bad pun intended). We de-evolved. Ooga Booga. We had Jetsons-like drag-and-drop IDE's and code that closely matched the screen and business logic, but then replaced them with Flintstone stone tablets, saying "It Must Be This Way" in case we go "mobile" in 2080 or whatnot. Now it's layers talking to layers talking to layers and we spend all our time wiring and rewiring the layers to layers. The buzzword is "separation of concerns", but I see separation of productivity and separation of money from wallets. "Enterprise" apps were always a bloated e-bureaucracy, but the bloat trickled down to smaller apps in a big buzzword chase to be "just like the big dogs". Maximalism rules IT. (In well-run shops, such stacks can be done effectively, but most orgs are semi-dysfunctional. The tall stacks are not riff-raff proof. One duck moves out of alignment, and the results are quacked.) |
|