docker-socks-tunnel VS yazz

I'm the maintainer of HTTP Toolkit.

In general the source for core components that can't really be used for anything else is AGPL, but all the generally reusable libraries are Apache 2 or similar. The goal is to share as much as possible, and let everybody access the source for everything, and fork for their own use or submit modifications or whatever, but without the risk that a proprietary product runs off with the core product in a different direction. Seems to be working reasonably so far!

Regarding Docker, you might also be interested in https://github.com/httptoolkit/docker-socks-tunnel (1MB Docker container that runs a socks proxy, for tunnelling traffic between networks) and this detailed breakdown of how the whole Docker interception setup works under the hood: https://httptoolkit.com/docs/guides/docker/#the-technical-de...

Shameless plug. My own one of course :)

https://github.com/yazz/yazz

You can also try one I am building, a cross between Visual Basic and Microsoft Access here:

https://yazz.com/

i am working on such a thing myself at https://github.com/yazz/yazz. Also there are many other people trying to build something similar

I keep hacking away on Yazz for over 10 years now.... even if there is zero payoff I keep hacking... and that is what hackers do... we are not doing for the money... https://github.com/yazz/yazz

I really loved this talk and feel for Evan. As someone who was a VC/Angel investor in the space (I was the initial angel investor for something called LightTable/Eve) back in the day, worked for a couple of years at Red Hat, and am working on my own Open Source Language here: https://github.com/yazz/yazz (so yes, you could say I am a VC trying to build a low code product with my own hands), so I feel I have a valid opinions on this. I think that it is possible to make money in opensource as a little guy, but you need to have a combination of consulting, hosting, and support services. If your product is not able to encapsulate being sold and packaged as something that is possible to demo and sell to customers then you will most likely struggle to make a living from it

I am actually trying to make an open source successor, but using Javascript instead of Basic, at https://github.com/yazz/yazz and a demo at yazz.com

I'm still building a low code system with an easy to use component marketplace where you can edit components within the low code tool. Still a work in progress: https://github.com/yazz/yazz

Author of a framework that also stores it's code in IPFS for easy sharing (https://github.com/yazz/yazz). ScrapScript is a really nice concept with how it stores code. I originally got the idea for storing the code as a hash of the contents from Unison, and it looks like the idea is really starting to catch on with more and more languages now. Well done!

I’m working on a low core project that is already using content addressable source code that is stored in IPFS at https://github.com/yazz/yazz so it can be done

There are already some Dbos type systems out there. I built one which stores program state in SQLite databases and process state and programs are also stored in SQLite. In the oat I believe things like silver stream did the same too. The project I made is open source too: https://github.com/yazz/yazz