Live data from Hacker News

Ask HN: The future of programming languages?

news.ycombinator.com

41–50 of 57 posts

Re: Ask HN: The future of programming languages?

#41

Topics that I think will be important: - Functional Programming - Logic Programming - Managing asynchronicity - Managing concurrency / Managing state - Pruning bad directions in OO (see the first two) - Type Systems - Virtual Machines Languages/technologies that I would look at more closely given these are Haskell, Scheme, Prolog, Clojure, Qi, LLVM. I love JS but as far languages go, I would not look there for new id…

Both your list and your comments look good, generally, but I have to wonder about your mention of logic programming. I think logic programming has a lot to offer the world, in theory, but in practice it seems to be pretty much dead. True, there is probably more going on with Prolog now than, say, a decade ago. But widespread use is not happening, nor is inclusion of logic-programming features into other languages. Fu…

I will make some heretical statements. I think unit-testing sucks. I think current type systems are overrated.

Logic programming + meta-programming as well as Logic programming powered RTEPLs (Read-Typecheck-Eval-Print-Loop) can give us optional rich, strong guarantees without adversely affecting runtime performance. This is a space that needs more exploration.

Re: Ask HN: The future of programming languages?

#44

Topics that I think will be important: - Functional Programming - Logic Programming - Managing asynchronicity - Managing concurrency / Managing state - Pruning bad directions in OO (see the first two) - Type Systems - Virtual Machines Languages/technologies that I would look at more closely given these are Haskell, Scheme, Prolog, Clojure, Qi, LLVM. I love JS but as far languages go, I would not look there for new id…

Data parallelism is something you missed spezially if you think haskell will get bigger.

Re: Ask HN: The future of programming languages?

#45

I think VMs are the future of application programming, especially as manufacturers become more amenable to using "unconventional" architectures like ARM to host full-featured computers. LLVM, the JVM and the CLR all have benefits- I don't see any reason to believe there will be a convergence in the near future. Environments like .Net and the JVM stack will slowly allow tighter and finer-grained interoperability of th…

Those VM designs are pretty heavily skewed towards class-based OO languages, though. Most VMs have some kind of behavior (polymorphic method lookup, unification, message-passing) that they do very efficiently because of the language they target, but others are omitted. For example, it isn't possible to do real tail-call optimization on the JVM without a trampoline, AFAIK. If it had been created for (say) ML, TCO woul…

LLVM is not skewed that way.

Re: Ask HN: The future of programming languages?

#46
The language(s) of future will be fifth generation languages. Current languages are not able to support more than 100M lines of code in one project and more than 10-20 years of continuous development.

In future, we will have something like that:

#... We are wrote large project using HTML7, but HTML8 is just released ...

$ spm update

...

12826 source files will be updated, 2324 new source files will be added, 343 source files will be deleted. Proceed? [Y/n] y

...

Done

#... OK, let continue our development ...

PS.

I have demo. I hate developing in any 3/4GL language now. :-)

Re: Ask HN: The future of programming languages?

#47

Earlier quoted context omitted.

Both your list and your comments look good, generally, but I have to wonder about your mention of logic programming. I think logic programming has a lot to offer the world, in theory, but in practice it seems to be pretty much dead. True, there is probably more going on with Prolog now than, say, a decade ago. But widespread use is not happening, nor is inclusion of logic-programming features into other languages. Fu…

Two visible things to come out of logic programming are Erlang and constraint programming. Both are very significant, in their own niches. I don't think Prolog is dead yet, either.

Erlang is not a logic programming language. They started with a logic programming language and eventually removed every feature that made it a logic programming language.

Re: Ask HN: The future of programming languages?

#48

Earlier quoted context omitted.

Both your list and your comments look good, generally, but I have to wonder about your mention of logic programming. I think logic programming has a lot to offer the world, in theory, but in practice it seems to be pretty much dead. True, there is probably more going on with Prolog now than, say, a decade ago. But widespread use is not happening, nor is inclusion of logic-programming features into other languages. Fu…

Two visible things to come out of logic programming are Erlang and constraint programming. Both are very significant, in their own niches. I don't think Prolog is dead yet, either.

[deleted]

Re: Ask HN: The future of programming languages?

#49
post #47

Earlier quoted context omitted.

Two visible things to come out of logic programming are Erlang and constraint programming. Both are very significant, in their own niches. I don't think Prolog is dead yet, either.

Erlang is not a logic programming language. They started with a logic programming language and eventually removed every feature that made it a logic programming language.

Hence, "to come out of logic programming".

It's declarative, but not an LP per se - backtracking really clashes with the priority on (soft) real-time behavior and concurrency. The Prolog origins are probably most visible in the syntax and emphasis on pattern-matching.

Re: Ask HN: The future of programming languages?

#50

Earlier quoted context omitted.

Those VM designs are pretty heavily skewed towards class-based OO languages, though. Most VMs have some kind of behavior (polymorphic method lookup, unification, message-passing) that they do very efficiently because of the language they target, but others are omitted. For example, it isn't possible to do real tail-call optimization on the JVM without a trampoline, AFAIK. If it had been created for (say) ML, TCO woul…

LLVM is not skewed that way.

Very true.
Post reply on HN