4 ms·

> They have a virtual DoM https://textual.textualize.io/api/dom_node/ https://textual.textualize.io/api/dom_node/ It's not a virtual DOM. It's not technically

by willm 2y ago

> They have a virtual DoM https://textual.textualize.io/api/dom_node/ https://textual.textualize.io/api/dom_node/ It's not a virtual DOM. It's not technically even a DOM, because there is no Document. The name has stuck, which is why we went with that. Technically, its a tree. One of the most common data structures used to represent a UI, and predates React by decades. > This includes a lot of what you'd expect from HTML, classes, CSS, etc. It has CSS in common with HTML. classes are pretty much required for CSS. That's not "a lot". But why shouldn't a UI framework borrow concepts that work for, you know, User Interfaces? > They have reactive attributes https://textual.textualize.io/guide/reactivity/ https://textual.textualize.io/guide/reactivity/ Reactives attributes are very useful concept to manage UI complexity. And again, not exclusive to React.

kragen 2y ago
this sounds like you're elaborating on why textual wants to be react rather than rebutting the assertion that textual wants to be react. but nobody was saying that wanting to be react was unreasonable hmm, well, i guess traverseda was sort of saying that react was bad. i doubt that's a widely shared opinion tho
- willm 2y ago
  I only meant to rebut the factual claims made in the previous comment. Textual is inspired by web development (and I've always described it as such), but "want to be react" is way overblown. It has things in common with React, but equally many other web and UI frameworks. Heck you could say that Textual wants to be JQuery, and that would be just as apt...
  - kragen 2y ago
    maybe it depends on what the implicit reference class is. if you're comparing it to react, angular, ncurses, s-lang, jquery, vue.js, and php, then sure, things like html and css are hardly react-specific. if you're comparing it to ncurses, s-lang, win32, mfc, the vic in the commodore 64, winforms, whiptail, dear imgui, the tms9918 used in the msx, emacs lisp markers and text properties, gtk, the nintendo ppu, opengl and glut, xlib, xt, tcl/tk, ansi.sys, naplps, ripscrip, turbovision, direct access menu.exe, and react, it's basically exactly the same thing as react jesus, i sure have built shitty user interfaces on a lot of platforms
  - yunohn 2y ago
    How is it more like jQuery than React?
- rojroy 2y ago
  [flagged]
  - rojroy 2y ago
    [flagged]

by willm 2y ago

kragen 2y ago

this sounds like you're elaborating on why textual wants to be react rather than rebutting the assertion that textual wants to be react. but nobody was saying that wanting to be react was unreasonable hmm, well, i guess traverseda was sort of saying that react was bad. i doubt that's a widely shared opinion tho

willm 2y ago
I only meant to rebut the factual claims made in the previous comment. Textual is inspired by web development (and I've always described it as such), but "want to be react" is way overblown. It has things in common with React, but equally many other web and UI frameworks. Heck you could say that Textual wants to be JQuery, and that would be just as apt...
- kragen 2y ago
  maybe it depends on what the implicit reference class is. if you're comparing it to react, angular, ncurses, s-lang, jquery, vue.js, and php, then sure, things like html and css are hardly react-specific. if you're comparing it to ncurses, s-lang, win32, mfc, the vic in the commodore 64, winforms, whiptail, dear imgui, the tms9918 used in the msx, emacs lisp markers and text properties, gtk, the nintendo ppu, opengl and glut, xlib, xt, tcl/tk, ansi.sys, naplps, ripscrip, turbovision, direct access menu.exe, and react, it's basically exactly the same thing as react jesus, i sure have built shitty user interfaces on a lot of platforms
- yunohn 2y ago
  How is it more like jQuery than React?
rojroy 2y ago
[flagged]
- rojroy 2y ago
  [flagged]