2 ms·
I've read plenty of comments about this article the last few days, it has made the rounds in popular sites, and the verdict is the same as the author's. What's
by axilmar 7y ago
I've read plenty of comments about this article the last few days, it has made the rounds in popular sites, and the verdict is the same as the author's.
What's surprising is that no one sees the elephant in the room: the problem with coding is that the abstractions available in coding are the same one offered by operating systems: files, processes, threads, mutexes, sockets etc. These are the wrong types of abstractions for the majority of cases!!!
What we should have instead is data, functions, events and channels.
If we had that, then we wouldn't need to have articles about 'no code', we wouldn't need visual programming tools.
The abstractions we have now only get in the way of programming. They make development really slow. If we had the set of abstractions mentioned above, it would have been a lot easier to create solutions!
I am not saying that the abstractions we have now are totally useless; they are not, of course, because they allow us to make things, but they aren't what we need in most cases.