20thr

Hugo from Namespace here. Thanks for the kind words! We try really hard to be there for teams, appreciate you recognizing that.

The Cirrus team is fantastic, and they'll be missed in the market.

We've shared a few customers over the years, and we have an increasing number of folks moving over after this change.

Feel free to drop me a note at hugo at namespacelabs.com to chat about it.

These suggestions make a lot of sense.

At Namespace (namespace.so), we also take things one step further: GitHub jobs run under a cgroup with a subset of privileges by default.

Running a job with full capabilities, requires an explicit opt-in, you need to enable "privileged" mode.

Building a secure system requires many layers of protection, and we believe that the runtime should provide more of these layers out of the box (while managing the impact to the user experience).

(Disclaimer: I'm a founder at Namespace)

I spend a lot of time in CI (building https://namespace.so) and I agree with most of this:

- Treat pipelines as code. - Make pipelines parts composable, as code. - Be mindful of vendor lock-in and/or lack of portability (it is a trade-off).

For on-promise: if you're already deeply invested in running your own infrastructure, that seems like a good fit.

When thinking about how we build Namespace -- there are parts that are so important that we just build and run internally; and there are others where we find that the products in the market just bring a tremendous amount of value beyond self-hosting (Honeycomb is a prime example).

Use the tools that work best for you.

Hugo here, founder at Namespace. We built Foundation based on what we learned from building Boq at Google — the app platform that drives the dev/prod workflow of many of Google’s main apps.

We leaned heavily on composition that spans build, test and production. You can define assets that yield code-level infrastructure definitions and also are automatically configured based on environment (dev vs test vs prod).

It was great building it, and we use it to build Namespace (namespace.so); our development-focused platform.

100% -- EC2's general purpose nature is not in my opinion the best fit for ephemeral use-cases. You'll be constantly fighting the infrastructure as the set of trade-offs and design goals are widely different.

This is why CodeSandbox, Namespace, and even fly.io built special-purpose architectures to guarantee extremely start-up time.

In the case of Namespace it's ~2sec on cold boots with a set of user-supplied containers, with storage allocations.

(Disclaimer, I'm with Namespace -- https://namespace.so)

Let us know how it goes!

This is very cool.

We built something similar in https://github.com/namespacelabs/breakpoint but the more general purpose nature here is great.

Hi -- Namespace's CEO here; if you have a chance, please drop me a note at hugo-at-namespacelabs.com; I'd love to hear what we could be doing better in the UI, and product overall. Thank you!

Hugo @ Namespace (https://namespace.so)

You can use namespace.so today which provides the best performance for Github actions in the market.

With the added capability of cache volumes: high-performance zero-cost cross invocation caching.

Built by a team of ex-Googlers and ex-Digital Ocean.

Disclaimer: i’m founder and ceo (happy to answer any questions!)

We have a similar vision at namespace.so; we are starting with development and testing. But that’s the start.

(disclaimer: I’m part of the team)

Namespace Labs https://namespace.so

Looking for: Frontend / Design Engineers GTM / DevRel

Prefer near CET tz; remote friendly.

Namespace wants to help developer teams do more with less: faster cycles, and more focus on what matters.

Email me directly: hugo AT namespacelabs.com

Competitive pay and generous equity. We believe in shared incentives.

Add breakpoints (static or on failure) to GitHub Action workflows; and SSH in to understand and debug failures. Open-source.

Helsinki, Finland - Blaast (http://blaast.com)

Rocking mobile -- making it fun and accessible for millions of users and thousands of new developers.

Looking for various positions, from platform/backend, to operations, frontend and developer tools. We work with Scala, Java and Javascript. We are lean and fast. We deploy multiple times per day.

http://blaast.com/jobs

Blaast is building a cloud-powered mobile OS, designed around web technology. We're disrupting the medium by building a platform that offers a native-like user experience: our apps are beautiful, fast and always up to date. We get there by leveraging our cloud platform to offer features that you don't see in today's mobile devices.

Our product has stirred the interest of a few big players and we're close to land our product into the hands of millions of users. We are a team of 15 young guys from around the world, based in Helsinki, Finland, and funded by experienced guys including the co-founders of Skype.

We are looking for brilliant software engineers that are looking to work into new disruptive technology. Our platform is based on Java and Javascript (node.js).

To apply ping us at jobs@blaast.com.

Helsinki, Finland.

We're looking for Javascript developers, for both backend (node.js) and frontend work. Also Java developers, looking to work on something new.

http://blaast.com jobs@blaast.com