naming issue

[Brian-ED]

I feel like this pun-less name is a serious waste of deliciousness. Theorefore may i suggest a bit of filling for your starving hunger for bacon!
bacon-nected
bqn-nected
both being a pun on "be connected".

web-of-bqn-strips is another pun, though a bit long.

these puns aren't exactly funny, so only consider these. You can probably find a better one :)

also i'm not sure if this repo is still being worked on. doesn't seem like it, but i feel like it could still use a funny name :)

[Caleb-T-Owens]

You are indeed correct, the name of this project is undeserving of its prestigious status as the most popular BQN web framework. I'm very grateful that you have brought this egregious issue to light. I will deliberate with Myself and Me and try to resolve this grave misnomer.

This project is not being actively worked on. At the time the cbqn-rs submodule was causing issues, but it's now available as a proper create online so that may work better. It would be good to at least get some of the essential web framework features finished like json parsing and more advanced routing. I have however been focusing my time on more... useful... ventures but if I'm feeling in the mood I might do some more work on this.

[Brian-ED]

Are you aware of https://github.com/mlochbaum/bqn-libs/blob/master/json.bqn for json parsing?
Also, good luck on your projects :)

[Caleb-T-Owens]

That is handy, thanks. I was originally trying to do all the work myself so I could understand all the code in the framework, but I might just import some of those files.

[Brian-ED]

maybe BQN-web-strips is better...
BQN-webstrips?