This is part 1: explain it to me simpler.
Part 2 : Be more specific
I have been at this for a long time. You might even say "building" is what I do for fun. We are building - its what we are doing anyway. We are "full-time" on HIVE this year, going all out. That doesn't mean that life stops, but just - "this is what we are doing".
If its valuable to HIVE, we might even do it better, faster and with more focus. Scroll down to see our AMA about the proposal - recorded in the HIVE discord - now uploaded to youtube.
What does it mean?
Let's unpack a few phrases first. Redhat style open-source microservices, "B2B Hive-as-a-Service Modules" - I believe these things are the essence of the proposal, and its all packed with a lot of meaning (to me).
"Redhat" (style):
If you don't know Redhat, you need to - they've become a leader in how technology "companies" can build a profitable business around free, community-developed software. We want to do that. Redhat IS the best practice example in the real world.
To put it simply - they open source everything, and charge for "service".
"B2B":
This does not mean "business" in the traditional sense, it could be a sole proprietorship, or a hustler. It means that this service is not for simple entertainment - it helps them achieve their goals. They are trying "to do something", for a specific reason or to achieve a specific goal (generally profit, but not always).
"HIVE-as-a-Service":
There is a reason that Facebook is not called NodeJSBook. No one cares (users that is) about your tech stack. "HIVE can do" many things, yes, but can I click a few buttons to actually use it? Software as a service is mainstream, for a reason.
"Module":
Our blockchain is so powerful. So each thing should be broken down into the simplest pieces. Then, other people can play with the legos (since yes, we are open sourcing)
"Microservices":
I don't think any of these things should cost all that much money. We have tx-free crypto for this right?; I can charge 11 cents a month for an auto-badger, if that's the number we come up with.
Nectar
We have released a pretty simple "kanban" about what is done, in progress, and needs to be done for our new libraries. You can actually query live nodes now, yay!
This is not about core chain code, this is about the 90% of free codecamp, mediocre learning-to-devs, want to play and flop around experimenting after pip install beem, strike that, reverse it:
pip install hive-nectar
https://peakd.com/nectar/@thecrazygm/nectar-progress
We did an AMA!
I think it went really well. So good. Why don't you listen and let me know?
