Skip to main content

A short comment on the future of programming languages

I've caught some recent articles and commentary asking a basic question of "What's next for programming langauges?" and I though I'd make a quick and short stab at a guess.

Considering a few elements to the soup that I think are key: the rise of dynamic languages and rapid development, the prevelence of the internet spreading word and use of multiple APIs and frameworks, and an increasing need for portability over a range of targets. I think this will lead to one inevitable move in software, but who makes it is anyone's guess.

We're going to see first one, and then many, dynamic, binary-compiled languages. We'll see things that allow two games to be written, one using Direct3D and one using OpenGL, and to compile them for the same target, using either. We'll see the ability for compilers to restructure the original code in such a way that library APIs will be more than calls to link to, but templates that will portray the intentions of the progarmmers and be able to adapt them to the target in question.

I call this "Hard Linked Libraries", but I'm sure a dozen names will surface. Python could make moves toward something like this, I'm sure. But my guess is that eventually something will surface in .Net to do things along these lines, probably using or extending generics.

I'll post more, and maybe some mockups. What do you think? Is this likely or feasable or stupid?

Comments

Popular posts from this blog

On Pruning Your Passions

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…

The Insidiousness of The Slow Solution

In software development, slow solutions can be worse than no progress at all. I'll even say its usually worse and if you find yourself making slow progress on a problem, consider stopping while you're a head.

Its easy to see why fast progress is better: either you solve the problem or you prove a proposed solution wrong and find a better one. Even a total standstill in pushing forward on a task or a bug or a request can force you to seek out new information or a second opinion.

Slow solutions, on the other hand, is kind of sneaky. Its insidious. Slow solution is related the Sunk Cost Fallacy, but maybe worse. Slow solutions have you constantly dripping more of your time, energy, and hope into a path that's still unproven, constantly digging a hole. Slow solutions are deceptive, because they still do offer real progress. It is hard to justify abandoning it or trying another route, because it is "working", technically.

We tend to romanticize the late night hacking…

Why I Switched From Git to Microsoft OneDrive

I made the unexpected move with a string of recent projects to drop Git to sync between my different computers in favor of OneDrive, the file sync offering from Microsoft. Its like Dropbox, but "enterprise."

Feeling a little ashamed at what I previously would have scoffed at should I hear of it from another developer, I felt a little write up of the why and the experience could be a good idea. Now, I should emphasize that I'm not dropping Git for all my projects, just specific kinds of projects. I've been making this change in habit for projects that are just for me, not shared with anyone else. It has been especially helpful in projects I work on sporadically. More on why a little later.

So, what drove me away from Git, exactly?

On the smallest projects, like game jam hacks, I just wanted to code. I didn't want to think about revisions and commit messages. I didn't need branching or merges. I didn't even need to rollback to another version, ever. I just …