Nice to always see this on HN... we have more landscapes out there too :)<p><a href="https://landscapes.dev" rel="nofollow">https://landscapes.dev</a><p>There are also two sub landscapes in the CNCF landscape in case you're interested:<p><a href="https://landscape.cncf.io/serverless" rel="nofollow">https://landscape.cncf.io/serverless</a>
<a href="https://landscape.cncf.io/wasm" rel="nofollow">https://landscape.cncf.io/wasm</a> (still in beta)<p>There's also a secret feature that shows who is raising funding etc in the space:
<a href="https://landscape.cncf.io/funding.html" rel="nofollow">https://landscape.cncf.io/funding.html</a><p>Anyways, I know people like to hate on the cloud native landscape but the reality of the situation is that there is a large healthy competitive ecosystem out there and a lot of options.
Once upon a time, the landscape in hadoop and bigdata had something like this. Projects, companies and startups with weird animal names. I miss those days where you couldn't tell a difference it was name of a bigdata project or pokemon.
I built out my first ISP in 2001, worked in FAANG by 2006, haven't the slightest comprehension of what this is for. Is it some kind of certified partner directory?
There’s another one of these dashboards linked which specifies JIRA as the only change management issue tracker.<p>That’s scary.<p>Seems like this isn’t really saying anything. But maybe useful to find things to look at further?
It seems like Kubernetes has reinvented JCL from the IBM Mainframe<p>From the Wikipedia pager for JCL:<p>"Job Control Language (JCL) is a name for scripting languages used on IBM mainframe operating systems to instruct the system on how to run a batch job or start a subsystem.[1]<p>More specifically, the purpose of JCL is to say which programs to run, using which files or devices [2] for input or output, and at times to also indicate under what conditions to skip a step."