I think all the Pajeet's we've imported are affecting the finished products after decades of getting promoted and now hiring their tribe over best skilled for the job.
You're not the only one who has experienced this.
My experience has generally been that shit almost never installs out of the box.
THere's always some dumbshit extra steps I have to follow to get it to work.
And don't get me started on docker. I don't get everyone's collective orgasm over docker, I've found it obnoxious to work with. Plus docker allows companies to sell proprietary containers which basically means docker will turn into a paid platform if you want to do anything other than use purely-open source code.
I think the problem is that technology is getting more and more specialized. The distros are moving farther apart from each other in terms of related packages and software versions.
There's a lot more competing installation methods out there. I think go has the best idea shipping (basically static) binaries.
This is definitely better than it used to be. Having scattered libraries all over to find and compile. Eventually to packages. While sometimes these things are broken, you can usually open an issue and get help pretty quickly. You do have to learn a little about a lot, but I think the ecosystem is evolving really well. A few steps forward with one back every so often.
I found that the scattered libraries always installed consistently. So yeah, it took a long time if several libraries weren't in the package manager, but you always got that end product.
I tried to install something yesterday, can't remember now but it wouldn't install. The make file would work, did a search and found that the idiots on the site that created the files didn't compile the shit right. I think the problem you are having is that the people are not competent like in the past. I was installing themes for XP and found a great one. The dumbass forgot to make a theme file for the theme and had great art but didn't make the file so the theme was usable. I was fuming that something that is so necessary for any theme even in windows with the theme file was not there. In windows though I was good enough to take another theme file and edit it for the theme I needed it for and it always worked but I don't have the experience enough in Linux to do that YET. Always leaning though so I'll be great by 10 years I imagine.
Right. Those people are inept. The problem is the people I deal with are also inept, but if I bother to tell them they packaged their software poorly I end up looking like the dummy when they say "don't you know how to use yarn"
The whole point of packages is that people don't need to know your shit.
You would think that packaging things for C, a lot of the complexity of the problem would bleed through to the user, but it doesn't. Yet now we have high level languages that let you write the same code in 10 lines that would take thousands of lines in C. Which is really great. But then they have even less excuse to pass on complexity to the user. They are taking the most uncomplicated thing and wrapping it in complexity.
So do me a favor guys. The next project you work on, add a Makefile.
Sorry , I sent you something and it did not have a Makefile. It should have though.
Lol
The best irony of all is that I was the one who convinced phuks to write a dockerfile. I wrote the first one. I just though dockerfiles do document how to install something so they are useful even if you don't use docker.
I almost made your code docker dependent.
They still don't use it, and its still shit. too many changes on the regular basis for it to work well. I Just setup another clone for someone 2 days ago and there was no really good documentation to make it work. There still isn't I'll just have to write it myself again.
I've got an instance of Poal running on a Pi2.
Best install moments in my life.
I'm sure docker would have made it easier. Good thing Poal doesn't have docker as a core dependency. That would make it less portable.
(post is archived)