4 ms·
> Visual programming comes around every ten years, and fails each time True. I think though visual programming is alive in niche markets -- control systems, au
by rdtsc 10y ago
> Visual programming comes around every ten years, and fails each time
True. I think though visual programming is alive in niche markets -- control systems, audio processing, industrial control. It might have never becomes mainstream but it is not dead there. Telling those experts that they now have to write code, is not going to go well, they'll never be ready to open Emacs and start coding.
> Constraint systems are alive and well in SolidWorks, Inventor, and other such systems.
Also GUI layouts in some cases are done using contraints.
> But I also think "different for different's sake" is a good way of eating money and alienating users.
The goal is not to do just different things, but do different things in order to better solve problems.
> It turns out, just because ideas are interesting, doesn't make them actually better at solving real problems in general!
But if it does, and you never go seek out new things, you'd miss out. That was one of the points in the talk.
For example there is mention of actor programming. I use that to program large distributed sytems in Erlang. And it is not just a gimmick, but abstractions provided by the framework allow a more concise representation of ideas. It does feel like going from Assembly to using C in terms of concurrent and fault tollerant system. You can do everything in C++ of course with threads and locks, and a library with serialization and networking. But it feels like using Assembly. The advantage also comes in other ways -- abilty to have less ops pain because system are more fault tolerant, ability to hotpatch live system and so on.
Someone who is used to segfault crashing whole backends and spending weeks chasing hard to find use after free bugs or concurrency bugs, might not know there is another way. They accept that "this is programming", the manager accepts that this is how systems are written and delivered and this level of cost of maintenance and bug chasing is acceptable and normal. Nobody in the chain will go and seek out and try new tools to solve the problem better.
> But I also think "different for different's sake" is a good way of eating money and alienating users.
That's true to. For every "this new technology helped us double so and so metric" there is 10 stories of "we re-wrote our stable backend in the latest fad language someone read about on HN and now 2 years later everything is crashing and nothing works".
- taeric 10y agoI take issue with the "they'll never be ready to open ___ and start coding." Sure they can. It just might take them a lot of training. But so what? You know how long it takes someone to become competent with a guitar? Piano? A wrench? Hammer? ... It isn't exactly overnight. I am also question that actor based programming is somehow something that provides a more concise representation of ideas. It may, for some cases. However, I suspect anything actually of real world use has moved beyond what anyone would consider concise. Indeed, after fumbling through something I was certain should be doable in fewer lines of code, yet again, I am coming to believe that the pursuit of concise solutions is the biggest fallacy in programming. I confess I am ok, however, with people preaching to a choir to drum up support. I don't have any actual data, but I do feel that this keeps the topics in people's minds, which does increase the likelihood of an idea finally having its time.
- rdtsc 10y ago> I take issue with the "they'll never be ready to open ___ and start coding." Sure they can. They can, but they would be upset if they had to (at least the ones I've seen). Making them develop what they did visually in code would be maybe like telling someone who is using Python to start writing assembly. Sure they could become competent, but when they are delivering products quicker with this other, better tool, they wouldn't want to do it. > I am also question that actor based programming is somehow something that provides a more concise representation of ideas. Not just actor programming, but the constructs available in Erlang/OTP library. It includes abstractions built on top of actors -- server instances, finite state machine, event handlers, logging, etc. But going back to actors, in general I find, actors map best to real world concurrency scenarios. A connection is an isolated actor, it processes data sequentially internally but there are multiple such instances running concurrently. A customer as an actor works, it has state, it issues purchase orders, it fails, it wait for response and so on. But there are multiple such instances running concurrently. You process an data file in a pipeline, each step is an actor like factory worker, doing some work and passing it along to next one on the conveyor belt. At least from what I've seen it represents the real world problems better than say an epoll event loop or a lock. > I am coming to believe that the pursuit of concise solutions is the biggest fallacy in programming. Concise doesn't mean a pure contest on line length. That usually results in obfuscated code. Conciseness includes clarity and operating at the right level of abstraction. If an order is being processed, it means seeing clear steps: load_price_list, submit_payment, check_inventory and so on, perhaps instead of lock_thread_1, handle_promise_callback_5. Some frameworks have better abstractions in place than others. Maybe Matlab has better abstractions for multiplying matrices and solving signal processing problems. Other languages are better at graphics, and so on.