How hard would be?
How hard would be?
https://news.ycombinator.com/item?id=8515987
https://news.ycombinator.com/item?id=11418285
Mention coding by voice and someone will explain how they can’t imagine not using a keyboard, or they bring up the open office problem.
Considering the limited scope, it’s probably just a matter of the proper editor integration.
Intellisense or shortcuts do this up to a level, but the current big IDEs are limited. Maybe some editor with the concept of VIM with a separate command and edit mode would be more fit to work like that.
- Ubiquitous frictionless headphones with built in mics like the AirPods.
- More demand and access to remote working where people are alone at home.
Currently for most languages, we have: "type productions of a particular syntax and try really-really-hard to color between the lines, and subject yourself to the chinese-water-torture of syntax errors till YOU get better at it".
Why not invert that, whether via mouse input, a visual (as in literally, visual, not microsoft-visual) connection, or a text editor that simply doesn't let you type invalid productions. Like Intellisense, but taken to the function or block level. You cannot save the file or even leave insert mode until the code compiles. Or even better, you cannot even temporarily input invalid syntax. From the first keystroke, it inserts a variable declaration, click/type up or down to choose a function call, conrol structure, etc.
Some vim-like integration would go as follows:
command mode:
* <space>+F outputs a function called func1, auto-highlighted for you to rename (or accept default). * <space>+R on the func name lets you set its return type * <space>+A for args, * <space>+B to edit the function body
At no point would you be allowed to input non-compiling syntax. Things like indentation would be non-issues, set uniformly by defaults.
Paper: https://arxiv.org/pdf/1810.02720v1.pdf
Code: https://github.com/pcyin/tranX
Live demo (try Django out): http://moto.clab.cs.cmu.edu:8081/
Machine code instructions designed by hand are not necessarily the best fit for the code we actually generate. Similarly, might our approach to language design lack pragmatic insight as to which constructs should be favoured, adopted, simplified etc?
“Data-driven language design”.