3 ms·
> 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 on
by 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.