170 karma · joined June 21, 2014
What this allows one to do is assemble handlers from lots of small higher order functions. It has the downside of one needing to have initialization well organized and thought out. But the fractal-cul-sac as one co-worker has nicknamed it of ever dividing and increasingly specialized functions with IO and logic twisted together is effectively prevented. One can always modify one handler without affecting others or changing how existing functionality works. And it is always testable in small unit tests because the logic is pure.
Systems built in this style can radically reform themselves in a controllable, reliable and consistent way indefinitely. They are immune to the "apogee" phenomena whereby a system gets to the size and fragility where it can no longer be modified without causing unforeseen regressions, triggering the need to rewrite it to move it forward.
This style is for handler-oriented procedural software common in web services etc. It does not apply to embedded state-machine oriented software that operates real-time control etc. That is a different problem space.
These initiatives will always exist because there will always be people that do not understand what encryption is and what it provides. But lots of smart people understand the consequences would be catastrophic, and rapid. We cannot eliminate dumb politically-motivated ideas.
I think the Swedish investigation, with no public announcement, might be the only source of primary information. Add to this the sabotage against German trains etc, and the overall lack of ability of the Russian government to negotiate for its interests but instead choose subterfuge (they denied the invasion, and claim themselves the victim), it is more likely such a secret operation is in the interests of the aggressor.
Now I don't mean to imply there are not good uses for tool chains like C++'s etc. Only I will say that the disconnection from the end result caused by the long write-debug-ship cycle leads to a certain programmer malaise. The same is true for things like coding chips with Verilog. The production chain is so long with respect to the creative endeavor itself that motivation and satisfaction is hard to get.
So, for me, doing SaaS software, which ships "all the time" with Clojure, has restored my ability to 1) read the std library and most others easily to understand them, 2) Create control, preprocessing and IO primitives myself for special purposes which easily rival standard ones, 3) use interop to access large libraries written in another long lived language (Java), 4) build and use tools that simply introspect the code, producing my own tool additions and automations without AST's, and elaborate tooling, after all, code is just data.
Obviously YMMV. One blog post documented someone who changed from C++ to Clojure and did not find satisfaction. But he was attempting to do something, embedded I believe, that is not well suited to a JVM. So changing to Clojure does involve changing to an area that favors one of the two big Clojure host language machines, JVM or Javascript based environments.
As for tautology, I am claiming that we are attributing intent (a human characteristic) to an object. I think I used the term correctly. That behaviors of objects should not in general be allowed to be equated with human behavior leading to therefore imply human-like intent. I think this is a good idea in science.
In my case I was trying to forward the idea of these two being at a different scale was a differentiator. And that the ants therefore were better candidates for such human like behavior than a plant.
However a studying biology major set me straight on that and introduced what I think is a better criteria for looking at these systems. She said the underpinning work focused on these colonies establishing communication mechanisms. And while anthropomorphizing systems is frowned upon, in this case that might be an overly strict rule. After all both communication and conscious intent are both associated with humans.
In computer science we fearlessly anthropomorphize with our names (actors, agents, managers). Why that should be not be frowned upon, but disallowed for plants therefore seems less and less obvious. So I think my concerns are unwarranted.
Working on serious problems like climate change would be hobbled without the rise of the data economy. But to be an economy it must have rules that protect private, personal and ethically important entities.