Indeed!
Beaker is a muchhhh slimmer and nicer codebase the more I look around it. 0.1 is big step forward, and this is part of the reason I originally proposed to focus on beaker first and brave/others if possible.
Brave does not seem like it’s going to enable use of electron.protocol anytime soon, which is quite the blocker for a straight up safe protocol.
It also comes with a lot of baggage that might not be useful for safe (ad blocking/ad replacement etc). ( it is so much more polished and has a lot of things that might be useful in a SAFE browser, too though).
I think there’s a lot of pros and cons, but what is clear is that I’ll be able to move much faster in a beaker fork / via plugins as required. And @PaulFrazee has been welcoming about PRs and forks so far (Beaker Plugins. Scan 'app/node_modules', instead of using global modules? · Issue #56 · beakerbrowser/beaker · GitHub ) so that might well end up being something ‘bleeding edge’, that allows us to define how/what we want a SAFE browser experience to look like, which we then port to other browsers via extensions as we’re able.