As an advanced Clojure programmer I never look for examples on the web, which is not the case for other languages.
The reason behind this is that since Clojure is data-oriented, API interfaces are clear, minimal and self-documenting.
With object orientation or anything that relies on datatypes, I always end up browsing docs looking for what's possible to do with the given list of methods. Never in Clojure.
I didn't look for examples on how to code something, I looked for examples on how to engineer the code I wrote. Clojure just assumes you have the engineering knowledge and that you'll be able to figure on your own how to glue everything toghether and this exactly where I had the most trouble.
Being expert-friendly is not a problem per se for a language. What matters is the ratio between sufficient wage and productivity increase as compared to other languages. By "sufficient wage" I mean paying your experts enough so that they become less rare.
I wouldn't mind paying someone 3 times as much if its expertise in the given language means he can be 10x more productive than an average programmer in an average context. (I personally have measured a 30x incrase in productivity by switching from ruby to clojure and have observed the same phenomenon with other people).
Unfortunately I think it is more of a cultural problem than a matter of leadership. The widely used FactoryGirl Ruby gem (the vast majority of Rails setups embed it) was renamed FactoryBot a couple years ago. It's not like my team had a say in this change but overall I was the only one against it but ended up implemented the change, which took about an hour (all our repos + the PRs). Note: technically I was in a situation of harassment.
This makes sense. My dog spends considerably more time sniffing ground from a pavement renewal project nearby. She may be sniffing smells that were left here decades ago !
Also, a few months ago, an article was shared on HN explaining how dogs are able to detect heat with their nose. And this makes sense too: whenever I shower, my dog starts sniffing and scratching walls near the shower stall, where the pipe is.
I bet she could sense a rat hidden inside a wall or in the ground. Predator™.
A swarm of non lethal drones equipped with 3D/depth cameras that collaborate in order to establish a dynamic 3D map of the terrain. A user consuming data from the swarm would enjoy a live "God's view" on what actually happens in reality, but through a 3D view displayed on a screen, very much like in Starcraft but without an artificial "fog of war".
This isn't a weapon of mass destruction nor a weapon in the classical meaning of the word.
But is this a weapon system, i.e. a system meant to ensure or enhance a weapon's function, such as targeting and guidance ?
I think you would be hard pressed to classify cameras as weapons. No one is being harmed by the action of taking a picture - you would have to introduce a separate weapon, such as a missile or gun, to cause any damage, and those are all governed by existing regulations.
> About 8 years ago I discovered unconventional approaches to subconscious trauma healing, and have undertaken these consistently ever since, and my "disorders" have steadily resolved. All that's left is some latent anxiety, but that continues to improve too.
The reason behind this is that since Clojure is data-oriented, API interfaces are clear, minimal and self-documenting. With object orientation or anything that relies on datatypes, I always end up browsing docs looking for what's possible to do with the given list of methods. Never in Clojure.