The SecureLang® brand is great for my core products as I want to focus on compiler-like infrastructure, but my products for new machines are simply taking too long between waiting on new hardware and trying to find a work/life balance funded by income somehow.
So I’ve decided to launch a second brand in the meantime for legacy hardware support based on stable open-source solutions. I think I’ll be able to use my core mechanical skills very productively in the world of second-hand servers, but I’ll be launching as a second brand to avoid confusion with the SecureLang® SL/RD OS which is targeted at research on new hardware.
Branding Yet To Be Finalised
A domain has already been registered for the new brand but it will be introduced gradually, probably without a new website initially although I have some plans to add like a generic code sharing site later (think like the git sites but hopefully with less git).
Combined Focus: High Performance Computing
The linking element of the brands (aside from links back to the main SecureLang site) will be a combined focus on lightweight HPC solutions: The new brand will cover the “Legacy HPC” field such as making ideal use of old server hardware, while the core SecureLang brand will be focused on upcoming CPUs: RISC-V and quantum computing.
Both brands will eventually offer some solutions for FPGA enthusiasts, although I haven’t been able to get to a point with FPGAs myself where I’m confident developing reliable devices with them. Someone out there will be much better at that game than I am, so I want to market robust operating systems for all of your experimental chips whether retro or futuristic in design.
The SecureLang Brand Will Be More Security Focused
The SecureLang® brand will retain it’s cybersecurity roots whereas this will be less emphasised in the new brand, I don’t recommend 2010-era CPUs if security is your main concern but they are still solid for database backend and lighter AI work if we just ignore the more public facing servers.
The SecureLang® SL/RD product still in development will increasingly have a strong cybersecurity focus, while the legacy support brand will be more concerned with patching solutions that already work. And SL/RD will not be rebranded to sound more appealing as per earlier plans, it will keep it’s original technical name and mainframe styling.
Leave a Reply