rio.Text(self.name, justify="left"),
Becomes: <span style="[...] text-align: left;">Dataset 1</span>
I'd prefer: rio.Span(self.name, text_align="left") rio.Text(self.name, justify="left"),
Becomes: <span style="[...] text-align: left;">Dataset 1</span>
I'd prefer: rio.Span(self.name, text_align="left") justify-content: center;
justify-content: start;
justify-content: end;
justify-content: flex-start;
justify-content: flex-end;
justify-content: left;
justify-content: right;Think of it like how Python has renamed a lot of things. What other languages call arrays, Python calls lists. HashTables are dicts, and so on. Python has faced a lot of resistance here from people that got used to the more technical names, but I think the popularity of the language speaks for itself. Easy to understand, meaningful names are a plus, not a downside :D
That is just false if you ask me. Eventually you reach the limits of the API defined by a framework and users will have to reach out to HTML and CSS. And now is there not only a level of indirection, but also all of the existing documentation from the Web Platform cannot be applied.
I think there is validity for having a Python based system (instead of JS) that runs on the client to render standard HTML and CSS, but this goes beyond that and will just become an immense scope creep.
Calling them arrays would be very confusing to everybody who expects a typical array: a pointer with some empty space after it.
The implementation defines the underlying data structure as PyObject *ob_item
When I said array, I specifically meant O(1) access, which is in contrast to linked lists, which the name "list" would seem to imply.
Also, let's not pretend that html/css is particularly well designed or easy too learn. It's the backwards compatible result of decades of experimentation, where the initial design did not even remotely consider building interactive apps with it.
Modern web app dev requires learning way to much (archaic) stuff, just to create something that ought to be simple. Rio at least seems to be trying hard to address that.