3 ms·

Because every six months we start over again with new models, libraries, tools, compilers, transformers, names. Except stable APIs and documentation.

dang 3y ago
I think causality is probably the other way around, i.e. we keep starting over because the problem is hard. There's a back-and-forth lurch that happens when people discover that yet again, they're caught in a complexity net, have a strong it-shouldn't-have-to-be-this-complicated feeling, and set out to build tools that will make the problem easier in general. Often it's relatively new programmers running through this cycle, who perhaps don't realize (yet) how many times this lurch has already taken place, or how they may be repeating the approach of a previous 'generation'. (That's not a cricitism—it's the cycle of life of the software business, and has been going on since long before most of us showed up.) I do think there's something about UI that lends itself particularly to this phenomenon. Perhaps its statefulness, as someone else said already.
- jbverschoor 3y ago
  I don't think the problem is too hard. It's just that people don't seem to understand the different models and history of things. People have this not-invented-here syndrome. It also comes from the fact that they initially think a certain framework is too complex. Only to figure out later that they didn't understand why certain things were done in a specific way. Also, the fame and opportunity that comes with creating a framework cannot be denied. For example, The whole "MVC" term on the web is plain wrong (web2.0 times). It's a term from actual GUI programmer, bolted on a document presentation format. These days it's probably faster and easier to distribute an OS such as MenuetOS via web assembly, and simply run a GUI application inside which uses a simple JSON api. About statefulness... why are we introducing stateful applications which is then patched up with server side rendering when a simple html application would suffice? It makes no sense. It's stupid, costly, and has 0 benefits. For more complex applications, sure.. but tbh, where are those? Is a simple admin panel or login screen really 10x more difficult to create than VS Code, or for that matter Microsoft Access? "Engineers" in general like^H^H^Hlove^H^H^Hget off on complexity. That is where the problem lies. It's intellectual porn and toxic as hell. End of rant |] merry Christmas:)

dang 3y ago

I think causality is probably the other way around, i.e. we keep starting over because the problem is hard. There's a back-and-forth lurch that happens when people discover that yet again, they're caught in a complexity net, have a strong it-shouldn't-have-to-be-this-complicated feeling, and set out to build tools that will make the problem easier in general. Often it's relatively new programmers running through this cycle, who perhaps don't realize (yet) how many times this lurch has already taken place, or how they may be repeating the approach of a previous 'generation'. (That's not a cricitism—it's the cycle of life of the software business, and has been going on since long before most of us showed up.) I do think there's something about UI that lends itself particularly to this phenomenon. Perhaps its statefulness, as someone else said already.

jbverschoor 3y ago
I don't think the problem is too hard. It's just that people don't seem to understand the different models and history of things. People have this not-invented-here syndrome. It also comes from the fact that they initially think a certain framework is too complex. Only to figure out later that they didn't understand why certain things were done in a specific way. Also, the fame and opportunity that comes with creating a framework cannot be denied. For example, The whole "MVC" term on the web is plain wrong (web2.0 times). It's a term from actual GUI programmer, bolted on a document presentation format. These days it's probably faster and easier to distribute an OS such as MenuetOS via web assembly, and simply run a GUI application inside which uses a simple JSON api. About statefulness... why are we introducing stateful applications which is then patched up with server side rendering when a simple html application would suffice? It makes no sense. It's stupid, costly, and has 0 benefits. For more complex applications, sure.. but tbh, where are those? Is a simple admin panel or login screen really 10x more difficult to create than VS Code, or for that matter Microsoft Access? "Engineers" in general like^H^H^Hlove^H^H^Hget off on complexity. That is where the problem lies. It's intellectual porn and toxic as hell. End of rant |] merry Christmas:)