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 / DevOps / Kubernetes

Nirmata 3.0 Launches With Virtual Clusters and Workload Policies

Nirmata's Kubernetes management features now include virtual clusters for self-service DevOps, workload policy management, service meshes and Helm 3.0.
Nov 19th, 2019 6:00am by
Featued image for: Nirmata 3.0 Launches With Virtual Clusters and Workload Policies

Nirmata sponsored this post.

Ritesh Patel
Ritesh is founder and vice president, products at Nirmata, a cloud native application-management platform built on Kubernetes. Ritesh has around 20 years of enterprise software development experience and has led software development teams. Prior to Nirmata, Ritesh was responsible for private cloud strategy and business development at Brocade.

Today, Nirmata is announcing its next major release which includes several new features aimed at simplifying Kubernetes for enterprises. The release also enables advanced multi-cluster workflows and use cases for cluster operators and the freedom to enable multiple developer experiences. 

As the adoption of Kubernetes within the enterprise accelerates, DevOps teams are going beyond the initial use cases and face challenges associated with day 2 operations and management.  As indicated in a recent poll of Kubernetes users by The New Stack, operator experience and developer experience remain the top challenges for Kubernetes adoption. Features released in Nirmata 3.0 are aimed at addressing these challenges and facilitating advanced use cases.

Key features in Nirmata 3.0

Virtual Clusters: The promise of self-service DevOps is here! Operators can now allow developers to request virtual clusters, a secure slice of a physical Kubernetes cluster, by specifying the required resources and services. A Virtual Cluster is then automatically provisioned for the developer, who can use it to deploy and manage applications in a variety of different ways. The cluster operator can manage resource consumption and will be alerted if the cluster is near capacity or any shared services are not functioning at the configured SLAs. Developers can request additional capacity for their applications as needed and the operator can approve the request to automatically adjust the capacity limits for the virtual cluster. For more background on virtual clusters, see The Case for Virtual Kubernetes Clusters.

Workload Policy Management: Ensure your workloads are compliant with your security, resources, corporate policy, network, and access policies! Earlier this year, the Nirmata team launched an open source project, Kyverno aimed at addressing the challenges associated with workload policy management. Kyverno was built from the mature policy management framework in Nirmata, and has seen rapid adoption in the community and has recently announced GA. Nirmata has full integration and support for deploying and managing Kyverno policies as well as providing visibility into any policy violations. To learn about how to use Kyverno in your clusters, see 10 Kubernetes Best Practices You Can Easily Apply to Your Clusters.

Windows Support: Earlier this year, support for Windows containers in Kubernetes reached general availability. There are a significant number of workloads that run on Windows and now they can benefit from the automation enabled by Kubernetes. It is now possible to add Windows nodes to clusters managed by Nirmata and deploy Windows applications alongside the rest of the applications in your clusters.

Service Mesh Support: As the complexity of cloud native adoption grows, enterprise developers are exploring service mesh for security and visibility for their microservices-style applications. Nirmata offers a choice of service meshes and enables single-click deployment of service meshes such as Istio and advanced workflows such as blue-green deployments and traffic splitting.

Helm 3.0: Helm is arguably the most popular tool for packaging Kubernetes applications right now. Helm 3.0 addresses security and complexity issues that plagued the earlier versions. Nirmata always supported Helm packages and now extends that support to Helm 3.0. The Helm repository can be used as upstream to directly deploy applications to clusters.

All of the above features are available on the Nirmata Management Console and do not require any additional integration effort from customers. As enterprises continue to adopt cloud native technologies, they require a management platform that can eliminate operational complexities and reduce the initial Kubernetes complexity curve.

The Nirmata 3.0 release further solidifies Nirmata as the most intuitive, flexible and efficient Kubernetes management platform in the market. If you are interested in finding out how Nirmata can help accelerate your cloud-native journey, please reach out to request a demo or explore Nirmata for free at

Photo by Billy Huynh on Unsplash.

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