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.
Kubernetes / Service Mesh

Red Hat OpenShift 4.2 Addresses Requirements of Both Development and Operations

Red Hat releases OpenShift 4.2, a cloud native software stack.
Oct 16th, 2019 9:00am by
Featued image for: Red Hat OpenShift 4.2 Addresses Requirements of Both Development and Operations

Red Hat has released OpenShift 4.2 this week, with many of the features that were introduced with the release of OpenShift 4 earlier this year being moved further along toward general availability. While the OpenShift Service Mesh, OpenShift Serverless, and OpenShift Pipelines continue to mature, with the latter two available in technology preview and developer preview in OpenShift 4.2, the latest version of Red Hat’s managed Kubernetes extends its  multicloud support to include AWS, Azure and Google Cloud Platform, and private clouds like OpenStack, as well as air-gapped installations.

“We’re continuing to invest in the platform, but expanding into two areas more aggressively. One is providing more productive services for developers — new capabilities to make developers more productive on the platform,” said Joe Fernandes, vice president of product at Red Hat, in an interview with The New Stack. “The second is improving day one and day two operations for the administrators. That investment goes back to Red Hat’s acquisition of CoreOS, our investment in our Operators technology, and our investments in full-stack automation and day two monitoring and so forth.”

OpenShift Service Mesh, which was released several months after the initial release of OpenShift 4, combines the open source projects Istio, Kiali and Jaeger, as well as Prometheus and Grafana, to provide an easily implemented service mesh and speaks to this focus on day two operations. With OpenShift Serverless and OpenShift Pipelines moving into previews, developers get managed instances of Knative and Tekton, respectively, that are easily installed using Red Hat Operators. The inclusion of CodeReady Containers in OpenShift 4.2 also speaks to Fernandes’ first point of increasing developer productivity, serving as a local developer environment wherein developers can install a pre-built OpenShift environment on a laptop.

The other focus of OpenShift 4.2 is the move toward bringing the platform to more locations, hence the addition of Azure and Google Cloud Platform to existing AWS support. Beyond multicloud support, Fernandes explained that there are also a number of OpenShift customers with special requirements for non-traditional operating environments, such as air-gapped networks, which are not connected to external networks, making installations and updates difficult.

“Bringing Kubernetes to enterprise customers means addressing their requirements for how they want to run it. We’ve seen with OpenShift 3, and now continuing into OpenShift 4, that government customers and some financial services customers need to run in air-gapped environments,” said Fernandes. “Today, we have I think over 1300 customers now on OpenShift and some of those include government customers who want to run it on planes, ships, submarines and stuff like that. That creates challenges.”

As with any non-SaaS product release, there also remains the challenge of getting customers to update to more current versions, and Red Hat has released migration tooling to that end.

“We’ve seen hundreds of customers who’ve installed OpenShift 4 since we launched, but there’s many more that are still just evaluating it and planning the full migration, because, in their OpenShift 3 deployments, they may have dozens of clusters. They have lots of large environments and so generally the process is you kick the tires on OpenShift 4, understand it, and make sure that it’s going to work the way you want it to,” said Fernandes.

The migration tooling will examine a current OpenShift 3 deployment, discover all the namespaces and pods and services, and then allow the user to choose which parts they want to migrate, he explained.

“The cool thing is, it doesn’t just move the applications over it. It has a notion of state, so if your applications are connected to storage, it can either move the storage volumes over or reconnect them to the same pods running in your OpenShift 4 clusters. It’s more sophisticated than just a moving the pods over,” he said.

Finally, OpenShift 4.2 also supports OpenShift Container Storage 4, which is a software-defined storage stack currently available in beta. Today’s release of OpenShift 4.2 will be available in the coming weeks and is available for preview at

Red Hat is a sponsor at The New Stack.

Feature image by Zhang Linxuan 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.