4 ms·
Wasn't it the idea behind visual basic? If I recall correctly the devs aimed at making a more natural programming language. I don't think it'll ever work, ther
by friendlybus 6y ago
Wasn't it the idea behind visual basic? If I recall correctly the devs aimed at making a more natural programming language.
I don't think it'll ever work, there's the obligatory xkcd comic about the limits of sophisticated programming languages. The code will never free you from the burden of having to specific exactly what you want.
Maybe an ML/AI parser for natural language would be a possible improvement and then tweak the details after the parsing. Likely just make things more complicated though.
- hardwaresofton 6y ago> I don't think it'll ever work, there's the obligatory xkcd comic about the limits of sophisticated programming languages. The code will never free you from the burden of having to specific exactly what you want. In my mind it's less about freeing the user from specificity, but just changing the language under which that specificity happen. Honestly it's just syntax! Imagine something like: > open file on disk at "/some/path/to/a/file" into $my_file_handle. read contents of file handle $my_file_handle into new variable $contents. print $contents to standard output. Imagine every sentence just being a textual template for a function invocation, with context in-between functions (state) being preserved and managed implicitly with the use of variable names & prose. signatures for the functions required would be something like: - open_file (path: string): file_handle - read_bytes(fh: file_handle): string - print(s: string): void We already have functions like this and compose them in ways that the text suggests -- it's more about just adding a different way to group and recall up the composed functionality.