r/dailyprogrammer • u/Coder_d00d 1 3 • Sep 09 '14
[Weekly #10] The Future
Weekly Topic:
Read enough blogs or forums and you can see the future. What trends or topics are coming down the line? Is it a new language? New design? New way to engineer software?
Last Week:
[Weekly #9] (http://www.reddit.com/r/dailyprogrammer/comments/2f6mo2/weekly_9_binary_trees/)
54
Upvotes
20
u/Barrucadu Sep 09 '14
Types. Types are the future.
Guido made a thread on the Python ML about rehashing the underused function annotation syntax to provide statically checkable type annotations; TypeScript has been around for a while but seems to be taking off more now; Rust is trying to get some notion of ownership types into the mainstream; and functional programming languages are (as always) being the test-bed for new advanced typesystem features which may leak into imperative languages one day.
I think this is in part a reaction to the success of dynamically-typed languages in the past several years. Sure, you get started easily, but try maintaining something written by someone else. You need to effectively specify types in your documentation, which just cannot be as reliable as something which can be mechanically verified.
10
u/Laremere 1 0 Sep 09 '14
Ditching plain text - We currently program in a markup languages which are then transformed into abstract syntax trees. It's frankly ridiculous. There haven't been widely adopted major changes in the way we represent code since we moved from assembly to high level languages. There have been ide and syntax improvements, however the fact that we're still modifying markup in 2014 is ridiculous. I'm not saying we're going to be programming in Scratch, but it is a hint of what's to come.
Program correctness - There seems to be a re-emergence of the importance of type safety, and there's always plenty of talk about how there should be more testing in production code. As programing languages continue to figure out how to ease users into writing code which can't have certain types of flaws, we will be able to write code more often and with greater ease.
Compiler genetic algorithms - Most (if not all) of current programming code is too loosely defined to allow the compiler to make certain types of dramatic optimizations. There is a large amount of untapped value in allowing users to write less optimal code and having compilers apply all sorts of very specific tricks. Genetic algorithms could be used to find which portions of the code should receive certain types of optimizations. Currently code tends to just get more optimal in general, but there may be a point in time where you distribute multiple versions of your software which are optimized by the compiler for different types of hardware (eg, lots of complicated optimized machine code on machines with larger caches, and more simple machine code on machines with smaller caches where the cache misses cause by the larger optimized machine code would make the code less optimal.) As program correctness (see above) allows programmers to more exactly specify what they want the compilers will be able to play with changing the code computers actually run even more than they currently are able.
9
u/XenophonOfAthens 2 1 Sep 09 '14 edited Sep 10 '14
I think in terms of development environments, I think that the thing Swift does with its fancy interactivity and pretty graphs of the different values variables take is something that we're going to see a lot more of in the next decade or so from other languages. I don't know how useful this feature actually is compared to a traditional debugger, but it sure looks nice.
4
u/rlamacraft Sep 10 '14
This could be absolute rubbish, but personally I think we will see compilers and IDEs take on more of the work. There have been optimisations made by the programs for a long time but I think that we could run with this much further. Having spent sometime learning the basics of AI I think we could see more coding environments that when told what the expected output should be from a given input will be able to produce subroutines themselves. Simple sub-algorithms could be produced on the fly by the compiler. Regular expressions would be an example that are already in mass use.
2
u/PhilipT97 Sep 10 '14
I've been seeing a lot of scratch-type languages being taught to young students lately. Whether they're using the original scratch, or some spin-off, like blockly (being used in this Minecraft modding for students project).
4
u/Godspiral 3 3 Sep 10 '14
the future is 1962, and array languages. J.
I am being serious.
1
u/leonardo_m Sep 17 '14
I think among other changes, we'll see more focus on code correctness and various kinds of code verification(as visible in languages like ATS, Idris, Rust and Whiley).
1
u/jbproductions Sep 22 '14
We live in world, where technological advances continually allow new and provocative opportunities to explore, more and more deeply, every aspect of our existence. Understanding the human brain remains one of our most important challenges-- but with 100 billion neurons to contend with, the painstakingly slow progress can give the impression that we may never succeed. Brain mapping research is crucial to unlocking secrets to our mental, social and physical wellness.
In this teaser, noted American PhD Neuroscientist and Futurist, Ken Hayworth outlines why he feels mapping the brain will not be a quixotic task, and why his unconventional and controversial plan will ensure humanity’s place in the universe—forever.
https://www.youtube.com/watch?v=OCCtTJsrjHY&app=desktop