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.
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.
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.
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.
Agreed, and I've personally noticed a lot of people moving out to the Denver / Boulder area. On my team alone we had 3 people from the bay area move out to Colorado. It's an attractive place for tech talent, which certainly wouldn't hurt Amazon's cause.
Seems like Denver would be good choice, considering how alike Seattle and Denver are. There's plenty of hiking, biking, camping, etc in the area, and it's central location is convenient for any travel to both the east and west coast.
Denver also has an excellent craft brewery scene. Denver / Boulder are already tech hubs in their own right as well.
One thing that I've always wanted was for Jenkins to get away from being a UI, and just be an engine with a nicely documented API. People could then build more niche CI/CD systems on top of that engine without having to reinvent the wheel. It's nice that Jenkins is finally getting a UI facelift though.
Looks really cool, but honestly the input lag is noticeable when compared to something like iTerm. Not sure that's something I could get used to. Is that just a limitation of Electron?
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 :)