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 / Cloud Services / Open Source

Pancakes Are Delicious and Data Centers Are for Free Stuff

Oct 11th, 2021 10:00am by
Featued image for: Pancakes Are Delicious and Data Centers Are for Free Stuff

The data center is a building with racks of servers, networking gear, raised floors with cables flowing underneath, and transformers to direct power flowing off the municipal grid.

But why is the data center needed? Why, this age of cloud computing, is the data center market expected to grow to $59 billion by 2025, up from a current value today of $32 billion as Gartner so predicts?

One argument: free software. Free, open source software is built by lots of developers who then share it with anyone who wants to use it. It then gets integrated into services that are core to how we live and work. In the cloud native world, these open source technologies are the base for what we are witnessing as one of the great renaissances in enterprise software markets.

The name of the game is scale. And the software that can scale is often free and open source but costs billions to run on cloud services, data centers and devices. The cost of scale is incurred by the consumer, be they a developer, a DevOps engineer, or one of the billions of end users like you and me.

With anything free and pretty decent quality, you’re going to need excellent infrastructure. It may not the newest and shiniest, but the hardware has to be capable to manage modern workloads with considerations for issues such as latency. Of course, the software has to be coded well so it does not waste hardware resources. Open source components have to run on any node imaginable. That may be a server in an enterprise data center or an observability service for a network running microservices. The costs add up.

Open source software and scale is a reality of almost any form of software development, which leads to a few questions that we are thinking about in prep for our pancake breakfast with Mirantis on Friday, Oct. 15 in Los Angeles at KubeCon+CloudNativeCon.

Like open source software, our pancakes are free (and delicious), but I digress.

Here are some of the discussions we look to foster:

  • What is different now in the data center compared to five years ago, and in the days before the pandemic?
  • How has free, open source affected at scale development, deployment and management?
  • What is the future of the data center based upon the shifts that have happened in the world over the past one to five years?
  • Has the increased popularity in microservices changed the dynamics of managing infrastructure? How so?
  • How is open source keeping up or even falling behind as the demand for services scale?
  • What are the challenges in storage, networking, and compute when it comes to the experience and ease of use for the developer?

At the Open Source Summit in September, Linux Foundation Executive Director Jim Zemlin said that in 2016, applications on average had 86 open source software components. Today, the average number of components is 528.

In the days that REST APIs became popular, circa 2006-2007, companies like Twitter emerged and built APIs that allowed anyone, really, to access the data on their platforms. All that API traffic with unprecedented loads made at-scale susceptible to outages. Twitter later adopted Mesos, a young open source project out of the University of California at Berkeley. Over time, Twitter built an open source stack that could scale in their own data centers with a bit of Google Cloud for Hadoop clusters and cold storage.

Today, scaling out means even the hardware is needing to be made in new forms. The hardware is often custom-built — not open source yet, but with projects like RISC-V, that train is coming to the hardware market, too.

Kubernetes became the successor to Mesos. Today, cloud native architectures are pretty much built on container infrastructure. But how can companies really leverage open source without investing all their resources into the effort? Do you really have to do it all yourself? I think that’s the question Mirantis is poising with its data center as a service concept. Build an open source infrastructure in your own data center and then leverage the compute, network and storage of the cloud.

Is that the future? We look forward to discussing over a short stack with The New Stack at KubeCon in Los Angeles.

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