bootstrap-vue-next VS porth

There's this project: https://github.com/bootstrap-vue/bootstrap-vue-next . But considering low number of dynamic components in Bootstrap, it is pretty easy to build a wrapper only for them yourself, and use other elements as simple HTML.

Moving over to typescript and vue 2.7 has been great, and we are making progress on refactoring our components to the composition API. But if by next summer there is no suitable replacement to bootstrap-vue ready, then there will be a lot of pain. I realize the maintainer of bootstrap-vue is in Ukraine so my hope is that this project can make it in time.

But it misses some really basic things. Like a carousel for example. So in the end, I got sidetracked making a PR for it: https://github.com/cdmoro/bootstrap-vue-3/pull/691

https://github.com/cdmoro/bootstrap-vue-3 wonder if anyone tried this guy’s version yet

Somebody already ported bootstrap vue here https://github.com/cdmoro/bootstrap-vue-3. not going to lie but your implementation seems like just a wrapper which people do not want html/css abstracted if they don't have extra functionality. I'd rather use my own components which literally take a few minutes to write and you can specify whatever you want in there instead of being restricted by using your library. Just seems like a headache to me when there is a bug or I need to expand on the feature, sorry just my honest feedback. Maybe the library could just be base components that people can copy paste?

I found a forked alternative that looks promising (https://github.com/cdmoro/bootstrap-vue-3)

Yes, unless there's another language I'm unfamiliar that shares the name. But the inspiration and some core ideas came from Porth: https://gitlab.com/tsoding/porth

Here's an interesting solution: in the language Porth which was inspired by forth (but takes some drastically different choices), there's an option to create separate scored bindings, which can either consume items from the top of the stack, or duplicate them, leading to some very slick solutions to the problem of limited access to the stack.

I personally haven't done that, but a very simple example, that I can think of is this one: porth-mode.el. The minor-mode doesen't do much, but maybe it helps understand the basic concepts.

You might want to look into Porth; IMO RPN doesn't have to be hard to read, Forth is just really terse and not very modern.

I believe Tsodings - Porth is a single pass compiler. Currently in development - it has some great vlogs and is also self hosting. He's recently said that re-implementing Porth straight up has become an issue for him - so please just take inspiration only. I suspect a concatenative language is quite a natural fit for a single pass compiler.

Tsoding did with his porth. Original conpiler written in python then reimplemented in porthq https://gitlab.com/tsoding/porth