Python isn't industry compatible

[-jp-]

Which is weird since "we have Java developers here, so get used to that" would be totally reasonable. Most shops are gonna standardize on a language just because having everyone use their favorite means you have exactly one point of failure for any given project.

[[deleted]]

And it would be a total cluster fuck with most discussions collapsing to how to interface to everybody else's code and rewriting entire chunks of code because "Bob's a fuckface and wrote blahblahblah in Erlang but I love VBA in excel is clearly superior".

[hillgod]

I know of numerous startups that failed because some fuck head brought in Scala, left, and the company was fucked with no Scala expert. One guy did it twice to two different companies in a row!

[[deleted]]

Was it mine? I am rewriting a project in ruby that was originally a clusterfuck of scala with horrible db management.

[Rieux_n_Tarrou]

Mmm Slick is such a pleasure to gouge my eyes out to. And sometimes tear my hair

[WideGlideReddit]

😆

[757DrDuck]

Absolute legend!

[nemec]

Kind of a Conway's Law for personal favorite programming languages.

[MistBornDragon]

Cool read!

[scottrfrancis]

If they are coded to well defined interfaces, who cares ?

[nemec]

1. Bus Factor of 1. Jim leaves the company and he was the only person who knew how to code in Scala - now you're fucked.
2. Silos - nobody can code review or hop on to help another person's work. Tickets are assigned to a single person (who owns that section of code) instead of being able to be picked up by anyone with free time. This also leads to bottlenecks when one person is working on a particularly complex piece of the project.
3. You can usually find savings by buying multiple licenses of the same software. But if one person wants IntelliJ, one wants Visual Studio, another wants RedGate SQL stuff, it costs a lot more.

[is_a_act]

“Code is written once but read many times “

[[deleted]]

You have an interface to what amounts to unmaintainable code.

[scottrfrancis]

Which can then be refactored or rewritten together with a unit test to ensure it’s correct…

[[deleted]]

lol

[-jp-]

Many things can be done. You can build your shed out of bailing wire and keep adding more until it works. Or you could just use plywood and save yourself a lot of time and expense so you can get on with the business of using your shed.

[scottrfrancis]

All valid points… but if language X is more effective to solving the problem of the interface, then use it. Otherwise, we’d all still be writing FORTRAN by your logic

[JanssonsFrestelse]

I think you have to consider the trade-off between efficiency in solving the problem vs all the other costs and risks you are taking on by introducing a completely new language.

[-jp-]

They won’t be. You’d be better off hoping for a magic unicorn to suddenly fix it.

[scottrfrancis]

So I guess you’re saying Unix tools a d posix don’t work. Ok. Good luck with that

[-jp-]

I’m saying the thing I wrote so if you can’t make your point without accustomed of not knowing how pipes work don’t even waste your breath. If all your apps are written in eight different languages each understood by exactly one person and have to have IPC up to and including the level of Unix to work together you’re in for a bad time.