Will JavaScript type annotations kill TypeScript?
The creators of Svelte and Turbo 8 both dropped TS recently saying that "it's not worth it".
Yes: If JavaScript gets type annotations then there's no reason for TypeScript to exist.
No: TypeScript remains the best language for structuring large enterprise applications.
TBD: The existing user base and its corpensource owner means that TypeScript isn’t likely to reach EOL without a putting up a fight.
I hope they both die. I mean, if you really need strong types in the browser then you could leverage WASM and use a real programming language.
I don’t know and I don’t care.
Cloud Native Ecosystem / Containers / Kubernetes

VMware Teams with Docker and Google, Further Boosting the Container Ecosystem

Aug 25th, 2014 1:18pm by
Featued image for: VMware Teams with Docker and Google, Further Boosting the Container Ecosystem

There is a certain truth in VMware’s news that it is partnering with Docker and Google. All good things do ripen but it’s better to embrace youthful new ways before it’s too late.

Instead of clamping down, VMware announced today that it has decided to embrace container technology and accept Docker and Google Kubernetes as integration partners.  Pivotal, also part of the news, is embracing Docker just a bit more.

Maybe it is the incredible acceleration in acceptance that Docker has received that spurred this broad partnership.  That is without a doubt true. But from VMware’s perspective, the move represents more. Look at VMware’s strategy and there is one common theme: the quest for dominance in the data center, which it can only achieve with an open, interoperable model.

VMware will work closely with Docker in its networking and other products.  Further, VMware is also embracing Kubernetes, joining the fast rising community that Google announced two months ago. Kubernetes offers VMware something different, allowing it to extend to another networking framework. Plus, it allows for a deeper level of integration with Cloud Foundry. Both Kubernetes and Cloud Foundry run on etcd, the configuration management service that orchestrates containers.

As we wrote two month ago, Kubernetes is an open source container cluster manager from Google, which leverages the etcd distributed key-value store.  Blake Mizerany of CoreOs wrote in a post for us that “It (etcd) takes care of storing and replicating data used by Kubernetes across the entire cluster, and thanks to the Raft consensus algorithm, etcd can recover from hardware failure and network partitions. In addition to Kubernetes, Cloud Foundry also uses etcd as their distributed key-value store.”

Clusters are usually built from a large collection of machines with the ability to run any workload at any given time. In order for a cluster to perform at high levels of efficiency, it’s neessary to distribute workloads appropriately across all machines in the cluster. Clusters then need a way of coordinating with each other.

Docker will work with VMware on compatibility testing to make sure there is a base virtual machine that can run Docker, said Ben Golub in an interview today. Golub is CEO for the young container technology company.The two companies will also coordinate with the development of libswarm, libchan and libcontainer. According to the GitHub Docker page, libswarm is a minimalist toolkit to compose network services, libchan serves as an ultra-lightweight networking library and libcontainer specifies configuration options for what a container is.

“There is work that is being done to integrate Docker Hub with management tools they have at VMware,” Golub said. “They [VMware] also have Project Fargo — making the virtual machine more lightweight and flexible.”

Docker, in its current state, is designed for applications that can be represented in a small number of Docker containers, Golub said. “What we want is to create applications that are built for a large number of Docker containers across a number of hosts.”

VMware would be contributing code and endorsing the standard, Golub said. The important thing  — get people behind the libswarm API to plug in networking frameworks that are emerging.

The collabration between Docker, VMware and Google covers a lot of footprint. It covers VMware vSphere to VMware vCloud Air as well as working together on libswarm, libcontainer and libchan.

For Google, the partnership gets it deeper into the enterprise. VMware will make Kubernetes’ patterns, APIs and tools available to its customers. VMware will also contribute code to Kubernetes and make VMware vSphere more readily available to customers exploring container management.

And then there is Pivotal, which has a lot at stake with its heavy VM-focused PaaS environment. VMware, Pivotal and Docker will add libcontainer integrations. This means connecting Warden, the Linux container originally developed for Cloud Foundry when it was a VMware project.

Red Hat has integrated Docker into OpenShift, its PaaS, and there are a host of new PaaS offerings using the Docker technology.

VMware is covering all of its bases. It has ripe technology that will be relevant for some time to come. But Docker is a fortified, young competitor, flying now with the acceptance of open source. With VMware, it can now open itself to a considerable market. And Google? There’s the netwoking connection there. Again a sign that VMware has its sights on a new type of data center that requries the networking of VMs and new container environments.

Image via Flickr Creative Commons

Group Created with Sketch.
TNS owner Insight Partners is an investor in: The New Stack, Docker.
THE NEW STACK UPDATE A newsletter digest of the week’s most important stories & analyses.