Programming hasn't fundamentally changed since the 1940s. Most languages still follow the von Neumann paradigm: write sequential instructions and m...
For further actions, you may consider blocking this person and/or reporting abuse
Sounds more like functional programming, especially with something like Erlang/Elixir.
Thanks. Sure there are similarities, but also differences. I'm planning to write a document comparing them
I'd be curious to understand your take on the differences. TBH, I think the difference here is you are not doing "function composition" the way you are in functional programming, rather this is more procedural and explicit passing of data through a series of black-box procedures. Is that right?
I believe its functional programming, but you are only allowed to use pure functions (no internal state or access to global variables)
You want to switch to a different programming language that is more suited to human limitations, but you fail to notice that in the near future more and more software will be written by AI that has no such limitations :-)
Thanks, good catch. I was thinking about this too and here's what I've ended up with:
Humans will still review the code. There will be part we don't care about and there will be parts we care a lot. It's good to have easy to write/understand code even if you use AI
I don't really think we will be reviewing AI's code.
Very soon, the AI will be programming out of the box, better than most developers.
Right now, it program way better that junior developers, and it is increasing it's capacity exponentially.
I think we won't program code in the future, but program concepts, "boxes".
Take a look at no code/low code options.
Quite a unique and interesting article
Cool piece!
Interesting. thanks!
that is good to know
cool language
interesting, as @jasonlotito said this has a lot of similarities to FRP, especially Erlang/Elixir. message-passing concurrency with actor model, immutable structs to prevent race conditions, lightweight parallelism and process isolation, all while being provably scalable
are you trying to solve for something specific that those don't? or it just learning how to write for parallel processes?
not knocking it at all, just curious!
It's called Flow-based Programming.
interesting
I want to learn and explore it . Where should I start?
interesting however the go sample and it's description is really poor and inaccurate
why?