We have an entirely new system that supports Windows and Linux (macOS coming soon), providing you binary builds of the Perl core, Perl distros, and supporting C/C++ libraries.

Linux distrubutions generally come with Perl in the distribution's native packaging resp. building system. Dependencies are resolved by the same system. The same is true for the *BSDs. Further more, building a custom Perl on Linux, BSD and other Unixes is a solved problem. Even building tens or hundreds of specific perls is ridiculously simple thanks to perlbrew. All that's left is Windows, and for that, Strawberry does the job extremely well. I've switched from ActivePerl to Strawberry around 5.8.0 and never regretted that.

When you use our State Tool, you can create any number of entirely self-contained virtual environments, one per project. This makes switching between projects trivial and these virtual environments are easily shared across a team or organization.

Creating a virtual machine for a project is trivial, both on servers and workstations, and so is copying VM files around. VirtualBox, Proxmox, TrueNAS (as FreeBSD-based VM host using bhyve) are free. So what?

No more ActiveState Community License! The only licenses that apply are the original licenses for each open source package we build for you.

In other words, people were so annoyed that they stopped using your products and now you want to get them back?

You don't need a Platform account to try this out. But you can play with our system and sign up at any time and keep all the work you've done so far.

I don't need an account to try. What about continous use?

It's usually quite fast. If we've already built a particular distro/language core for the given platform, we use a cached version, so many builds take a few seconds. Entirely new builds are slower, but still faster than doing it by hand locally in many cases, because we distribute work throughout a build farm.

distcc, ccache. Both come prebundled even in ancient distributions like Slackware.

The core features are all free. Most features are free for public projects. We also have paid features including private projects, build engineering support, support for older platforms, indemnification, and more.

So far, I don't see anything that can't be done without Activestate, except for paying money for things that are free and come preinstalled.

The Platform has lots of other cool features like revisioned projects, advanced dependency resolution, and more.

So it uses git or svn?

Alexander