10 ms·
The Python Paradox Is Now the Scala Paradox (2009)
- interrrested 10y agoWhat language would it be in 2016 ? Go ? Rust ?
- MichaelBurge 10y agoHaskell's a good choice there.
- Anderkent 10y agoGo is pretty much mainstream by now, I don't think it's a stronger filter than say python. Depending on subject area, I'd look at clojure, ocaml, haskell, lua, or rust.
- claudiug 10y agohow you define mainstream? by number of jobs, scala is way ahead, also python, javascript, ruby, java. Even here, when jobs are listed, numbers of go jobs are quite low
- hughperkins 10y agoWhenever i see a bunch of code written in a language different fron whatever the rest of tge team are using, that language is often: go :)
- Anderkent 10y agoMight be bias from my anecdotal experience, but whenever I speak with people working at large corpos, go comes up more often than python or ruby.
- tonyarkles 10y agoAnother subject-area-specific option: Elixir. I do like every option you've presented as well; Elixir just fills another niche.
- Anderkent 10y agoI was considering mentioning erlang, but you probably don't want to write erlang. I've never touched elixir, but I would likely try it if I hit a problem that I would use erlang for in the olde days.
- agentgt 10y agoI would say OCaml particularly with a potential killer app of MirageOs. Stat usage wise it makes Haskell look mainstream... but serious real world code is written in OCaml (I would argue maybe even more serious than Haskell :P ). The users of OCaml almost always know how to parse really hard things to parse which is a pretty descent filter.
- JohnnyConatus 10y ago+1 I'm seeing OCaml at a number of HFT FinTech plays. MirageOS sounds cool. What are people using it for?
- vegabook 10y agoThe missing link in MirageOS is a BEAM-style distributed computing framework. If this were available, I'd be using Ocaml/Mirage almost exclusively. Imagine the beauty of supervisable, millisecond demand-scalable, ultra-lean, Ocaml-safe microkernels all messaging each other atomically and cross-node, without the dev having to build it from scratch.
- aikah 10y ago> Go It was specifically design to disallow smart-asses to write ninja-code, so no. Go is for monkey programmer factories which managers want to make sure they will only code a certain way because Go doesn't give the developer choices. It's the anti C++,scala,python,clojure... Go tells you to do this that way, and doesn't give you the constructs or features to make your own choice about coding.
- fixxer 10y agoIf you want to experience a "programmer factory", learn Java and get a job at a bank.
- booleandilemma 10y agoI've read that a good codebase is supposed to look like it was written by one person, no matter how many people have contributed. I know that doesn't sound fun but it makes maintenance so much easier.
- adrenalinelol 10y agoOf the two you listed, Rust. Go could have held this space back in ~2013?
- jsmith0295 10y agoGo would probably be the opposite of this, and I would argue that is a good thing. Hiring "smarter" people by picking a more esoteric language is likely to result in you having an esoteric or "clever" code base. That's just going to cost you in terms of maintenance in the long term, and it's not a requirement for productivity. You should be able to hire good people without this kind of filter, and use the tools that best fit your domain. That may or may not be Go, but at least it emphasizes consistency, simplicity, and readability, which is basically the opposite of what you get out of Scala.
- acjohnson55 10y agoI'd argue Scala emphasizes both simplicity and readability. Simplicity in the "simple, not easy" sense. I will grant that the language had a reputation for operator soup, due to many library authors being enamored with them. But I think this has long since fallen out of favor. In Scala, you basically have to learn the constructs and their semantics. No way around that. But once you do, almost everything is just various compositions. For the most part, it's very predictable. The execution model is ultimately pretty simple. Consistency -- I'll give you that. There are a lot of options for how to structure your code. And when you start composing libraries together, you have to be able to understand the paradigms the authors use.
- Roboprog 10y agoYeah. Seeing some Scala Build Tool stuff a while back really turned me off. Me: ooooh, look at all that overloaded operator stuff! Scala guy: those aren't overloaded operators, they are just function calls with funny names and optional parentheses. Me: it just gets better and better :-( Operator stew, whether Scala or C/++, REALLY makes me appreciate the Lisp style of function calling. "Evaluate inner parentheses first. There is no step 2." Now you're trained in "operator" precedence, which, by the way, I have seen responsible for far more costly errors than runtime types. (I'm putting C's lack of any real type checking at all in a different level of problem - sometimes useful for systems stuff, but foolish for general biz apps)
- 10y ago
- tsaprailis 10y agoProbably Elixir
- sotojuan 10y agoI second Elixir, though if trends continue you're going to get a bunch of long time Ruby/Rails people (not bad or good, but something to be aware of).
- danenania 10y agoElixir is great in the sense of attracting people who are interested in functional programming, distributed systems, and scalability, but aren't willing to give up pragmatism/productivity/readability in exchange. In my experience, these are the best kinds of people to work with. Cs theory + get shit done = good engineering.
- sotojuan 10y agoHappy to report that I'm one of those people! I like how Elixir keeps itself very practical, but at the same time lets you extend it however you want if you feel something is missing in your project. For example, you'll never find monads in the standard library but people have made their own monads through macros.
- acjohnson55 10y agoThe only problem, in my opinion, is the lack of explicit types. From what I can see, the compiler provides some safety that doesn't exist in typical scripting languages. But I think we're pretty much at a point where so many of the commonly used scripting language idioms can be effectively described in a type system. TypeScript proves this. But it also proves that's it's still pretty difficult to add types to a programming language ecosystem after the fact, so it feels like that ship has likely sailed for Elixir.
- Roboprog 10y agoI would argue that enforcing, or at least favoring, immutability and the ability to trace data flow is more helpful that static types. You could have both, but I know which one I would rather give up first. (actually, in the best of all worlds, I would want optional [compile time] types as well as type inference)
- lj3 10y agoClojure? Nim? Julia? Kotlin? Swift? There are no shortage of new, good languages these days.
- crdoconnor 10y agoI think we live in different times now. Ecosystem matters much more. There are certain languages with features that I love (haskell's state isolation looks lovely, for instance), but I'm not willing to make the jump because the Haskell ecosystem isn't there and might not ever be there. This mattered much less in the past as ecosystems were much smaller and people tended to build software much more from the ground up. That said, I think it applies within ecosystems still. Scala programmers get to choose a better language without abandoning the Java ecosystem. F# programmers get to choose a better language without abandoning the C# ecosystem. The "paradox" is evident there. Go is definitely not that language (generics? lack of package management for years? c'mon). Rust, maybe (for systems programmers).
- ludamad 10y agoCan't you just bias for people with personal projects in any language?
- biehl 10y agoYes. Leaning new technologies (and using them appropriately) is probably a valid indicator of something to hire for. But certainly not the only one. A personal project might show of better indicators - design skills, communication skills etc
- hughperkins 10y agoI vote personal project. Its meritocratic. It involves approximately similar skills to being successful in a technical role. It contributes something new and novel to society. Its probably a better predictor than fizzbuzz, or knowing some technology buzzwords...
- deleted 10y ago[deleted]
- crazygringo 10y ago"Smarter" programmers are very rarely what a company needs, in my experience -- it's extremely rare for a startup's success to depend on that. (I mean, I love clever algorithm programming, but it's just so rarely needed, sadly.) To the contrary, programmers with the ability to deliver and iterate working code quickly is what is needed -- and especially without overengineering, or inadvertently creating huge future technical debt due to inexperience. And if there are only 2 or 3 or 5 programmers on my team, and one of them gets sick or leaves, it's far more important to have a big pool of potential replacements who could can get up-to-speed in a couple weeks, not months -- which means a popular language and a straightforward codebase.
- galdosdi 10y agoActually I would count the skills you describe as "smarter." The fact that we don't all assume this is a sign something is wrong. Maybe it lies in that I don't remember too much emphasis in CS education on legibility and maintainability, beyond some token "practicum" classes that focused just as much on the many other "practical" topics like version control, working together, unit testing, etc. The best programmer I ever worked with had an incredible ability to produce straightforward, simple code, that could have been written by "any fool" ... if "any fool" had gotten incredibly lucky. His code looked so obvious in retrospect, like anybody could do it. He made the difficult look easy. I call that very smart, and you desperately want brilliant people like that. The programmers I've worked with that were traditionally "brilliant" in the sense of quickly coming up with "clever" but hard to maintain solutions only count in the middle of the pack, and I dreaded working with their code. Their code was more likely to not last as long and be thrown away in a refactor. So I learned to aspire to be more like the first than the latter. And in doing so I saw just how damned hard it is to create simple looking "any fool could do it" solutions to hard or even medium problems. So many times I thought something was clear, but it was not to others. So many times I only finally thought of the architecture that would make it possible to write it simply and legibly after many iterations through other designs that generated much more complex "clever" code. It made me gain incredible respect for the amount of smarts and experience it takes to generate simple, easy, boring code that anyone can easily read and pick up.
- zerr 10y agoThese paradoxes come and go, but there is only one paradox that remains the same: C++ :)
- antod 10y agoThe original paradox was the Paradox Paradox where you avoided all those blub Access developers.
- cortesoft 10y agoI think there is some serious flaws in the author's logic. Having the free time to learn the 'fashionable' new language doesn't mean you are smarter or a better programmer; it just means you have more free time. In my professional experience, people that are always learning new languages or are constantly using new libraries and frameworks are never the ones who accomplish the most. They simply are the ones who are always seeking novelty; they never become great at a language, because they are always wanting to try something new. They start lots of projects, but don't finish them. I don't think those are the best qualities to look for in employees.
- zengid 10y agoGreat points here! I agree with you that there are people who chase after novelty and don't complete most of what they start. If the person is naive about it then I would be weary about hiring them, but it depends on the persons motives. If they are doing it to experiment with a new library/framework then finishing may not be the point; it could be to see if the tool is worth the hype or if it adds unnecessary complexity. This exploratory tinkering has been good for me personally because it has developed my sense for parsing out the bullshit used to market new tools.
- crdoconnor 10y ago>In my professional experience, people that are always learning new languages or are constantly using new libraries and frameworks are never the ones who accomplish the most. There's a huge difference between chasing fashion and seeking out what is new that is actually better. I agree that those people are usually worse. The ones that pick up on new stuff that isn't necessarily fashionable, assess it intelligently and balance the trade offs of the good vs the bad - those are the better programmers. IME scala programmers are better - mostly because they tend to be programmers who got frustrated with java's shortcomings and realized scala solved many of those shortcomings, not because it's fashionable to learn scala. IMO people who chased mongo, on the other hand, demonstrated a responsiveness to large marketing budgets rather than critical thinking skills. You don't have to try out every new technology either. There are some that you just have to read a bit about to know enough to dismiss them.
- JohnnyConatus 10y agoI used Scala for one company I founded and the Python Paradox to be true. People who already knew Scala were generally much more accomplished programmers and for the people who didn't know, the learning of it was a great test of their ability. Here's why: as a hiring manager, I know it's possible to learn Scala. So if someone couldn't learn it and be productive within 30 days I knew they weren't sharp. (FYI, everyone did learn it quickly, but frankly, the best programmers can learn a new language in a weekend.)
- noir-york 10y agoWhat are you hiring programmers for? A science project, or a company which has to meet business goals? If the former, by all means, pick some esoteric language. If its the latter, more mundane issues like existing codebase, skillset and, I don't know, perhaps using the right tool for the job? C# can do things Python cannot and vice-versa. Learning Scala to show off and fit in Graham's paradox is silly and doesn't prove that you are a smarter programmer. A smart programmer is someone who comes up with smart solutions; you can write crap code in any language.
- crdoconnor 10y agoI'm pretty sure what applies to Scala vs. Java programmers applies to F# vs. C# programmers. Existing code bases, etc. don't matter so much when you're sharing the same ecosystem, and the good programmers from that ecosystem will certainly choose the best language that they can within it.
- noir-york 10y agoSure, if its within the same ecosystem - at which point the diff is really just syntax. (Whats Python's ecosystem anyway?) But I doubt a moderately complex architecture can live within just one ecosystem. We use PHP, C, Lua (to script the C), Go and Python (being phased out in favour of Go) because different workloads/problems have different requirements.
- crdoconnor 10y ago>at which point the diff is really just syntax. If you think the difference between F# and C# is just syntax then you have little understanding of either language. >Whats Python's ecosystem anyway? Everything on pypi (django/flask/pandas/etc.). It doesn't have another language targeting the VM like C#/F#/Scala/Java if that's what you mean, and there won't be a paradox among programmers of that ecosystem like there is for .NET / Java. >But I doubt a moderately complex architecture can live within just one ecosystem. We use PHP, C, Lua (to script the C), Go and Python (being phased out in favour of Go) That mix of technologies suggests that you have a legacy problem (e.g. a CMS based on wordpress you can't get rid of) and technology choices that are fashion conscious (migrating python to go). I suggest reading Mozilla's story ("from python to go and back again"): https://docs.google.com/presentation/d/1LO_WI3N-3p2Wp9PDWyv5B6EGFZ8XTOTNJ7Hd40WOUHo/mobilepresent?pli=1&slide=id.g70b0035b2_1_168 https://docs.google.com/presentation/d/1LO_WI3N-3p2Wp9PDWyv5...
- TheMagicHorsey 10y agoI would have said Go rather than Scala, but now Go is pretty mainstream. I think my choice today for a Python Paradox would be Erlang or Ocaml. Ocaml + MirageOS is a system level simplification that makes application correctness/security a much more tractable task than [any other language + linux]. Erlang is the most common sense way to build resilient, distributed applications. But there is a high barrier to entry to learn both Erlang and the OTP framework that makes it useful. Having said that, I've never worked at a company where choosing Erlang or Ocaml was a possibility. I think there are companies that make bold technical choices, but I haven't had the good fortune of being given the chance to work at such a place.
- sidlls 10y agoGo is mainstream? In what universe? These are mainstream languages today: C, C++, Java, PHP, Ruby, Python, JavaScript, and C#. The vast majority of all applications written today are written using one of those languages. Go barely registers inside the Bay Area bubble, and far less outside of it. If a "Python paradox" even is a thing, Go would certainly be a candidate. I think the "Python paradox" is a silly concept, though.
- TheMagicHorsey 10y agoYou may be right. I work in the Bay Area, and I see a lot of devops projects in Go these days. In fact, I'm hard pressed to find a new devops project that isn't in Go. But I agree that the Bay Area, and San Francisco specifically, is a bit of a bubble. So its very possible that there is little Go traction in other cities.
- XorNot 10y agoGo has devops traction because of it's deployment story. It solves a bunch of problems people have with trying to use Python for the types of things you do in devops.
- BerislavLopac 10y ago
- kozikow 10y agoI was there and worked in company that hired for Scala. I've seen teams who went back to Java 8 be more productive than teams that went hardcore Scala, including Scalaz. If you filter for Scala, you are more likely to pick academic purists trying to show off with their core. If you filter for go, you are more likely to pick pragmatics, who will be aware that every choice is a trade-off (including no generics) and will value maintainable code over clever code. I already made a choice.
- labrador 10y agoIf hiring a JavaScript programmer, if he or she had not at least learned the basics of Dart and TypeScript and done a weekend project in it, I would consider them incurious. Considering that all the best developers are very curious people, this would be an effective filter. For c++ programmers, if they hadn't done something in D it would be a red flag.
- dasmoth 10y agoWould you give a pass for Purescript or Elm?
- labrador 10y agoThose are great too. Something that shows a passion for learning. How could a passionate JavaScript programmer not learn Dart, TypeScript, or Elm? Even if to say why they're no good.
- douche 10y agoYou're selecting for language dilettantes, then, I'm afraid. Especially for languages like C++ or JS, that contains worlds of different approaches within their umbrellas, I don't necessarily see not dabbling with something that fills the same niche as a deal-breaker, or indeed all that valuable, really. I would consider a more useful filter looking at people that have experience in multiple levels of the stack, whatever your particular niche happens to be. For web dev, having a good handle on two or more of: SQL, a server-side language, and JS/CSS/HTML. Substitute whatever blocks fit in your particular equation.
- labrador 10y agoWe're talking about two different types of programmer I think. You're talking about a maintenance programmer and I'm talking about someone who might be able to move the technology stack forward and possibly save some money in the process by finding a new and more efficient way of programming. I wouldn't expect someone who is happy doing the same thing over and over again in maintenance mode to be that person, although this type of programmer is a very necessary part of the team.
- djhworld 10y agoI wonder if the author still believes this, 7 years later.
- bogomipz 10y agoI am curious what constitutes a programmer who "knows" Scala? It is enough to be fluent with a common framework such Play? Must one be proficient in using it in all three - functional, object and procedural programming contexts? The breadth of the language really is an overwhelming barrier to entry to someone coming from say Python. I am interested in hearing what people think.
- watmough 10y agoWhat's the feeling on raw C++ these days? Is it still truly mainstream, or have C++ users, at least on Microsoft, mostly migrated to managed C# code? Certainly at the company I work at, there's been an active migration over maybe the last 5 - 6 years to C# from C++, though we still have millions of lines of C++ / MFC / WinForms code in the primary application I support and help maintain. Career-wise, I'm quite happy to stay with C++, as it's been my experience that I can throw together utilities that run with minimal, run fast and are reliable, just using C++ and the standard libraries. As far as writing Scala or Python, Why write code that goes slower than it needs to?
- BerislavLopac 10y ago> As far as writing Scala or Python, Why write code that goes slower than it needs to? Let me put it this way: why write software that goes faster than it needs to but is written slower than it needs to be?
- watmough 10y agoGood point, but the sort of utilities, data munging code I typically write, can be hammered out in C, or C++ pretty fast. I've been easing into the C++ standard library, lambdas etc., and familiarity makes it easy to write code that uses standard proven, fast, data structures, and mostly allows me to avoid any non-stack data allocation. Avoiding heap memory allocation, and taking advantage of the appropriate idioms, allows much faster development, even in C++. The huge bonus when done correctly, is very high-performance, clear and portable code.
- BucketSort 10y agoIt's not a paradox. REEEE
- meshko 10y agoI'm not terribly sure about this, might be my skewed perspective, but it feels like Scala is being dragged into mainstream by Spark.
- dllthomas 10y agoThis matches my impression - it seems very much mainstream within the data analysis niche, and that's leaking a bit.