jetblackio

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).

3) Install from source

4) Install via language-specific package manager

5) Install via curl | sh :)

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.

Proton VPN is rock solid. I recently made the full switch off gmail to Proton email, and signed up for the VPN as well. It's worked great so far.

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 did not know about this. Thanks, it looks very interesting.

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.

In the same boat as you. If Apple doesn't fix this horrible keyboard in the next release, I think I'll finally switch to ThinkPad.

Looks great! I've been running through exercises on exercism.io, but this looks like a good next step in my Gopher journey.

Right on, this is perfect. Thanks!

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.

AWS or GCE are the way to go. Azure is horrible. Stay away from it.

I'm moving to Mexico in a few months :)

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?

If generalization is something you enjoy, that skill is hugely important in the DevOps / Sysadmin world.

Findbugs is the main one. If you had support for that, I'd get my 120+ dev team moved over tomorrow :)

Any plans on adding Java support? I suppose with this new platform, anyone can. But is that something you already happen to be working on?

I've successfully worked a 4-day work week for over a year. I assume you mean 4, 10-hour days, which is what I did. I actually staggered my work week so I'd work Mon-Thur, then Tues-Fri, giving me a 2-day weekend, then a 4-day weekend.

Other members of my team had the same schedule, and we'd stagger our schedules as well.

It worked very well for me. I loved the extra time. I don't have kids, so the 4-10s was pretty easy for me. And having 4-day weekends every other week allowed me to do take mini-vacations and do some travel.

Forgive me, but I'm not very familiar with the rapidly growing container-based ecosystems market, but how do all these pieces fit together? Namely:

* Mesos / Yarn

* Marathon

* Kubernetes

* OpenShift

* Chronos

There are others I'm sure that I just don't recall.

Also, how does the container approach fit in the traditional VM models of OpenStack / AWS / Digital Ocean. Are these systems aiming to ultimately replace them? Do they solve the problems of networking and disk?

Maybe it's time I spent an afternoon looking into all this.

I haven't thoroughly investigated possible CLI solutions for the following, but here are some things that come to mind.

* iMessages / SMS

* Viber / Slack / Whatsapp / Facebook (messages)

* Better calendar app

* Better Pivotal Tracker CLI

As you can see, I think messaging is a perfect use-case for the CLI, and you don't lose much functionality when compared to a GUI (except images, gifs and movies for the most part). So seeing development in that area would be awesome.

This is completely different than DynamoDB. Essentially this is a framework for sharding or horizontally scaling multiple datastores (MySQL, Memcache, Redis, etc).

I like this idea, but one issue I see is that, while 95% of people could use an extra 10k, the real cost of welfare comes from those few who have major medical needs, and that 10k would do nothing for them, at least as currently outlined here. There are always going to a portion of society who will need a disproportionate amount of financial assistance, and this doesn't seem to take that in to account. It seems likely that after problems arise, we would implement some other form of welfare on top of this program, and wouldn't have really gained anything.

That's my quick assumption anyway.

Looks interesting. How would you say it compares with Deis.io?

Yep, my app is down and can't be restarted.

Yes, I think it would be a deal breaker for me personally. For the one thing, there would be a bit of effort to migrate from any config management system (my background is Chef and Ansible) to straight bash scripts. Also, it doesn't allow for the modularity and reusability of scripts that these services grant you. In fact, if you really want to make this simple, adding support for config management as crucial. I can easily import a Chef cookbook, override a couple attributes and have a MySQL server up and running.

So ya, I think adding support for a config management system (my vote is Ansible) would make this 10x more useful.

That's unfortunate. I understand where you are coming from on making this absolutely as simple as possible for those who are maybe not so admin inclined, but I feel it's limiting to actual administrators/devops engineers, who are more than comfortable with traditional config management systems.

Personally as an administrator I want to be able to continue to use Ansible from the command line, but then grant access to my developers to a UI where they can easily spin up instances for temporary use.

That's just my use case. Otherwise, looks like a cool product. Good work.