4 ms·
The notion that languages focused on writing large-scale programs must be "boring" seems a bit silly. What these languages need is lots of ways to define sensib
by zozbot234 5y ago
The notion that languages focused on writing large-scale programs must be "boring" seems a bit silly. What these languages need is lots of ways to define sensible modularity boundaries, and the "boring" aesthetic (or lack thereof, rather) can really get in the way of that.
- pjmlp 5y agoThe point being that at scale all code should be written the same way, in an environment where most teams are composed of rotating consultants.
- marcosdumay 5y agoWell, the counterpoint is that you shouldn't have a team composed of rotating consultants. And if you have one, you can't expect it to deliver anything with any quality or productivity. But yes, if that's your team, then all code should be written the same way, all on the most boring way possible. There's a reason Java and C# are so popular.
- pjmlp 5y agoThis is the modus operanti from all Fortune 500 whose main business isn't shipping software, for them IT is a cost center.
- marcosdumay 5y agoAs I said, there's a reason Java and C# are so popular. And it may not even be a bad thing, I don't know the overall impact. It does cut a lot of good developers that could be creating great software out of it, but it also opens space for a lot of people that wouldn't add value in a different environment. It also adds a great deal of costs due to the bad software, but it probably increases the amount of problems we can solve with software.
- zozbot234 5y ago> But yes, if that's your team, then all code should be written the same way, all on the most boring way possible. I agree that code should be written to be "as boring as possible" but even then, it's not clear that a "boring" language helps. What you really want in your scenario is very extensive and up-to-date documentation, both of inter-module boundaries and within individual modules. Java and C# supposedly try to make this easy, but mostly fail. The real reason they're still so popular is that they're easy to "learn" up to some not-even-barely-tolerable standard for the average cheap consultant.
- ysleepy 5y agoThis is short sighted. Teams do not build everything from scratch, probably most shipped executables are 90% outside libraries, open source or not. Code being predictable is a huge win, not only with other people but also with your own code from 10months ago. It also makes change more calculable.
- Consultant32452 5y agoI would submit that any language that reaches the level of adoption that Java does will be considered boring. The human mind has a tendency to prefer new/fresh things, particularly for people high in trait openness (big 5 personality traits).
- ReleaseCandidat 5y ago> I would submit that any language that reaches the level of adoption that Java does will be considered boring. I know of nobody who would call Javascript or C++ boring ;). Or compare COBOL (boring) with Fortran if you prefer something from the past.
- Consultant32452 5y agoI don't know anyone who is excited about learning C++. The excitement around JS is trying to make it not be like JS.
- gmueckl 5y agoTL/DR: it's about readability and clarity of unfamiliar code. One problem of large codebases is that they tend to be team efforts. Given a a sufficiently large and flexible language, each team member will find their own style and idioms for their code. This creates the subtle problem that team members are unfamiliar with each other's styles and when they touch the same pieces of code, they each extend the subset of used language features by whatever is required for their favorite idioms. Eventually, the resulting code gets too elaborate for its own good and maintainability goes down. A boring, simplified language ideally constrains the team to use more or less the same patterns and idioms and this side-steps the problem.
- lenkite 5y agoBoring Is Best! When you have junior programmers joining/leaving teams, consistent, boring code written in one Boring PL according to Boring Code Conventions is like driving on a freeway in one straight direction with auto-pilot on. Clever code written in half-a-dozen Cool PL's is like driving for your life in sharply turning mountain roads with no guard-rails - something guaranteed to become cataclysmic as your number of issues/escalations rise and rise, your tech debt becomes an un-surmountable mountain and you watch your hair turn grey before you are middle-aged.
- jimbokun 5y ago> What these languages need is lots of ways to define sensible modularity boundarie One of the most important modularity boundaries is dependencies on libraries written by others. So a good, easy to use dependency manager and a straight forward mechanism for creating and sharing libraries is crucial. Java does really well in this regard.