AstonJ
In an age of AI, what can programming languages do to survive/compete?
Inspired by @jdiago’s post containing this slide:
I thought it would be interesting discussing what independent languages like Elixir, or those that are not created by FAANG (or whatever the AI equivalent might be) will be able to compete/survive/stay relevant, assuming, for the purpose of this thread, that the AI industry ends up being like pretty much every other industry in a capitalist world:
- In the beginning there is ‘healthy’ competition (where most languages will probably be treated well as the companies will be competing for customers/users).
- Over time smaller companies are acquired/swallowed up/go out of business (some languages may begin to get neglected or dropped at this stage).
- Eventually you end up with a small handful of companies who essentially control the market and more or less dictate what you’ll use (based on what we’ve seen from big tech already, probably their own or very closely affiliated languages).
I realise there could be lots of different outcomes but for the purpose of this specific thread (and in the interest of being prudent) let’s assume the above pans out - what can programming languages do to stay relevant/survive?
Most Liked
sodapopcan
I’ve made this joke a couple of times (hopefully not on the forum yet) but I like to imagine a future where AI slop has gotten out of hand and someone says, “Maybe we should come up with some kind of deterministic language to program computers with and we can all learn it—like a “programming language” if you will.”
DaAnalyst
I’m more in favor of thinking about what different approach we’ll need to organize and supply the requirements and solutions to the AI assuming they manage to pull it off beyond the surface.
The problem “vibecoding” faces is not a translation from ideas/requirements to code but from the problem domain to the solution domain. Who’s going do the work in-between if not humans? When a client or a business analyst unload their requirements onto developers, it’s a two way communication from then on, and not just a multiple-choice question. It is about finding the problem behind a problem that saves the day, not translating a solution into code.
Given the way the LLMs currently work, I simply don’t find it feasible for them to pattern match their way out of such situations, no matter how large the “model”.
And don’t get me wrong, I would love so much for the “AI” to be way smarter and help me more than it’s currently capable of. The bitter taste I’m left with after spending a considerable time hoping it will get me somewhere, and then resorting back to my own human intelligence feels so bad, like a complete waste of time. After a couple of such wasteful disappointments it takes me time to dare try again.
AstonJ
It’s just one possible scenario based on what’s happened in other industries - a few companies end up controlling the market, and from what we’ve seen of big tech, they sure do love their own languages/frameworks; if they control the tools they can ultimately control or influence the competition to some degree or another.
Going back to what independent languages can do, Elixir (and languages like Ruby) already have a head start in this imo - by being intuitive, natural, easy to use, and beautiful.
-
If people enjoy programming in a certain language then this could be one way to remove reliance on AI and AI controlling firms.
-
If a programming language is easy to use (like being intuitive and natural) then again, there could be less of a reliance on advanced AI/firms controlling them.
-
If a programming language brings you joy, whether from the process or by just being beautiful, again, there could be less reason to want to use AI
In summary: in all this hype and excitement around AI focusing on things that might draw people into using the language directly (or with a very light sprinkle of AI) might be a real lifeline/advantage ![]()
Popular in AI / LLMs
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance










