presspot

It's amusing to read a bunch of people who know very little about marketing wax philosophically about marketing

We also tend to forget about Quantum Link, the precursor to AOL, which was also a very robust system on the Commodore 64 in the mid 80s.

I feel sorry for the guy who registered foo@bar.com

About time someone called bullsh*t. Bravo.

ClickUp is totally badass, and their feature velocity is breathtaking.

Spot on.

I would totally fund this on Kickstarter.

Except for all of those trees (and grass!) we plant to help us forget we live in a desert.

Linkerd 1.0 and Istio are traditional service meshes; you install them in their totality across an entire platform. They are rich in features and bulky, completely overkill for a single service.

Linkerd 2.0 follows a new bottoms-up model that is, frankly, non-traditional. An individual service owner can install a lightweight package on a single service and derive immediate value. When multiple service owners on a project adopt Linkerd 2.0, their services will properly "mesh" without any platform-level installs. This makes adoption organic and immediately valuable for a single dev but also for an entire project as it gets installed into more services. Game changing IMHO.

Buoyant invented the service mesh concept and added that term to our vernacular as a way to describe Linkerd 1.x and similar systems. Istio was built using the same pattern as Linkerd 1.0. Those are "traditional", albeit in internet years not real years.

Linkerd 2.0 takes a fundamentally different approach. It's tiny, fast, lightweight and designed to add value as a service sidecar (installed on a single service) without any "mesh". If multiple service owners install Linkerd 2.0, it self-morphs into a mesh configuration and provides all of the value of a service mesh. This creates an installation and deployment pattern that is very practical and bottoms-up, delivering value to the individual service (and service owner) but also supporting a higher-level abstraction of a mesh at the platform level. This is a fundamental innovation and, hence, a new model for service mesh patterns versus the original, er, traditional model.

+10000 Airtable is badass. It is simple and elegant and fills a niche

Actually, we used that phrase in a deceptive 'loading' progress box in PC/GEOS in 1989

It was Marketing's fault!

What's something that happened in your career that changed your way of thinking?

Makes sense to me. I certainly saw this anecdotally in LA and Miami

So, if you absolutely need the functionality in a subscription app with local processing, what do you do?

And, if you're willing to pay ' thousands of dollars' for the right to use a local app, why would you not 'rent' the license for tens of dollars?

"Most of their time"? I highly doubt that.

PayPal. It's global and optimized for marketplaces (eBay). Don't become the merchant of record, which creates liability. Let your buyer and seller transact with each other directly.

Even if it makes a sales team a few % more productive, it pays for itself. Plus, it's such a gold standard that there's not really a lot of justification for using a different CRM.

Or, more precisely, http://randsinrepose.com/archives/category/management

http://randsinrepose.com #ftw

The open source food safety idea is genius.

This is a fascinating story about a genetically modified crop (RoundUp Ready cotton), a pigweed that naturally selected against it, and murder.

http://www.npr.org/sections/money/2017/06/02/531272125/episo...

Don't rule out the Azure Container Service, which is based on the open source DC/OS[1] and is, arguably, the most robust and proven container system.

[1] http://dcos.io

Kick ass team. They will surely nail it.

This was a garbage test, not real world use case that any customer actually cares about. Mesos and the Mesosphere DCOS blow both Swarm and Kubernetes out of the water with production workloads w.r.t. scale, resiliency, recovery, etc. Things operators actually care about.

In the parlance of Mesos, the Mesos kernel is an "allocator" (in that it assembles and allocates all of the compute resources) and the frameworks are the "schedulers" in that they request and consume "resource offers" (made by the allocator) and then schedule tasks to be run on those accepted resources.

>>> Mesos is more of an SDK than anything, giving you the tools to write an orchestration system

This is why Mesosphere built their DCOS; it recognizes that Mesos is a sharp-edged distributed systems kernel and needs to be packaged with convenience layers like Marathon and Chronos and "userland" tools (CLI, graphical UI, packaging system, etc) that make it a complete OS.

"Adding k8s on mesos you get the next-generation cloud native scheduler and the ability to run existing workloads. by running k8s by itself you get a lightweight cluster environment for running next gen cloud native apps." @cmcluck

More references:

[1] https://mesosphere.com/blog/2015/04/22/making-kubernetes-a-f...

[2] http://blog.kubernetes.io/2015/04/kubernetes-and-mesosphere-...

[3] http://thenewstack.io/mesosphere-now-includes-kubernetes-for...

I know a lot about Mesos and Mesosphere's DCOS, so can comment on those:

* There are users of these systems that get 90+% cluster utilization.

* Pre-emptable tasks (e.g., best effort scheduling vs guaranteed SLA scheduling) will be landing in Mesos.

* Mesosphere is building advanced scheduling plug-ins that will use the new scheduling models to do oversubscription of a cluster, helping to drive utilization to the 90%+ range without the need for any special tooling. You can get an idea of some of the algorithms being employed by checking out the Kozyrakis/Delimitrou Quasar paper[1].

[1] http://csl.stanford.edu/~christos/publications/2014.quasar.a...