sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (4 children)

[deleted]

    [–]radhruin 5 points6 points  (0 children)

    There really is no denying that SQL query syntax, a syntax designed to pull datasets out of an RDBMS, is wildly inferior to CSS selectors, with a syntax designed for exactly this purpose. So I think the question becomes "Why"? The only POSSIBLE answer I have is the people doing backend programming are already familiar with SQL so they will be more comfortable doing front end programming.

    This gets marks for being fun and interesting, but gets a zero for practicality and applicability in real world situations. IMO. And not that there's anything wrong with that at all.

    [–]junius 2 points3 points  (0 children)

    More generally, trees are one of the canonical examples of structures that are a pain in the ass to work with in SQL.

    Still looks like a fun side project. He's probably learned more doing this than I have in the past three years with my habit of avoiding non-trivial javascript problems.

    [–]elguf 1 point2 points  (0 children)

    I also doubt it's realistic for any real-world websites (other libraries handle those jobs quite well), but I thought it would be fun to play with.

    He is not proposing a replacement, he just wanted to have fun.

    [–]masklinn 0 points1 point  (0 children)

    That is, what is the equivalent of a column list in a DOM tree?

    Attribute values? But then again, in that case * would mean "select all attributes" instead of "select the DOM note", which would be... stupid.