6 ms·
I've spent most of my career hoping that something - anything that's better than SQL will come along and replace it. It's like FORTRAN, except FORTRAN has had
by cratermoon 5y ago
I've spent most of my career hoping that something - anything that's better than SQL will come along and replace it. It's like FORTRAN, except FORTRAN has had the decency to stay in use where it's really the best choice. But SQL is out there, like Clippy. "Hey, I see you're collecting some data. SELECT TRUE FROM HELP WHERE COLLECTING_DATA IS TRUE
- urthor 5y agoNobody else has invented any other declarative language it seems. Come on aspiring post-docs, do your thing and launch a new programming language. If MIT can launch Julia someone can launch a language that's not SQL.
- pjmlp 5y agoLike Kusto? https://docs.microsoft.com/en-us/azure/data-explorer/kusto/concepts/ https://docs.microsoft.com/en-us/azure/data-explorer/kusto/c... https://docs.microsoft.com/en-us/azure/data-explorer/ https://docs.microsoft.com/en-us/azure/data-explorer/
- urthor 5y agoHmm. It's read only, but holy shit please become popular and displace non-ANSI SQL in my life.
- BiteCode_dev 5y agoEdgeql is trying.
- masklinn 5y ago> Nobody else has invented any other declarative language it seems. Postgres was originally built on one: https://en.m.wikipedia.org/wiki/QUEL_query_languages https://en.m.wikipedia.org/wiki/QUEL_query_languages There’s also D/D4/Dataphor, though i’m less convinced. Unsurprisingly that mostly died out after sql took over everything.
- goto11 5y agoThere are multiple alternatives. Problem is SQL is "good enough" and ubiquitous and deeply entrenched. It will be extremely difficult for any alternative language to unseat SQL.
- kumarvvr 5y agoThe closest that many have come to is to develop ORM libraries. LINQ + EntityFramework Core is my favorite.
- mike_hock 5y agoHe said better than SQL.
- kumarvvr 5y agoTo me, ORM code is better than raw SQL. But, a lot many applications can be developed without really knowing the depths of SQL with help of the ORM itself.
- m_mueller 5y agoIs it? All that's ever worked for me with ORMs are simple CRUD apps that don't require referential integrity. We currently need to support one built on Django/ORM where this isn't the case and e.g. deleting an object can require deleting thousands of others.... which the ORM helpfully renders into thousands of queries and can take you half an hour. Luckily the creators soon decided to switch off all timeouts....
- sebmellen 5y agoI have had amazing luck with Prisma.io on the oracle side
- setr 5y agoLINQ is a much nicer SQL IME, at least for CRUD operations — but I generally don’t use the “objects” part of it except for very rudimentary insert/deletes. However group by specifically seems to be a hack, and it falls on its face in weird ways almost every time I use it. I’m not sure how much I like it’s “AST rewriting” model, but it works great when it works. Just the LET command alone justifies it
- xupybd 5y agoI'm normally not a fan of ORMs but I've had good experiences with Entity Framework. I really like the automatic migrations. For small apps and a single dev it hits a sweet spot. I find .Net really good at being kitchen sink included and business ready. If you're making internal small apps I've yet to find a better platform. Especially if you're in an MS Office heavy environment.
- pjmlp 5y agoKusto, https://docs.microsoft.com/en-us/azure/data-explorer/ https://docs.microsoft.com/en-us/azure/data-explorer/
- downWidOutaFite 5y agoEdgeQL looks promising https://www.edgedb.com/docs/edgeql/overview https://www.edgedb.com/docs/edgeql/overview
- BulgarianIdiot 5y ago> I've spent most of my career hoping that something - anything that's better than SQL will come along and replace it. So, if we put aside Clippy jokes and so on, what's your problem with SQL exactly and what does "better than SQL" mean to you? Because what I saw in the last couple of decades is the NoSQL movement lose air, and half the products representing it adding some sort of SQL dialect support, which if you think about it is hilarious admission of defeat. SQL is exceptionally good at being a relational algebra language, and if you think in terms of relational algebra, you might find out there's nothing wrong with it, aside from superficial remarks like "FROM should come before SELECT".
- BiteCode_dev 5y agoIt's super verbose, doesn't compose well with the host language primitives, is hard to introspect, full of gotchas and very low level.
- BulgarianIdiot 5y agoDatabases have no "host" they have "clients" which are heterogenous. So directing this critique at SQL is completely unfounded. .NET added LINQ and now basic queries are integrated. It was not up to SQL, it was up to .NET And calling it "very low-level" makes me question if you understand what SQL does and is. It's probably the only mainstream 4th generation language I can think of. https://en.wikipedia.org/wiki/Fourth-generation_programming_language https://en.wikipedia.org/wiki/Fourth-generation_programming_...
- BiteCode_dev 5y agoHost language, as in the language of your app that embeds some sql code, not host related to the db. The host language may or may not be the client language. It's low level because it lacks abstraction and anything outside the data query declarative paradigm is subpar. It has no notion of anything outside of itself, so it's a very restrictive inflexible dsl living in it's own bubble. And even worst, it lacks elegant abstractions for problems we've have had for decades, such as pagination, hierarchy, etc Also, using linq as an example rather shows your lack of understanding of the field of abstractions for sql. The state of the art ORM is currently SQLA, the leading innovation to replace sql as a dsl is edgeql, both are addressing sql pain points while aiming at allowing you to do all of what sql could do.
- wvenable 5y agoSQL may look ugly but it got the fundamentals correct. It's sort of like Git in that way. SQL is hard to replace because most replacements are either not radical enough to make migration worth it or so radical that it's something else entirely.
- setr 5y agoThe problem with SQL is that it doesn’t have the fundamentals correct — it doesn’t compose well, the language is an arbitrary hodgepodge of keywords, it conflates data administration with data manipulation/retrieval, it runs a ternary logic under boolean terms — leading to both potential for false negatives and false positives, it lacks a real standard (it has one, but it standardizes very little, and gets extended arbitrarily), it lacks any useful standard for libraries — causing your choice of DB to essentially also be your choice of standard library. As a language, SQL is a downright mess. The only thing it really got right was being based on the relational algebra and model. It’s also why language tooling is utter garbage is the DBA world. The lack of real Autocorrect/suggestion, code formatters, useful error messages, static typing (the tables & views are strictly typed, but your queries can’t be?), the lack of interoperability, etc all stem from how awful SQL is at being a programming language. Jumping from C# to SQL is like viewing a portal into the 80’s — it’s ridiculous. Hell, the standard itself is behind a damned paywall. If that’s not a signal of something going horribly wrong, I don’t know what is What I’ve never understood is why open source databases don’t have alternative frontends to SQL — where’s my first-class support for datalog in Postgres? Or even just a SQL dialect that lets me put FROM before SELECT so autocomplete can do something useful for once?
- reedf1 5y agoThe monkey's paw - you get your wish, but now instead of one annoying query language, you have two!
- thrill 5y agoStandards - the thing that we need more of and that we have too many of.