I agree with the overall sentiment of the article. I've felt many times helpless trying to keep up with the the latest js framework or workflow (webpack, Babel, grunt, brunch, Backbone, Angular, etc). By the time I've gotten comfortable with some new piece of js software, a new one, even cooler had appeared.
And on top of it, add the fact that I also enjoy learning new programming languages for the backend, and the mental overload is definitely ensured.
This did not happen overnight. The big computer companies have been building AI labs for years, decades in case of MicroSoft. They've been revisiting Go for the past few years too. One of Marvin's early students advises Googles R&D. These companies have raided every major university. If Marvin was still alert in his final years, he would have known some about this.
One of the problems with how we develop software today is the long path from idea to a working prototype.
There are many layers in between, each with its own set of abstractions and assumptions. Factor in the number of different platforms you need to develop for, and you've got yourself a very complex world you need to navigate.
Writing software in 2016 is to some extent similar to operating a 18th century ship through the dangerous waters. We have a good enough machine to take us places, but we still need to visit the engine room, to keep things running. It's getting better nonetheless, but you still need a specialized crew to steer a big ship in the right direction. I would much rather prefer a yacht, where I could just press a button and enjoy a more experimental, higher level experience, in which my job would be to map ideas to real world working systems.
With that given said, this definitely looks interesting. I'll surely give it a try.
Technology is truly augmenting ourselves and this medium "shapes the scale and form of human association and action", as Marshall McLuhan once said.
With that given said, compare a whistleblower, say 20 years ago, with one today. Snowden not only had the world's greatest communication platform at his disposal, to disseminate whatever information he cared about, but now he can still address millions of people, speaking at the world's greatest universities and giving interviews, while being in exile.
Regardless on where you stand on these privacy/spying issues, I think it's hard to deny the fact that he started a dialog, and now the entire world can be part of it.
> With the telegraph Western man began a process of putting his nerves outside his body. Previous technologies had been extensions of physical organs: the wheel is a putting-outside-ourselves of the feet; the city wall is a collective outering of the skin. But electronic media are, instead, extensions of the central nervous system, an inclusive and simultaneous field. Since the telegraph we have extended the brains and nerves of man around the globe. As a result, the electronic age endures a total uneasiness, as of a man wearing his skull inside and his brain outside. We have become peculiarly vulnerable. The year of the establishment of the commercial telegraph in America, 1844, was also the year Kierkegaard published "The Concept of Dread."
> [...] When new technologies impose themselves on societies long habituated to older technologies, anxieties of all kinds result. Our electronic world now calls for a unified field of global awareness; the kind of private consciousness appropriate to literate man can be viewed as an unbearable kink in the collective consciousness demanded by electronic information movement.
>Once we have surrendered our senses and nervous systems to the private manipulation of those who would try to benefit from taking a lease on our eyes and ears and nerves, we don't really have any rights left. Leasing our eyes and ears and nerves to commercial interests is like handing over the common speech to a private corporation, or like giving the earth's atmosphere to a company as a monopoly.
Funny, I would say that the perception of this as a violation is something only felt by those who don't understand that the whole point of putting your nerves outside your body is to expose them to the world. If you wanted to keep them private, all you had to do was nothing.
Or to boil it down to John Oliver terms since you seem to be a fan, nobody's going to see any pictures of your dick unless you take pictures of your dick.
To put it in terms that match our political realities, no one will see your dick provided you take exceptional care to not expose your dick for even the slightest second, otherwise, there are too many people watching to make a guarantee.
> If you wanted to keep them private, all you had to do was nothing.
You are advocating for the complete repression of any idea that hasn't yet become both known and acceptable to the mainstream.
It's not going to always be pictures of your dick. To name just a few of the most obvious groups with real risks, you're effectively saying that anybody with unpopular political views, anybody LGBT, and anybody with a religious belief that isn't "Christian" shouldn't participate in modern society and the network interactions that participation requires if they want to stay safe?
Blaming the victims for not staying out of sight isn't the solution.
If you have an unpopular view, speak out. Be oppressed. Fight back against the oppression if you can, and roll over and die if you cannot. If you win, your side is and always was right. If you lose, the opposite.
This gets a Cowboy application up and running, but it doesn't tell you what to do to write your own Cowboy application, and doesn't give you a very firm understanding of either how the hello_world example works, or how to modify it to suit your needs.
As someone who's been down this road in the past, unless you're already rather familiar with Erlang and OTP's conventions, the gap between the User's Guide and the API documentation is far too large to make connecting information you learn from one with information you learn from the other easy.
I've summarized my personal struggle with the Cowboy user's guide and documentation in my other comment in the thread. Please read that comment before you downvote this one. :)
As far as I know there's no such thing as a `Cowboy application`. They're all Erlang/OTP applications. Sure, there's a learning curve associated with OTP apps, but since Erlang is a bit of an exotic language, I think it's understandable.
I guess you didn't read my other comment in this thread. Please read it. ;)
> As far as I know there's no such thing as a `Cowboy application`.
From one pedant to another: "I know that." >:)
However, there is (to put it loosely in OTP terms) a set of Cowboy behaviours. Your application is expected to implement one or more of these. While the API for these behaviours is reasonably documented, the Cowboy equivalent of the -say- gen_server "User's Guide" is so sparse as to be almost non-existent.
I generally agree that -in the absence of sufficient documentation- reading the tests and source for the project is generally the best way to learn how to use a project.
However. If the language the project is written in is wildly unfamiliar to you, and you've never had experience with a similar language, then this technique is often... less than satisfying.
From your comments, it appears that you have more than a passing familiarity with Erlang/OTP. You have to admit that it would be substantially harder to understand both Elixir and Phoenix without your understanding of Erlang. :)
I'm actually wondering what would be more reliable: a physical button or a digital one. I would like to see a comparison.
Of course, one could argue that in both cases it depends on the implementation. Nonetheless, I think it's fun to think about what kind of buttons would the average person prefer, when their life is on the line.
I was thinking the same thing - sure, it's cool to have a glossy touch screen and futuristic touch panels, but I can't count the number of times touch screens / buttons have gone wonky on me with everything from my cell phone, to my tablet, to my microwave, to my fridge, whereas the light switches in my house are about 50 years old and have yet to let me down...