Should we be Unix? That is, is it better to be a jack-of-all-trades,

I have a little webdev knowledge there, some sysadmin there, a little C# there, I even done some ARM assembly at some point, and I'm earning quite well.

>>62012747
What do you do?

>>62012790
yesterday I made 50$ in an hour migrating some wordpress site. The other day I made 200$ doing a laravel framework php job. I got 100$ to do a C linux thread assignment for an uni kid. I'm a jack of all trades master of none pretty much

>>62012731
>muh Unix philosophy

Friendly reminder that "the UNIX way" is a loose and vague idea angry neckbeards and borderline autistic manchildren throw around whenever some decision is made that they don't agree with.

This is why we end up with 14 different forks of BSD and why BSD developers spend most their time discussing how the original project doesn't live up to their code purity standards, than just getting shit done and contributing upstream.

Uriel and cat-v.org is the epitome of the vile and hostile community this kind of attitude fosters: a bunch of angry nerds who doesn't really contribute in terms of code, but instead spend their time compiling lists of what they consider to be "harmful" and write angry rants that alienate potential contributors.

The UNIX way is the reason why Go has the horribly broken "import directly from github" import system, without any form of security or ability to specify a specific version. It is also the reason why Go inherits a broken error handling paradigm from C, because that is what the UNIX way is. Robert Pike, among others, were involved with UNIX and has forced their archaic legacy ideas onto their new programming language.

>>62012832
>"import directly from github" import system, without any form of security or ability to specify a specific version.
Yet, so does NPM, and it knows how to specify a version, either by a tag or a commit. I can't really explain why such a simple feature as that would have gotten left out of go get.
>broken error handling paradigm
>from C
Your precious exceptions are setjmp, nigger.
>legacy ideas
Your muh innovtaion is the reason it sucks to actually work in this industry.

>>62012940
>Yet, so does NPM, and it knows how to specify a version, either by a tag or a commit. I can't really explain why such a simple feature as that would have gotten left out of go get.
At least we agree that Go get is retarded.

>Your precious exceptions are setjmp, nigger.
Still, goto's are considered harmful, and relying on a programming model where checking the return value with conditionals is the idiomatic approach would make Dijkstra turn in his grave.

Exceptions are not perfect, but at least they offer error handling semantics that aren't pants on head retarded. You write code that assumes a successful path, and errors are considered exceptions to the successful code path. Not only does this allow you to write cleaner code, it also allows compilers to potentially optimise for the successful path.

>Your muh innovtaion is the reason it sucks to actually work in this industry.
The whole idea of Go was to become a new systems programming language, not fucking C+=1.5

Instead, companies are trying it out and writing "microservices" in it, because it's fucking useless for anything larger than a minimal service.