4 ms·
> usually have lots of layers for organizational reasons The ridiculous number of layers in Java or C# are more of a skill and guidance issue than anything els
by jen20 2y ago
> usually have lots of layers for organizational reasons
The ridiculous number of layers in Java or C# are more of a skill and guidance issue than anything else. Older languages don’t always mean over-attempted-abstraction (think C, for example).
- trustno2 2y agoI have worked in enterprises and the layers are usually an organizational issue that just acts as code issue. Structure of code often reflects structure of your company. The code is often maze of layers because the company is a maze of sub-committees. Java/C# fits more neatly in there. Although with Go, what can happen is that there is a maze of microservices. Maybe that's not that much better.
- pjmlp 2y agoNever seen CORBA and COM written in C, I guess. Enterprise Architects will do their beloved architectures with whatever languages are the tool of the day.
- jen20 2y agoOhhhh boy have I seen that. Like I say, it’s a skill issue, but those people tend to be in Java and C#, not Go and Rust.
- pjmlp 2y agoGo has Kubernetes ecosystem for that, and Rust is yet to take off as application programming language embraced by Enterprise Architects at big corp.
- jen20 2y agoThe Kubernetes code base isn’t great, but the notion that the ecosystem is even nearly as complex as the average EA monstrosity implementing basic forms over data as multi-player Microsoft Access is fanciful at best.