29
2024 Stack Overflow Developer Survey (Page Technology)
(survey.stackoverflow.co)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Jul 2024
29 points (93.9% liked)
Programming
17314 readers
106 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
I don't see why not. It has a sublanguage which can be used to query - same with SQL. You can do other things in SQL besides querying as well, so why not?
C# also has a built-in query language (LINQ). I think it might just be simpler to group them together to avoid nuances like these, though I don't think anyone would complain about not seeing LINQ on a query language list either.
Personally, I would like to see LINQ query syntax and LINQ method syntax separated too. Because I find method syntax very useful (for simple or linear-spread-cascading queries), but I find query syntax hard to read and reason. Even worse so when it introduces variables. I don't want to see it anywhere in my projects. But method syntax has clear reasoning borders and I enjoy using it (up to a certain query complexity).
I also avoid query syntax generally because I find it hard to map to method syntax with more complex queries. It's a cool concept though, despite it being painful to use.
Do we list it in both categories then? Query languages and scripting languages?