That is true. But there are ways around that. Including documentation on how to build it locally is pretty standard. And hosting prebuilt binaries with package installation for targeted platforms is also pretty common as well.
With interpreted languages with language-specific package managers, you have to:
1) Install the language
1a) Possibly have to install a language version manager (rbenv, pyenv, etc)
2) Install the language's package manager
3) Install the CLI utility via the language's package manager
Here's the order I think CLI maintainers should strive to making their utilities available:
1) Install via OS package manager
2) Install via prebuilt release with OS-specific package, from hosting site (GitHub, etc).
If you find this to be the case, then maybe you’re not being as polite / kind as you think. Because from my experience this simple is not the case. I’ve seen this argument made a few times and it’s pretty rubbish. You are free to talk to anyone of any sex if you treat them kindly, politely and with respect.
I think the distinction is "reach". Emails are generally directed to dozens, maybe hundreds of individuals, whereas with modern social media, an individual can reach millions of people. It begins to enter the realm of traditional media organizations.
But unlike traditional media organizations, there are far fewer laws in place regulating the responsibility that comes with that reach.
It is an interesting problem, and I'm not sure there is a good solution, other than try to combat it head on with education (how to properly evaluate the information you accept), and possibly PSAs.
It's also a matter of "endorsement" which is what Facebook tacitly does when they they host this stuff.
You are free to say or feel whatever you want in your own living room, amongst your friends, private function, your head, email, decentralised hate-sites or even reddit or 4chan.
Precisely the problem with Facebook is that they are actively stirring the pot to sell ads. They are making money off this stuff.
How unused is the letter z on your keyboard when typing? Different regions of the brain serve different functions, so though they aren’t always activated, they are necessary.
Besides, obsolete and unused brain tissue is very expensive calorically to maintain, and would be a hinderance to survival over long periods of time.
In an office of 20+ developers on Macs, over half have had to get their keyboards replaced, and a few more just live with broken keys. This keyboard is truly awful.
After 10 years on the Mac, I'll be switching to ThinkPad / Linux / Hackintosh if the next MBP doesn't fix the keyboard issue.
I spent 8 years writing Linux software on a Mac, with various configurations including SSH, VMWare and Docker development environments.
For a while I was happy about this state of affairs, but over time I became increasingly dissatisfied.
Late last year I started a new job and essentially demanded that I be allowed to choose my own hardware. I ended up getting a high-spec X1 Carbon and running a Fedora variant on it.
It works very, very well. And the keyboard is great. I won't be going back to a mac any time soon.
Have you run into any issues with Wayland? I've been running Mint for the past few years, but the lack of fractional DPI scaling is frustrating so I've been considering switching to Fedora.
Congratulations on open sourcing this. It looks great. Is there a reason you went with Node.js instead of something like Go? As a sysadmin, I personally hate having to deal with dependencies from tools built in non-compiled languages like Python, Node and Ruby.
We did try to partially write it in Go. Writing it fully in Go would not have be possible because of the plugin system we have. However we struggled with Go quite a bit and ultimately dropped it from the codebase. This article gets more into detail as to why: https://blog.heroku.com/evolution-of-heroku-cli-2008-2017
We also have some tools we use with the Heroku CLI we will be backporting into oclif very soon that directly addresses this problem node has with distribution. Essentially it's some scripts that let you export an oclif CLI as a standalone tarball (node binary into it), optionally being able to autoupdate with github or s3.
oclif is also compatible with pkg (https://github.com/zeit/pkg) which will turn the CLI into a dependency-less single binary just like it would be with Go. I don't like it personally as I find it useful for debugging to actually edit the files. With Go we would have to cut a release just to add extra debugging information.
As part of dropping Heroku for our own platform we ended up writing something equivalent in python, then Go initially to deal with packaging/distribution. Its been pretty great, but damn I would have loved this to have been in Go. Then I wouldn't even tell the developers we moved off Heroku :P
I'm interested in the reasons this annoys you, as I find nearly all the installation problems we see in node is when somebody has included some C code that needs to be built.
Not sure if this is a good place to ask, but how do Apache Arrow and Parquet compare to Apache Kudu (https://kudu.apache.org/)? Seems like all three are columnar data solutions, but it's not clear when you'd use one over the other.
Kind of surprised the article didn't mention Kudu for that matter.
I have been working full-time on Kudu since its early development. As others have mentioned, Arrow and Kudu are quite different. Despite the controversial-sounding title of Daniel Abadi's article, his content was actually reasonable and his conclusion in the final paragraph of the article is worth reading. In summary, he acknowledges that in-memory and on-disk columnar formats have different goals and both have their place (Arrow being an in-memory format).
Apache Kudu is much more than a file format - it is a columnar distributed storage engine. One way to think of Kudu is as mutable Parquet, but really it's a database backend that integrates with Impala and Spark for SQL, among other systems. It's fault tolerant, manages partitioning for you, secure, and much more. For a quick introduction to Kudu you can check out this short slide deck I put together over a year ago... it's a bit dated but a good overview: https://www.slideshare.net/MichaelPercy3/intro-to-apache-kud...
For more up-to-date information, follow the Apache Kudu Blog at http://kudu.apache.org/blog/ or follow the official Apache Kudu twitter account @ApacheKudu.
One quick note to make on this. Kudu is a storage implementation, (similar to Parquet in some ways). Arrow isn't about persistence and is actually built to be complementary to both Kudu and Parquet.
Also note: Kudu is a distributed process. Arrow and Parquet are libraries that can be embedded into your existing applications.
With interpreted languages with language-specific package managers, you have to:
1) Install the language
1a) Possibly have to install a language version manager (rbenv, pyenv, etc)
2) Install the language's package manager
3) Install the CLI utility via the language's package manager
Here's the order I think CLI maintainers should strive to making their utilities available:
1) Install via OS package manager
2) Install via prebuilt release with OS-specific package, from hosting site (GitHub, etc).
3) Install from source
4) Install via language-specific package manager
5) Install via curl | sh :)