So you're using a weird language
morepablo.com
morepablo.com
If niche lang is so much better, then why is no one using it?
Well, quality doesn't necessarily lead to popularity. I would encourage talented solo devs to seek work in niche languages, at least once in their career. You can deliver more value, work with interesting people and solve more interesting problems.
Life is too short for Java CRUD.
The xkcd linked in the article had me laugh out loud. I hadn't known that one, it's great, and what it says about languages rings true.
Well, yes, there are. But picking the right language for the task is one easy way to improve software quality, so why discard it?
Also, for some issues and metrics, software quality is in fact limited in practice by the language used. Getting guarantees of certain properties is trivial in garbage-collected languages, near impossible in languages with manual memory management. Similarly, the lack buffer overruns and underruns, XSS exploits, properly following protocol, etc. are going to be trivial to guarantee in some languages, near impossible in others.
Now, I fully understand that following the hype wagon (or listening to fanbois singing praise about the latest tech, whether it's a language or anything else) is annoying. But let's not confuse hype and using the right tool. The intersection between those is often rather small :)
The language isn't all that important. The main problem is functional decisions that transcend the implementation language. It's not hugely important if I write this comment in English or French to get my point across, and that's why I'm writing it in English.
Beyond the random internet post (or the rare one, like "Beating the Averages", which might well be exaggerated) I haven't seen any obvious competitive advantages from choosing a non-mainstream language. On the contrary, what you often see is that immature ecosystems are huge timesinks because a lot of stuff simply isn't "there" yet.
That's not to say there aren't incremental improvements happening with new languages over time. But if your goal is to complete a project as opposed to evolving a language ecosystem I'd say that it's unwise to pick a non-mainstream language. Heck, I'm still using C for almost all of my projects (chances are I'd be using Java or C# if I was working in other domains). I've tried to switch - I have smaller and larger investments in a dozen languages. But no other language has stuck for me. A big reason for this inertia is that I simply know C well and I feel productive with it. But there are more objective qualities, some of which are related to it being mainstream and having a mature ecosystem. My language of choice has flaws, but they are well-known, with well-known workarounds. That lets me focus on the problem instead of the tools.
Blog posts generally don't consider these qualities because they can't be discussed with toy examples that show you how you can neatly turn an isolated problem from 10 lines of C code into a 2-line fancy language solution. The problem with these examples is that they are not representative of longer-term and larger-scale software development.
I think this is the root of the disagreement. For my domain at least, I find it very hard to write robust software in some languages and fairly routine in others.
Unfortunately the data on this topic is very limited - typically groups of college students implement something in various languages to compare. Hardly a realistic test.
What I can point to are code constructs that I cannot make in certain languages where the work arounds are either more verbose or less precise.
But you will be hard pressed to find a serious domain where there aren't solid mainstream tech choices.
> What I can point to are code constructs that I cannot make in certain languages
This is what I was alluding to, these examples are not very relevant. In a larger-scale codebase the important thing is the structure that you build, not the structure you get for free (or are being imposed) by the language.
If you cannot say certain things easily, then write a function to factor the common stuff in a layer that you can then build upon. This is the basics of programming, and from what I've seen this is already where it fails in most real-world codebases.
Functions and records (structs) are sufficient to cover you in almost all real world situations. I believe that the step up from assembly to higher-level languages is a very powerful step, because it frees you from doing a repetitive task again and again, that you can't even realistically do better than the compiler (because of time constraints), at least not on a large scale. Another reason that the step works is that what it automizes are quite local issues to solve. Barring extreme optimization requirements, we can simply come up with a function call ABI and have the compiler solve all register allocation for us. The tradeoffs and ramifications of this are quite clear - we can be confident by now that there are no unknown tradeoffs that will come haunt us later when the project has grown much bigger.
The same step up will be hard to repeat, since functions and structs are so expressive already, it's rare to find a problem that can't be elegantly solved using them. Garbage collection is another big help automating the repetitive in some domains, but it gets in the way in other domains.
One thing that's hard to express with them is a data type that's TypeA OR TypeB OR TypeC. For that you need Sum Types, which a lot of the newer generation of languages (Rust, Swift, Kotlin) have, but the older generation (Java, C#, C++) historically haven't had at all and still have poor support for.
I find this to be a significant productivity boost over languages that don't support this.
One thing I don't particularly about ADTs is that they remove opportunities to tweak the representation, and make you think less about smarter ways of avoiding certain complexities caused by choice (Sum Types) in the first place. But I have to admit that very often I'm simply doing the "struct with a tag member and a union member" thing manually, which one gets for free by using standardized ADT syntax.
This presupposes that the language even has facilities to enable appropriate abstractions! You can't argue that languages don't matter without reckoning with these real world matters. Yes, sure, I can just "abstract it away", yes, sure, "all languages are Turing complete so equivalent".... but no, that's not the whole story at all.
> The same step up will be hard to repeat, since functions and structs are so expressive already, it's rare to find a problem that can't be elegantly solved using them.
Expressive types are that next step up.
Maybe, sometimes, ... - in practice, I've often seen them pave the path to madness. When types become "expressive" the problem is that now you have to deal with 2 languages. An ok one and a soul suckingly bad one.
My thesis is that you need to pick the right language for the task and that language evolution regularly produces languages that are an order of magnitude better at some tasks than previous languages. To pick an extreme example, I doubt that you're going to code your next relational storage with pure C. You'll most likely use some SQL (or a competitor) somewhere in the stack.
And of course, as I believe we agree, the ecosystem matters a lot. In many, but not all, cases, it matters more than the language.
As usual, development is a matter of tradeoffs.
As everything in development, it's a tradeoff. I have written system code in JavaScript (calling directly into libc or kernel32.dll methods) and I don't want to ever do it again. I have written compiler code in C++ and the code was orders of magnitude worse than it would have been in a functional programming language. I have written database code (the actual dbms, not using a database) in both OCaml and Rust and I'd really prefer using SQL (or some layer on top of it), rather than reinventing it.
etc.
Just look at the market cap of YC companies started over its first 10 years and group by initial back-end language choices.
It wasn't dominated by companies using Java, .Net and PHP. On the contrary, those using Ruby account for over 50% of the valuation. Those using Python (a far less popular language then than now) accounted for another 17%. PHP, JS, Java and .Net combined were at under 5%.
The additional effort to add tooling and workflows that most of the teams aren't comfortable with, extra effort implementing integration layers, might slow down delivery to the point of diminishing returns, thus withdrawing any advantage.
So while I personally might not like it, in some scenarios that is exactly the tool to use.
Same applies to other domains and whatever language might be the "to go option" there.
To stick with Java as the example, Java was designed with a set of affordances for managing mutability, complex inheritance relationships, and objects with rich behavior, and the coding norms and "wisdom" surrounding Java in the early years was based on that. Appreciation for immutability, value objects, and transformation rather than mutation came from outside of Java. That's my experience and the experience of the people I've worked with: our understanding of the value of immutability and dumb data came from working in languages that demanded or at least strongly suggested it and had elegant affordances for it. If we worked exclusively in Java, we would have been much less likely to realize the value of an approach that seemed alien and awkward in our language of choice. (Eventually, due to popular demand, better language support was tacked onto Java, but I'm talking about 10+ years ago.)
Every programmer should at least dabble in other languages and try to absorb the good big ideas from them, even if they ultimately put these ideas to work in "mainstream" languages.
> "Stop wasting your time on programming languages"
"stop trying to fasc us out of having fun while being productive!" is my reply.
there are already enough people trying to improve software quality using rusty shears, let me use my fusion powered laser cutter if i want to!
In the end you just have to plow, and it doesn't matter all that much how you do it (as long as you use my preferred brand of course). Plowing tech isn't all there is to growing crop and vegetables. There is an awful lot more that you have to understand and plan and take care of, and upgrading your plowing tech won't help you with any of that.
Which XKCD? I read the article but missed it.
The XKCD: https://xkcd.com/568/
As someone who has used Nim in-anger and production at a couple companies now (and am currently using it to build our firmware for our industrial IoT sensor platform), I can wholeheartedly agree with this.
The first couple things I built in it at previous positions were small internal tools. They went well, team members contributed to them as well, things were good. It was that, plus the unique constraints of this firmware project that allowed us to have the confidence that it would work well -- and it has.
Of course, Nim is sort of cheating, as it being able to be compiled-to-C-sources means we have an out at any point we want, both in terms of being able to easily bind and use driver code from vendors, to wrapping up a Nim object file with a nice C header to call from some C/C++ code if need be.
Now: our backend is Java, and our front-end is Typescript and React. Pick your battles! If we were swinging for the fences with some other niche server side, and Elm or something (as much as I enjoy playing with it) for the client-side, as well as trying to use something non-standard for the firmware itself, I'm sure we would've failed immediately.
But we have our devices out in the wild in rural Papua New Guinea where no one's going to be flashing our boards for us, and they're working fantastically :)
I know Python best. But I have reached my breaking point with its syntax, and its lack of binding constructs, and lack of symbol datatype, quote, etc. I am intending to use Clojure ... but I have to ship this thing by May 2023 come hell or high water.
All else being equal, I will proooobably be able to go further with Python. But I'm concerned it will hamstring me from doing the crucial feature of "extending the design [ie code] of a game as it runs" since, AFAIK, it's difficult to get a Lisp-ish experience of total live reloadability in Python... jurigged[2] and reloading[3] not withstanding.
I know some common lisp so I'm not a total lisp noob. I've learned enough CLJ to be dangerous ... but I'm worried I'm backing myself into an endless hole by using a language I'm not yet master of. Yet, I think the features of the ecosystem (total live reloadability of a CLJ/CLJS app! with current state preserved even down to what a user has typed in the HTML UI!) are so tempting...
Just venting out loud. comment/contact if you have suggestios or are curious about the project; i'm soon to begin blogging as I develop it.
[1] I'm reinventing the "virtual tabletop." Current ones are so fucking shallow. [2] https://github.com/breuleux/jurigged [3] https://github.com/julvo/reloading
A big part of the value proposition is access to the entire JVM and JavaScript ecosystems. Bindings will be available for the more popular libraries, and if there aren't, well, Clojure is designed to make that easy.
It might not be pretty, it might not be idiomatic, but you're never going to hit a wall where "oh, if only I was using a popular language, I'd be able to do $obscure-thing". $obscure-thing is available for the JVM.
Also, for anyone interested, Casey Muratori implemented such a system (though very simple) on C for his Handmade Hero game. It works by reloading a dynamically linked module on every frame. It's a model that should be adaptable to any compiled language.
There doesn't seem to be a good GUI framework for Clojure. There was Seesaw but it hasn't been updated since 2019 (no maintainer). There is a guy developing a new framework https://github.com/HumbleUI/HumbleUI/ but it's WIP. I guess you could sidestep this by making it a webapp and using figwheel + web framework of choice.
My project will definitely be a web app -- I'm most familiar with web dev, plus I'd much rather be able to point someone at a URL and say "here's the thing try it out" and have that happen in 5 seconds instead of dancing the installation mambo.
Thanks for the pointer to figwheel -- that looks like hot stuff and just what I need for end to end server/client interactive dev!
>but I have to ship this thing by May 2023 come hell or high water.
Do you feel that you have to start working today in order to meet the deadline, or you can put a couple of weeks aside to develop your skill in whichever other language you'd like would be more adequate.
coupling clojure with python sounds like a drag, even using graal i dont think this will be easy. but janet you could bind as a dll and eat your cake while having it as just recently FFI was added. if you are interested, i can probably help a little as im working on an integrated (game)development repl myself. not sure how to classify what im working on but i think its close to your domain as i want to change my hotloop during runtime from the repl and from inside the running game. i just wrote you an email.
EDIT:
ah, just now read that you want to make this a webapp, in that case being closer to the metal isnt really helping, so nevermind ^^
This makes it one of the languages of choice for auxiliary scripting a big system, like a game or an application. (The other common choice is Python, and nowadays also JavaScript.)
Anything else, it is relatively awkward at.
I looked at D, Crystal, Nim, Go, Rust, Haxe, Swift and Zig (and C/C++, even Pascal). The language I liked the most (by far) is Nim, but unfortunately the niche community makes it a no-go for using it at my job, and the lack of hype like Rust makes me pessimist about its future.
The second most interesting languages where Rust (but the borrow checker and the amount of ', |, <, > intimidate me) and go (but for a weird reason I'm not hooked by its syntax).
My conclusion was that where I work (not a dev company), I can't use nothing but java, python and javascript if I want my code to be sustainable, and that I will keep Nim or maybe Rust/Go as a low level hobby
Edit: as a funny note, during my exploration i stumbled upon array languages programming languages like K, and I'm convinced there are mainly a scheme to guarantee jobs for people using them
I came to Java as my 6th or so language (small amounts of Basic, VB, C, Assembly and Javascript before) and while I absolutely didn't like it in school, once someone told me how it was supposed to be used (rely an a real IDE) it became much easier.
I still continued to dabble in other languages (mostly php and python), but these days no way I would go back to Python.
I like Nim too, but it needs more adoption.
I'm trying to think back to when we all started moving from Perl to Python and it's been so long I can't even remember what that looked like and if it was senior developers driving that or just a subconscious decision and happened "magically".
What really makes me pessimist is the fact that software development decisions are increasingly hype/marketing-driven than based on technical reasons.
If it's actually something relatively high-level or language agnostic — which is when I would have to "understand what I'm trying to do" — chances are indeed higher that I'll find a solution in Python, than that I'd find a solution in OCaml, but the thing is, I don't really care what language I'll find it in, as long as I am able to read it. I just have to get the idea, then I'll write it in any language I can write.
One might respond that "well, not being able to copy-paste it is the all difference it makes", but, seriously, there might have been like 2 cases in my entire life (that's 15+ years of programming) when I just copy-pasted something from stackoverflow (I think I actually remember those cases — these were indeed very specific situations, some stupid language quirks, and workarounds for them really should've been implemented in the standard library; and TBH, I didn't even really care how they work, as long, as they work — these were not your typical programming problems). Otherwise, I just don't find it very applicable: there's always some difference between stackoverflow solution and what/how you want to do. So you read the code to get the idea, then you go and write it yourself.
Ok, there are also CSS problems, I copied styles plenty of times. But that's different. And I have to change colors and stuff in the end anyways.
You need a VERY good reason to use anything except TypeScript/C#/Java/Golang/Python/React/Vue/Postgres/MySQL/SQL server/Oracle. Perhaps Rust. These technologies are good enough to get almost anything done these days. There's exceptions of course for example games tend to written in C++ and embedded is often C.
Apart from anything, you should be using these most popular technologies if only for the sake of recruiting.
Using less popular technologies like Erlang/Dart/Kotlin/Ruby/Elixir/OCaml/F# or whatever weird new JavaScript React alternative thing got you interested lately is a bad idea not just for recruiting but for support and community and documentation.
If you are the person deciding which technologies to use, you should probably be using the most mainstream thing you can, not the coolest newest thing that you read on Hacker News. There's any number of companies saddled with their main systems being built in the weird assed framework that the fourth-to-last CTO decided was a good idea, and those companies are now stuck with the problem.
I should note of course that my comments refer to company/organisation development. For personal projects or fun or whatever you should do whatever the heck you enjoy.
Sure if your value add is content then go ahead and use mature tools within the paradigm, but if you want to cause a so called "paradigm shift" then you'll need to understand where the progress is happening and what kinds of opportunities it creates.
Ocaml for example is looking more and more enticing. Standard meta language is used by academics and programming language theory is developed in it. Meaning that it has a good long term trajectory (along with lisps I suppose).
Of course we are about to grow out of syntax, soon it'll just be another config param in your editor.. but I don't think these "obvious choices" you list will all be as well positioned w.r.t. that change.
Right now it may be harder to agree with me than with you, but that makes me think of a hn thread I was reading recently where people didn't want to admit to being programmers (in public / to strangers) because the perception is starting to be that what we do is immoral. Sufficient mastery of programming will make it a boring thing that everyone knows how to do but lowering the bar to that point won't happen within the web paradigm we currently inhabit. We'll see if wasm brings us closer but I think it will take more than that.
Anyway, I'd say your advice is good but not great. A CTO should be able to assess which tools fit the problem they have for the timescales they're considering. If they're swayed by your comment (or mine for that matter) then they're not fit for the role. The person you are actually talking to is someone who is building a company that suffers tech while the core business is something else or a company that is meant to be sold to some giant.
This is the most Hacker News thing I read all year. What are you talking about? Where did he say anything about wanting to cause a paradigm shift?
Facebook was PHP.
Google was C++.
Bitcoin was C++.
Netflix was Java.
Spend your innovation points on your product, not on programming language.
Most Telcos, what’s app used Erlang.
Apple used Objective C, and built its own language.
Microsoft used C++… and built a series of languages.
Most of the web programming was in flash… until suddenly JavaScript won out.
Except for Figma which uses WASM based stuff.
Spend innovation points on your product… but sometimes innovative products require innovative ways to built it.
Nokia Networks customers were using a mix of C++ and Perl running on HP-UX back in 2004, and nowadays it is mostly C++ and Java running on Linux distributions. Not every telco is using Siemens Erlang based switches.
Apple created Clascal and Object Pascal, migrated to C++, got Objective C via NeXT acquisition, which previously licensed it from StepStone. They also created Mac Lisp, Hypercard, Dylan and Newtonscript.
Microsoft used BASIC for a looong time, dabbled with Pascal, had one of the best macro assemblers in the market, was the last MS-DOS vendor to actually add C++ support to their C compiler, focused on VB and C++ until .NET came to be.
I've never in my life done anything that I feel standard languages aren't a good fit for.
I do think Dart deserves full best practices status, because the tooling and ecosystem around it is fantastic, and because it doesn't have a bunch of "Outside the paradigm" stuff, it's all things you can learn in a week coming from Py/JS/etc.
Runtime errors.
I'm not exactly sure what the slowness people talk about is. Even the most bloated of websites are fast.
The one thing that still is an issue is Android load times. It gets a little excited about killing background apps on my phone and will take 10 seconds to open my notetaking app again.
any chance you could find and link to that thread?
I'm perfectly happy letting other people work in the middle of the bell curve, but I cry a little inside when I see a super cool application be ruined by highly conservative software thinking. I have never been able to understand that, usually hardware-oriented, companies will be doing something super advanced and novel with physics, engineering, biology, and other "hardware" related things, but then will bury their heads in the sand unless the most common denominator programming language is used because they supposedly can't hire people otherwise. But yet they're perfectly willing to hire and train people on the novel hardware designs. It doesn't add up.
There is a very strange uncomfortability with software ideas that are new to people that I do not see when it comes to even the most novel and cutting-edge hardware-related topics. I have experienced this in internal talks, where hardware-related talks will generate a huge amount of buzz and questions, despite often being well beyond the audience, and the software-oriented talks seem to attract crickets. Honestly, I think it's a bit of hidden hubris, in that many scientists and engineers consider themselves to understand software, and in showing interest in new software-related things, they fear showcasing that they don't know something they fancy themselves as knowing. The other possible answer is that people are just afraid of software in some sense.
I found this in a recent interview where it seemed to be expected to solve a problem using objects and either interfaces or inheritance. I solved the problem with discriminated unions and pattern matching, and there seemed to be some uncomfortability with the solution because it wasn't what they were used to as being the "right answer", when in reality it was just another spot in the solution space of the expression problem.
It's such an insightful phrase.
In general, people are afraid of simplicity. When you show them a technique or programming language or method or perspective or whatever that is new to them but also simplified the problem, people are inherently bothered that it isn’t as complex as they’re used to, which convinces them that it isn’t a valid solution.
But mainstream languages also include C++, C#, Go and many others. It's a good thing to have several different tools in your toolbox, but a few tools can cover pretty much any scenario outside of really extreme corner cases (where something like e.g. Prolog might be of use).
I'm not surprised, it is very difficult to scale Python to larger teams and projects. I mean people have done it to some degree, but at what cost?
It's much better to stick with a static language like Java or C#. You mentioned pattern matching and discriminated unions at the end of your post, which Java has recently gained, and C# to an extent as well.
Its value decreases swiftly the less glue you require, since that is its real niche.
I'm not sure what you're suggesting.
Are we expected to rewrite everything every decade when a new flavor of language comes out?
It seems like, with the exception of Rust, you've named a lot of "lowest common denominator" languages. These languages, while productive, tend to lack expressiveness. It is my opinion that expressiveness is seen as a bad thing in the "professional" community because it takes significant cerebral evolution over the course of a career to learn which tool in the toolbox to use. In other words since the explosion of programming as a career there are more idiots in the proverbial gene pool, and so more companies prefer more idiot-proof languages because the average developer can't help but hurt themselves. This doesn't mean we should prefer "new safe technologies", it means our recruiting should far more stringent and our education far more formal (as in an actual useful programming degree).
I for one would quit if I could program, for example, common lisp and make even 3/4 of my current salary.
Here's, in my opinion, a better and less controversial hot take. Use what works. If you have a team of erlang developers do it in erlang (or whatever). Who cares about the market. If it means spending even more time (and money) learning to write another more popular language correctly it may not be worth the investment. If you build it, they will come. You will have no problem finding an endless stream of developers you can build from the ground up.
As a side note: Kotlin, Ruby, and F# are extremely popular. TIOBE is not a real measure.
I think the ironic thing here is that these "approved" languages are both less safe and less expressive. Statically typed functional languages like Haskell and OCaml allow much more correct code and reject much more wrong code compared to something like Java or Go. I'd even go as far as to argue that in some ways, Haskell is more expressive than the mainstream dynamic languages (Ruby, Python, JS etc).
Now, if your developers are really "idiots" (which to me is a very condescending thing to assume, but that's a different story...), then maybe they won't even be able to get their code to type check in the first place and ship no code at all :)
In functional code, sure. In a predominantly mutable algorithm, you fight the language more than what you gain, and sometimes, yes, the mutable approach is simpler and easier to reason about. Especially local mutability can be very readable/maintainable.
As an IC, I care about the market. I go to work exclusively to exchange my labor for money to support my addiction to food and shelter. When it was time to change jobs as your bog standard enterprise dev, it was much easier to throw my resume in the air and get a job offer by being an experienced C# developer than it would have been if I had spent three years writing software in Erlang.
And most job interviews outside of tech companies where most developers work are not going to be language agnostic nor are they going to have you reversing binary trees on the whiteboard while juggling bowling balls and riding a unicycle on a tightrope.
As a reformed former dev lead, why would I hire an Erlang developer when I could throw a rock and hit a good enough C#/Java JavaScript/React developer to push out some CRUD SaaS app or line of business app?
Idiot proof languages are popular. If you want assured money learn an idiot proof LCD language. In fact, everyone should have one in their tool belt to put food on the table.
However, if you're actually a talented engineer these languages will hamstring you and your art. You will probably eventually gravitate to something more heady (such as the less popular languages) and probably even leave your nice cushy gig to give a professional life in that stack a shot. This isn't, however, to say talented engineers don't exist in lowest common denominator language pools. It's just esoteric/less-used languages tends to cause the best quality of talent to come from them owing from many of their problems. If you can be proficient and productive in a language that you can't easily google a solution for, you're probably an excellent candidate for promotion into the higher echelons.
This is a similar phenomenon to editor choice. My anecdata in a little over 10 years of a career has given me the impression that I can tell what kind of developer someone is by their editor. People who use raw vim/emacs tend to better developers. Why? It's not the editor itself. It's that these editors pull no punches and require time and expertise. That dedication is not taught. The easier an editor is to use for a beginner, the more average a programmer tends to be. Again, there are a lot of very talented developers using VSCode or full blown IDEs. But with those editors your signal to noise ratio is quite low. It's anecdata but mixed with the information above you can gather a lot of "metadata" about a person without much effort.
My anecdata, people who overly focus on language and tools tend to be the worse developers. It's the developers that effectively address the universal problems of writing software people want to use, like api usability, reliability, data consistency, maintainability that have the most props in my book. The best developers I've known weren't particularly attached to any editor, language, or framework.
I think this is an apt analogy. Mostly because carpenters who use hand tools produce more beautiful, unique works of art. When everything you do is on rails (no pun intended) you don't have the flexibility or creativity to make works of art. It's like saying Ikea tables (the equivalent of an idiot proof language) are just as nice to look at and functional as a purpose-driven hand crafted table. I have my doubts, despite using Ikea when I "just need something done".
Nice one, being it elucidates the art being lost in other fields (and perhaps all over).
Serious question: all else equal and without any additional information, between two carpenters who produced the same output in the same time, one with power tools the other without, is there any reason whatsoever to assume one of them is any better than the other?
I'd think manual carpenter is going to have to retire early due to repetitive strain injury.
The same with "easy"/mainstream languages: something like OCaml/Haskell/Nim/Nix/etc. is a power tool with a steeper learning curve compared to something like Python/JavaScript/shell scripting; you being able (and willing) to handle it without abundance of learning resources says something about your mental capacity and potential value as an employee.
Companies pay employees to add business value. Not to get into their own flights of fancy to do things the hard way. As you mature, you learn only to focus on things that “make the beer taste better”.
I have yet to see an argument by any of the proponents of “obscure” languages where their choice adds business value.
And the “hard problems” that are being solved by the large companies at a scale that has never been solved are doing so by using mainstream languages.
I’ve never seen a report of a job interview where they asked you to reverse a binary tree in Erlang.
The vast majority of problems that developers are being asked to solve are not that hard technically. They are business problems.
You saw that whole spiel about my desire to exchange my labor for money to support my addiction to food and shelter?
> However, if you're actually a talented engineer these languages will hamstring you and your art.
I have no desire to be a starving artist. I turn requirements into code so businesses with money will give me some of it by adding business value. I don’t program to create the next Picasso.
I stopped considering programming “fun” after doing it for 10 years across 4 assembly languages (65C02, 68K, PPC, x86) before I graduated from college in 1996.
> and probably even leave your nice cushy gig to give a professional life in that stack a shot
So tell me again why I would leave my “cushy gig” (and it is the cushiest gig you can imagine in any BigTech company)?
> you can be proficient and productive in a language that you can't easily google a solution for, you're probably an excellent candidate for promotion into the higher echelons.
Every single leveling guideline I have seen at any tech company doesn’t mention “ability to code in an esoteric language well”. It’s all about “scope”, “impact”, “managing ambiguity”, etc. “Coding ability” really only comes into play from junior to mid. After that it is about system design even at the interviews.
this makes me sad to hear. I fell in love with programming at age 7 and still love it at 32. I'm extremely fortunate to enjoy something that pays well, rather than languishing at a cushy job that leaves me empty.
> Every single leveling guideline I have seen at any tech company don’t mention “ability to code in an esoteric language well”. It’s all about “scope”, “impact”, “managing ambiguity”, etc. “Coding ability” really only comes into play from junior to mid. After that it is about system design even at the interviews.
if you're hiring plumbers, sure. it's not all plumbing, though. there's algorithm design, compiler engineering, formal verification, program synthesis, numerical methods, etc. etc.
the really effective people in those fields use (or make) weird languages. Isabelle's written in HOL, Coq in OCaml, Agda in Haskell. having a knack for weird languages is a plus for brainy jobs working on that kind of stuff.
My job paying well allowed my wife to buy a vacation home/investment property for the winter and starting at the end of the month fly around the country and stay in mid tier hotels and do the whole “digital nomad thing”.
I spent the first fifteen years out of college having a great time outside of work as a part time fitness instructor (more of hobby) and training and running with friends.
Sure I’m learning a new language now - Spanish.
Making sure that you actually enjoy those hours has a massive impact on your quality of life.
For an extreme example, what pay cut would you be willing to take if you were able to do fitness training full-time?
> My job paying well allowed my wife to buy a vacation home/investment property for the winter and starting at the end of the month fly around the country and stay in mid tier hotels and do the whole “digital nomad thing”.
This is somewhat off-topic and I don't know you or your wife personally, but I find it flabbergasting that a spouse would choose to do the "digital nomad thing" when their partner can't or won't follow them. Even more so when they're being bankrolled by said partner.
Early in my career I thought of software as art. I was wrong.
The very last thing I want in any production software team is an artist looking to express themselves. I want the worlds most talented engineers who want to use consistent proven methods to create solid maintainable code with zero surprises.
Code as art has its place, granted, but that place is in the privacy of your own time in a repository with one single contributor. I occasionally still go back to writing lisp for fun, but it has no place in production.
The very best engineers are like artists, in that they harness their creativity to solve problems efficiently and effectively, often in innovative and personal ways.
And artists who are respected in the field of software can use consistent methods to produce solid maintainable code. I wouldn't say "zero surprises" though, I'm often surprised by reading the code of an artist, how they achieve extraordinary results with mundane code that a child can understand.
The example that comes to mind is Fabrice Bellard. He's one of the most talented engineers - and I'm sure many of us would agree that his software is a work of art.
Well, as someone who has to manage a team, I completely agree that what's needed are engineers who can consistently produce predictable results. We don't want someone who chooses (or worse, creates!) an esoteric language to pursue their art. But I myself am of the latter persuasion, "writing lisp for fun". And having a team of only non-artistic engineers would be so boring. But then again, boring is what we need most of the time.
As a reformed former dev lead, I wanted a consistent industry standard idiomatic method of writing code and I used a combination of static analysis tools and code reviews to establish a culture to do just that.
I don’t want my C# developers who came from Java writing an AbstractFactoryFacadeBeanProxyDecaratorSingleton.
“Fun” for me is doing anything except being in front of a computer after hours. Between time with my wife, exercise, learning Spanish and just vegging out, computers are the last thing on my mind. I don’t even have a personal computer anymore.
That reminds me of an excerpt from this humorous (but still relatable) bit of writing: https://www.stilldrinking.org/programming-sucks
> Every programmer occasionally, when nobody’s home, turns off the lights, pours a glass of scotch, puts on some light German electronica, and opens up a file on their computer. It’s a different file for every programmer. Sometimes they wrote it, sometimes they found it and knew they had to save it. They read over the lines, and weep at their beauty, then the tears turn bitter as they remember the rest of the files and the inevitable collapse of all that is good and true in the world.
> This file is Good Code. It has sensible and consistent names for functions and variables. It’s concise. It doesn’t do anything obviously stupid. It has never had to live in the wild, or answer to a sales team. It does exactly one, mundane, specific thing, and it does it well. It was written by a single person, and never touched by another. It reads like poetry written by someone over thirty.
> Every programmer starts out writing some perfect little snowflake like this. Then they’re told on Friday they need to have six hundred snowflakes written by Tuesday, so they cheat a bit here and there and maybe copy a few snowflakes and try to stick them together or they have to ask a coworker to work on one who melts it and then all the programmers’ snowflakes get dumped together in some inscrutable shape and somebody leans a Picasso on it because nobody wants to see the cat urine soaking into all your broken snowflakes melting in the light of day. Next week, everybody shovels more snow on it to keep the Picasso from falling over.
If you look at the leveling or hiring guidelines for any major tech company, what separates “senior developers” and up from mid level developers are system design, “handling ambiguity”, leadership, “scope”, “impact” and in the case of Google did you write a messaging app.
Even the largest tech companies realize “coding ability” only gets you so far and most developers who want to get ahead would be far better off focusing on the other aspects of software engineering.
Coding has little to do with handling ambiguity.
While I have never been through a BigTech coding interview, I have been through (and passed) a BigTech system design interview, it has little to do with coding.
Designing (and redesigning) systems for large organizations is my $DayJob where I have to be able to explain those concepts.
Even in C that lacks any form of sane abstraction capabilities, people have come up with object systems and what not if they fit a problem domain better. While I think that the language optimum is well past C, there is no significant difference between modern managed languages in any way besides ecosystems — and that is the most important thing.
Are we really to believe that the average Javascript developer is going to be able to be dropped in an Erlang shop (or any of the other "weird" languages) and be productive any time soon?
I’m sure I could (re)learn Java that I haven’t touched since shortly after it was first introduced in the 90s in a few weeks. That doesn’t mean I would be a competent Android developer.
The average JavaScript developer would be an idiot to ever step foot in Erlang shop if he knew what was good for his career.
My resume was sacrosanct when I was in the enterprise dev world until mid 2020. Why would I reduce my optionality by not using the most marketable technologies?
If the incentive is to ship product then choosing the language you already have a team for makes the most sense.
If you are choosing based on hiring a new team, then the current flavors work. 20 years ago that was Java. Today it's C#. 20 years from now it'll be something else.
If you are a developer looking to grow a resume for the next job, then it's a double-edged sword. Sure it's easier to get a C# gig. But it pays less because you're in a bigger pool. It's harder to stand out. Conversely it's harder to get say a Cobol gig. But it's easier to build a profile in the Cobol community (simply by being under 80 years old) and there is a Lot of work around, and is very well paid.
Equally something that's marginally popular now will have a long tail and can be very lucrative. Erlang might be obscure, but there are plenty of shops who would love to pick up another experienced, capable, erlang developer. You're a bigger fish in a smaller pond.
So yeah, language is like most things, dependant on your point of view. That's why we gave so many of them.
BTW, what languages do you think all of those BigTech companies that pay well are using?
I just keep bringing up C# because that’s the language I have the most experience with. But substitute $any popular language.
Even OCamls share would be bigger within big tech, thanks to Meta.
(and I say this as a big fan of OCaml)
also note that Jane Street does everything in OCaml. I can't believe it's bad for their employees' careers. probably because they're not looking for the same jobs as the average JavaScript pleb.
Work is not only about money for me. My best work environments have been a small team of skilled people tackling a big problem. For this we would use whatever is the best tool for the job, regardless of its outside popularity.
It's a fundamentally different ask to learn Haskell, datalog, SaC. You are actually learning a new language instead of just the flavour of the week imperative programming.
What good is a language in 2022 without a complete ecosystem of frameworks for most jobs?
Libraries cannot change that basic fact - there are just problems it will be extremely unsuited for.
Java has some of the same problem by the way in reverse. (Package handling, forced garbage collection and unknown real time and memory usage characteristics.) The difference being that Java's core has much less important opinions about algorithms, while Haskell tries to make everything functional or it is awkward.
So, while Haskell will be hard to use for problems best described in an imperative way (in addition to other issues say Java has), Java will only have serious problems where memory and runtime determinism are paramount.
It so happens that a lot of the programming is done in imperative way. Including the libraries.
The last time the third party Haskell SDK for AWS was updated was in 2014. I do see a third party GCP SDK. But if GCP and Azure works like AWS, as soon as a new API is released by a service team, all of the officially supported SDKs automatically get updated.
I am sure there are other service providers that have SDKs and code samples for popular languages.
Now the real stuff that can cause problems is bad tooling and lack of support. You cannot code your things when you're trying to fix the compiler, build tools or the debugger.
Sure you will. There’s no “Android developer”, there’s Java/Kotlin developer who uses Android SDK.
Who would you rather lead the development of your Android app? Someone with no experience with Android or someone with previous experience.
It also means you’re competing in a much smaller market and people looking for strong Erlang developers will be suddenly very interested in you specifically, because it’s tough to find strong candidates with this expertise.
It also might mean (depending on your interests) that positions that are open are in a more intellectually interesting problem space, because boring problems tend to be solved in the lowest common denominator languages, and if an unusual language is chosen, it might be chosen because it’s a being used in a unique context.
As in, reductio ad absurdum, “if only I had been working in Java, I’d be safe, but because I worked in Ruby, I am going have to go flip burgers, as no one will let me near their precious production code now?”
I mean, yeah, ok, there was the dotcom bust, and I suppose another could happen at any point, but somehow I get the impression that you’re arguing that using any language except the most mainstream option (whatever that might be for a given industry) is too risky? Or am I misreading?
But in the boring enterprise dev world where I came from especially during the latter part where I was specifically being hired to lead initiatives, of course they wanted someone with relevant experience.
If you want top talent then you've got to offer something they want; sure you can always pay more, but past a certain point that might not be enough, plus it gets expensive. Using better languages is one of the most effective ways to get noticed by the candidates you really want.
When I was in the Enterprise/Corp dev world until a couple of years ago, I could call a few recruiters and have 8 interviews and two or three offers within less than a month. It’s easy to pattern match when you use a popular technology.
Or even the same amount of money when the pay/bullshit ratio starts going in the wrong direction.
You realize all of the BigTech companies use the same “boring languages” don’t you?
I'm zero worried about it as it's never been an issue.
If you’re being hired to lead developers and projects, don’t you think you need to know the technology you’re leading?
- back end development in a few popular languages
- about an average “data architect” for lack of a better word. I’ve led implementations on every type of database imaginable including ETL type jobs and online systems.
- “DevOps” (at least if you give me an AWS account) including setting up networking infrastructure, logging, monitoring, CI/CD, etc.
I’ve led plenty of pre-sales meetings, writing SOWs, pretty PowerPoint slides and architecture diagrams etc.
The “generalist” is very useful when you need someone to lead projects and to understand how everything fits together. I’ve had to wear all of the above hats at startups. Now I wear those same hats at a cloud provider I’m sure you have heard of. I specifically targeted my current position because I wanted to be a generalist.
I’m no special snowflake. Many of my coworkers who came up the ranks in startups and have similar experience can do the same.
I'd pass on such a position.
Also you talk about only having experience in a less popular language as a death sentence.
I've been only writing Haskell professionally for a decade, but I get endless amounts of interview invites for prior experience.
Out of curiosity I went through some of the better invitations interview process and had no issue getting offers either.
If anything mentioning my professional Haskell experience gets me an offer faster no matter the positions requirements.
I personally hate the clusterfuck of the modern front end ecosystem and would avoid it like the plague. But, if I was responsible for choosing the framework to use, I would choose React any day just for recruitment reasons.
Because of this: "The Python Paradox" [1].
Replace Python (which has become mainstream in the meantime) with any other "weird" language from the article and I think the point still stands.
If it matters I had started learning Python just about when this article was being written/published, and in my early to mid-career that advice of using a "weird" language (Python, at the time) was really good for me, got me into a couple of small companies where I really enjoyed working.
Granted, now I'm already over 40 years of age with a mortgage to pay, I'm a little more flexible when it comes to the technologies being used (even though I would cry myself to work in the early hours of morning were I to use Java, and I'm not kidding), but for people who are quite early in their careers letting them explore and use those "weird" languages will still do them a lot of good in terms of them enjoying their programming work, they might even land on a forum written in Arc.
When I first started in my career over two and a half decades ago, my focus was on being able to be aligned with the market and being able to support myself. I was young, single, had no responsibilities and just moved to a major city. The last thing I considered “fun” was programming.
Yes, you leave money on the table if you do that (I know I did, I have friends the same age as me who earn a lot more than I do because they went the non-obscure language path early in their career), but at the same time you also bring some purpose into your professional life, which cannot be entirely bought with money.
Or maybe I was the weak one when I didn't see myself programming in something like Java for a living for my entire career (30 to 40 years), again, that would have literally caused me to cry before going to work, in which case, yes, those persons that can surpass that type of feeling should definitely go for the "more money/less interesting programming stuff" route.
By 2016, I knew I didn’t want to be “just a developer”. I enjoyed working with customers, leading projects, mentoring and teaching. But I still wanted to stay hands on
I belatedly discovered “the cloud” and realized I wanted to specialize in true “Devops” bringing developers and operations together and working with companies to show their developers how to be “cloud native” (application modernization)
When $BigTech came calling about a pure software engineer position, I really wasn’t interested. I kept talking to the recruiter and she told me about a cloud consulting position where I would be able to be involved in the full life cycle from pre-sales, to delivering a finished product including infrastructure. I jumped at the chance.
If the attitude you're encouraging were followed, these would all have been relegated to unsuccessful research projects and we'd all still be programming in assembly language.
It's weird to me that it's the stubborn languages that seem to make it through.
And they continue to introduce new ML features in the form of pattern matching, ADT, etc.
I think sometimes these languages get unfairly evaluated.
I mean, I don't follow that advice at all, and if you don't want to you shouldn't either, but there's definitely a fair argument that it would be "better" for most cases to accomplish your goal with boring technology.
Considering the popularity of the Android platform and Google's control over it, I don't think it is a bad idea to develop an Android app in Kotlin. According to Google, their Maps, Home, Play, Drive, and Messages apps are all built in Kotlin, and my personal experience is that Android developers like and prefer Kotlin.
Wow if Google is behind it, where do I sign up? It’s definitely going to take off and not be abandoned.
I probably could even write some games I could release on Stadia.
I thought they were fully committed to Dart or was that last week?
Also compiled languages have longer staying power because if you move on from the language, you can still make use of the binaries but simply never write it again. Look at all the Fortran libs that are still in use by other languages...
That's why I don't think it makes much sense to treat kotlin in the same category as the other languages. Sure, it's a programming language, but the way JetBrains executed on it with its easy upgrade path from java and really excellent design, not to mention the toolchain, mean that it's success and trajectory cannot easily be generalized to other "weird languages".
That is because the other option is a deliberately crippled Java from a decade ago. Also, while apps are indeed mostly written in Kotlin for android, I am fairly sure most of Google’s listed apps have a Java shared library that does the core of the functionality that is shared between backend, android, web frontend (j2cl) and ios (j2objc).
Also, don’t forget that android development is a niche, on the web backend side Java is just an incomparable bigger player.
As the article indicates, there's no SO or Google to find solutions easily... You need to read the docs or find some dark corner of the web for help you require. It highlights passion and genuine interest in understanding what you're doing and figuring things out yourself. Whereas your languages are financially job driven... Not curiousity driven; and my issue with that is if you can learn the esoteric languages, the mainstream languages are laughably easy.
I also love weird (/old) languages as the community that exists, however small, are asking 400-level questions amongst each other and not CS-101 topics. There's a nice serenity in not having polluted search results of utter basics.
My favorite programming language is an amazon link. If I can say "I could build this, but it already exists here", I'm happy because I know I've given them something truly professional in a week that would have taken way longer and cost way more to build, plus any random person can work on it and parts will be available on eBay.
Using common languages is just an extension of that.
If someone uses unusual languages, I expect they'll have unusual problems that will become my problem if I'm working with them.
On the other hand, if the task at hand requires a novel approach and using tools that are less frequently used, then that will also be justifiable. Are you developing something that only makes sense to run on the BEAM virtual machine? Go ahead and work with Erlang or Elixir.
Now a third category is programming for enjoyment. In that case you don't work with the constraints of profitability, and you can just have fun. And don't worry too much about Beating the Averages (http://www.paulgraham.com/avg.html)
And with regards to employee retention, I would rather bet big on benefits (paid time off, parental leave, etc.), reasonable working hours (4 days per week), achievable goals, great communication, democracy and good team cohesion. I have a feeling this works for a lot of people. If a language is the only thing that makes you stay, by all means find a place that truly makes you happy in that regard. All I am saying is that there are a lot more variables to worker satisfaction.
Those are important factors also. But I would prefer to work 5 days per week and enjoy my work rather than working 4 days and not enjoying it because the PL sucks. Just my 2 cents.
Yeah, I would like to see a source on that.
I'd wager that most of the remaining PHP sites are wikis and legacy applications that are too painful to port.
The article even concludes with: "PHP is far from dead, no matter what any disgruntled developer may tell you. After all, 79.2% of all websites in the world can’t all be wrong, and most importantly, PHP’s market share has remained relatively steady throughout the last five years (oscillating between 78–80%). Few programming languages command that type of staying power."
PHP powers a lot of legacy code bases, yes. But there are also a lot of job opportunities in Laravel and Symfony which are both very good frameworks.
How are you getting that number? From the link you referenced, the percentages are Wordpress: 40%, Joomla: 2.6%, Drupal: 1.7%
It's getting ever harder to find good PHP developers.
PHP will be around forever, but it's getting less popular.
I promise, Oracle (the company) is a good reason to use anything except Oracle.
On a more humorous/worrying note, there's also this: https://news.ycombinator.com/item?id=18442941
And you’re doing a grave disservice to Elixir at the least. I prefer Erlang myself, but Elixir has established itself as a robust choice.
I haven't had the same luck with frontend. There's so much magic, config file hell, and other rough edges that you need someone who knows the framework. In the JS world, actually writing code is maybe 50% of the work, and managing the ecosystem (config, build, packages, etc.) is the rest.
If you only stay with what is popular nothing new becomes popular.l and you become mediocre.
Popular isn’t always the right choice. There’s the situation things are only popular because they are popular. React seems to fit that now, it’s the default as everyone else is using it even if there’s newer alternatives.
Innovation only happens by doing things different.
Choose what is appropriate, not what is popular or what is new.
The three you mentioned got over the hump by corporate backing. In particular Rust got in force thanks to Mozilla, golang to Google and TypeScript to Microsoft. Big guys sometimes make an abject irrelevancy or failure (e.g. F# which didn't quite catch on, old stuff like Visual Basic) but usually at least the support and visibility is there.
Additionally the standard request model of PHP (like with PHP-FPM) is a fast, efficient, and easy to learn model of request for new developers. Easily scalable new processes that are cleared at the end of the request. It seems like this is something people try to emulate with the “server less” model but PHP was built for this and is quite efficient at it.
And it's not even true that Haskell cannot be on that list for any sane human. Admittedly, it's not on MY list, but that's just me. Popularity isn't the end of things, nor is it set in stone. Agda or TLA+ aren't very common, but neither are problems they are meant to solve. Neither is Verilog, but it's not even an alternative to anything popular. And Ruby wasn't popular before Rails. Then it was, then it wasn't again. I thought that I was done with Java, but then Android became a thing. I guess you get the point.
…I think I'd like if there was only 1 language for everything, but I don't think it's even remotely possible, because then there would be different dialects of that EsperantoPL, different frameworks or ways to use it, and people would never agree on 1 thing anyway.
All the world is not a web app...
Yeah, like for instance: nobody knows or wants to know PHP.
A language of a somewhat more sophisticated design can make it harder to find developers but let you need much less.
E.g. Scala (which, contrary to the myth, has great learning curve and readability as long as you don't insist on making heavy use of the really weird parts - they are entirely optional) vs Java can easily boost productivity 10 times. Scala code usually is less verbose and works perfectly once built successfully - ~99% errors are detected at compile time. I know numerous Java devs who have switched to Scala to solo-dev efficiently, because they have no time to code and debug Java. Kotlin was designed based on the Scala experience to make it even better.
WhatsApp, Facebook Chat used Erlang, and Discord is still using Elixir… make of that what you will, I suppose.
And Ruby / Rails + your frontend of choice is still a ridiculously productive stack to bring up an app, and probably run it at any scale you’re likely to realistically hit (poster child being Shopify)… if you ever get to stage of “scaling problems”, you are at a stage where you’d be rearchitecting parts of your stack regardless of what your original implementation was in.
So in sum, choosing a particular language because of popularity, I think, is not particularly useful framing. I’d say, choose one because it either gives you joy to write in and maps to your thought process well, or because it has a particularly strong ecosystem for the subject matter. Life is too short to program every day in a language that you dislike just because you think it’s the “safe choice” :)
I also wonder how we can define popularity better. Does that mean industry acceptance, number of GitHub repositories, number of StackOverflow questions, number of libraries, developer satisfaction surveys, etc. If you choose different metrics here, different languages and frameworks will appear popular. Svelte for example seems to be on top of some developer satisfaction surveys, but React is still one of the number one choices for frontends. C is the industry standard for embedded, but developers often do not enjoy programming in it.
Yeah, there is always a balance to strike and a multitude of factors that might lean the decision this way or that…
And even in something like embedded it seems like there is movement, I have seen some posts about people using Zig or Rust or Nim for embedded programming for example.
Not impossible to reverse but very hard, especially since Ruby only has once niche and has not been doing well there.
I haven't had a problem finding Ruby devs, but I haven't had to hire in a couple of years.
It still seems pretty relevant and useful.
When I started the main project I am still maintaining, react wasn't even around yet. It started only 9 years ago, which might seem like a long time to some younger folks, but feels like yesterday to me.
Are you suggesting that languages and frameworks are 'solved' now? That we won't get a new react that changes the ecosystem? How will a new language or framework that makes things easier ever come about if everyone follows your advice?
It just somehow fell behind on the hype curve, mostly because Ruby itself wasn't used for anything else than Rails. Python took its spot in most general use cases.
I'm going with this as the problem statement, and it is a problem, but I submit that being saddled with a technology is a cultural problem, not a technical one. Related: Conway's Law Any organization that designs a system will produce a design whose structure is a copy of the organization's communication structure.
> If you are the person deciding which technologies to use, you should probably be using the most mainstream thing you can, not the coolest newest thing that you read on Hacker News.
This solution does not address the problem statement, and so will sometimes be a good answer, but only by accident, and makes the same mistake as choosing "the coolest new thing on Hacker News". Choosing a technology to address a specific challenge is not always easy or obvious, but takes thought, humility, consideration, familiarity with the options, probably even a team decision. A manager that just top-down decides for the engineers is doing it wrong, whatever they choose.
There's actually a tricky tradeoff here. Many startups working on hard problems can benefit from making one weird technology choice, if it offers them some kind of significant leverage on a previously difficult technical problem.
But when it comes to recruiting, it can actually be an advantage to be using a slightly obscure language. Often, these languages have communities of very skilled early adopters who wish they could use their favorite language at their day job. And especially if your company has a strong remote culture, this may make it possible to hire some extremely talented people.
I do agree that, on average, a company's overall tech choices should be mostly boring. But knowing when a lesser-known tool will offer a big advantage is an art, and it can pay off.
If it's an issue with existing devs refusing to skill up, they can just write their ancient antiquated Java until they retire, it'll still work just fine alongside the new Kotlin code. But in my experience it's rare that even the most institutuonalised Java dev doesn't appreciate the nullability support at least.
However I also think, that time should be spent in non-mainstream languages to learn new programming concepts, and eventually future version of "X, Y and Z" might even get those concepts and thus one is better prepared to apply them.
(But then again your list is also kinda weird. I mean, seriously, it has React but not C++?)
Come out of the reality distortion bubble, please.
This has naturally led me to prolog, but this is a very scary proposition for me to try and sell to the company though they have been very supportive.
It's a powerful tool but just so esoteric and I worry it'll be a pain to build a production grade system that can be worked on by someone other than myself.
Though trying to introduce clojure, as much as I enjoy it, would just be adding to my social woes :).
> Passion fades, but you’ll always need a job.
No and no.
The original post was about having fun with weird languages. If it were a post about windsurfing, would you advise people to check the availability/pay of jobs for programming languages/frameworks instead of going windsurfing?
> offer suggestions about the best course of action to someone.
For example... by playing with a weird programming language purely for the joy of the craft?
You can do programming outside work, you know.
Anyone else read this and feel really old?
As a former Erlang developer it never ceases to amaze me that an entire language, standard library, toolchain, and runtime that's entirely dedicated to and on-paper perfectly technically suited for the most pervasive "backend" development challenges of our time somehow managed to effectively blow a 20-year technological headstart and failed to leverage the notoriety that should have come from several super high-profile "trendy" commercial use cases in the 2006-2013'ish era. Such that it's still relegated to general obscurity and is seeing its core competencies taken over by a hodgepodge of other languages and technologies that started much later but became rapidly more popular while also still arguably doing a worse job at those things than Erlang did.
I showed it to all my developer friends back around 2008 (I found out about it because a competitor used it and open sourced some of their stuff) and the only comments I ever got was how weird it looked. No one gave a shit about anything else. The story it told me wasn't about sales, it was about how shallow most developers are.
Once nodejs came out it was the final nail in the coffin - callback hell solves all your problems, no funny looking language necessary!
On the JVM you have languages like Clojure and Scala, which both are top class in their domains imho. I wish there was the same for the beam.
I wish clojerl were more than just someone's side project.
I simply like to put in a lot of focus during certain times to make the compiler understand what I'm trying to do and then go to "autopilot" later and have the compiler tell me exactly all the places I have to change (and often how) when I implement something new or fix a bug.
I actually really enjoy the assertive style of Elixir/Erlang. I think that while they are dynamically typed languages, the assertive style rests somewhere between dynamic and static typing, and in fact offers some safety benefits over your average statically typed language: while you don't get it at compile time, this idiomatic code offers benefits at runtime that most people don't bother with in other languages.
Maybe for example you have a good memory and I don't (I certainly don't). I forget things so quickly that it's always a huge hassle for me to be productive when I have to use e.g. python. That's just one example, there are surely other different traits of people that make them prefer one over the other.
Another one is that I really hate to write documentation and tests, except for very highlevel ones (UATs and high level documentation). The reason is that it gets outdated quickly and I don't like to keep it aligned. With types, they are automatically always aligned (the compiler forces me to) and it's easy to do so because there's lots of tooling for refactoring types.
Maybe other people actually like that part of the job and hence don't feel that a typesystem is helping them much.
For instance, TFA suggests sitting down with a pot of coffee to read the language docs sequentially (they were written by a hermit). This is also a great way to try to familiarize yourself with a mystery system.
The author recommends paying attention to building your workflow, since you'll be figuring things out as you go and the cost of forgetting details is high. I've found the same to be the case when working on integrating unfamiliar systems: early investments in automation and testing pays dividends.
The one innovation in it is the borrow checker - making it somewhat dependent on the quality of the compiler and adding a bit of noise to syntax for exchange in predictability of the code - and the cargo packaging system, unusual for a statically typed fully compiled language.
If you have so little awareness of the Scala ecosystem that you don't realize how laughable such a remark is in 2022, yet allow yourself to have such a strong opinion on the language, I have less than zero interest in the rest of your opinions about "weird languages".
Just gonna point out you didn't keep your cool and ignore it.
Keeping your cool: good!
Ignoring it: no way!
You obviously have a lot of passion for the topic, and may have rightly identified a flaw in the author's blog post. You can use that passion - and keeping your cool - to correct the record.
e.g. I dunno OP is wrong and Scala is not a mess, it is awesome! That culture war was resolved in favor of cats years ago, and here's why...
I don't know Scala though, so perhaps your argument would make more sense to me if you explained why they were so wrong.
I'm tired of people who never really used Scala or haven't used it in years casually shitting on it like it's a cool thing to do. Like "Scala is a mess" is something self-obvious that doesn't even need any explanation / justification.
And Scala aside, it's pretty amazing that a blog post that can be summarized as "be a normie, being weird is expensive" is at the top of Hacker News. Such hackers we are.