7 ms·
Databases shouldn't be exciting. They should just work. The main reason webcrap works is because the databases underneath work. If the Javascript crowd had to
by Animats 6y ago
Databases shouldn't be exciting. They should just work.
The main reason webcrap works is because the databases underneath work. If the Javascript crowd had to manage data storage, nothing persistent would work reliably.
- msla 6y ago> Databases shouldn't be exciting. They should just work. A complicated thing which just works is exciting.
- bigbubba 6y agoOne man's exciting is another's snorefest. A lot of people would probably laugh at the suggestion that anything involving computers could be exciting.
- systemvoltage 6y agoIt is unproductive to talk about subjective opinions of excitement. The GP was referring to "Databases shouldn't be exciting" - not in the traditional sense of the word, but a metaphor that hinges on "excitement" being new features, frivolous decorations, unnecessary tangents, losing vision of what a database should do, frantic patching and heated bikeshedding discussions. It wasn't meant as "Ooooo I am excited about a database".
- bigbubba 6y agoI think you're restating my point.
- systemvoltage 6y agoIt is often downvoted to talk about the "javascript crowd" on HN, but I've worked in software industry long enough to unequivocally and with certainty say that it totally lives up to the cliches. It never gets old to scold people that are not serious, disciplined and principled in their endeavors that affect the rest of the world. Javascript community absolutely deserves the avalanche of criticisms they face. It is the reason why the modern web sucks, and frankly - I wish folks at Postgres would develop a new web standards including browsers that are not governed by corporations and can be implemented in a couple of weeks. Not trivializing what goes into building browsers, but making the whole standard small enough so any one can build a browser during a sabbatical.
- dfee 6y agoThat’s quite the perspective. It’s a big enough world where you don’t have to interact with every technology that exists, but this is one of the more prevalent ones - and you might find it useful to make peace with that community. Anyway, good luck out there.
- noir_lord 6y agoI'm seeing this in action now, the difference between the backend code and the frontend code is stark and the backend code isn't up to my standard either (and my standards aren't that high, I know I'm merely competent for many places). It just seems to be the nature of the web side of things, lots of sloppiness. The devs are smart enough, they just don't think and it shows. That or they use something but clearly don't understand the thing they are using. I replaced nearly 500 lines of code with ~60 by taking a bunch of massive conditonals re-ordering them then extracting them into methods and returning on the simple case. This isn't voodoo, you have to work harder and remember more to do it the wrong way. Also comments, they don't seem to understand you document why you did the thing, not what you did, what you did is in the code, I don't trust your comments to tell me what you did, I want to know why you did it. That and general documentation (cross link stuff, link at the top of the class to the documentation in the wiki, update the documentation when you get a ticket that changes the behaviour, write the high level flow in plain english a 10 year old could understand). rant over. I actually like my job, the people are lovely and the work is interesting its just frustrating when an ounce of thought saves a pound of cure.
- soneca 6y agoShould I assume from your comment that you never saw code worth improving other than those written by JavaScript developers?
- noir_lord 6y agoNo.
- robertlagrant 6y ago
- hashtagmarkup 6y ago> If the Javascript crowd had to manage data storage, nothing persistent would work reliably. Wait until this guy learns what the JS in "json" column types means, and how the largest webcrap sites rely on them for persistence.
- kulig 6y agoJson is just a format. There are trillions of formats that work just as well as json.
- LukeShu 6y agoNote that 'Animats didn't comment on JS as a technology, he commented on the crowd. In 2017 Bryan Cantrill gave a wonderful talk titled "Platform as a Reflection of Values: Joyent, Node.js and Beyond" https://vimeo.com/230142234 https://vimeo.com/230142234 In it, he talks about how even though they liked JS as a technology, they came to realize that the values of the JS/Node.js community differed from their values at Joyent. In the talk (at around 19:30), he identifies that in 2014 Joyent's core values wrt node.js were "debuggability", "robustness", and "stability"; while the core values of the broader node.js community were "approachability", "expressiveness", and "velocity". And there's nothing wrong with either of those sets values, but they're not the same! With that lens, I'd characterize the parent comment as contrasting the PostgreSQL team's core value of "robustness" with the Javascript crowd's core value of "velocity". That's a distinction in values, not in technology.
- edgyquant 6y agoJson has nothing to do with the persistence part.
- hashtagmarkup 6y agoIf you need to persistently store frontend state in the backend, would it not be easier to use the native frontend data format? It's not entirely about persistence... it's about the ease and reliability of the persistence.
- 6y ago
- dragonwriter 6y ago> Databases shouldn't be exciting. They should just work. With enough experience with the alternative, things that just work are exciting.
- auggierose 6y agoAmen.
- raarts 6y agoHear, hear.
- anakaine 6y agoSeconded.
- loco5niner 6y agoAnd it's wonderful to work with someone whose stuff just works
- baybal2 6y agoPG steamrolls every other general purpose database, and has tons of extensions, and frontends so you can use it in any database paradigm. With 30m minutes of time, you can turn it into a document db, log/time series db, columnar, graph, key value, whatever
- pricechild 6y agoI bet we'd both seriously consider (if not prefer) sqlite over postgres in a bunch of scenarios?
- api 6y agoSQLite is amazing, and “lite” is really not fair. I’ve seen it handle 1tb+ with at least decent performance. It’s not a replacement for a real DB but it is damn close.
- robertlagrant 6y agoIt's not, because it is a real DB. It's just one for single user access only.
- bachmeier 6y ago> Think of SQLite not as a replacement for Oracle but as a replacement for fopen(). https://sqlite.org/about.html https://sqlite.org/about.html
- Koshkin 6y agoWell sure, it’s better be thought of as a replacement for fopen() than one for Oracle. (Unless you were thinking of buying Oracle in order to use it on your desktop.) An even better way would be to compare it with MS Access, for example.
- Rodeoclash 6y agoActually as I understand it (and a couple of minutes Googling doesn't back up my case) the "lite" on the end is pronounced "ite" and refers more to SQL as a geology like term. In other words, the SQL is a rock.
- jeff-davis 6y agoA lot of people imagine databases that way, but they are complex beasts with a lot of features. Everyone seems to say features don't matter, except of course for the ones that they use. Which is often a growing set as your application matures. All of these features are exciting to the people that can use them.
- lhnz 6y ago> If the Javascript crowd had to manage data storage, > nothing persistent would work reliably. There are different incentives to writing UIs than there are when you're writing a backend. Often a business needs you to iterate very quickly, so people change their practices to suit this. Some are able to get away with never raising the quality bar once they finish iterating and it's unfortunate how the industry allows this. Additionally, there are, of course, teams and companies that want high quality code, but even here quality is defined differently from how it would be for data storage logic. For instance, it often means "high framerate" and "easy to understand", instead of "optimal" and "robust". There are less JavaScript engineers writing backend code, and most that do this are generally making simplistic CRUD Node.js apps. However, there are companies and people that specialise in high-quality complex Node.js apps, and they try just as hard as backend engineers from other programming languages to do this well. (I'm thinking of projects made by developers on the core Node team. I've seen good backend code there, perhaps because they're more aware of lower-level concerns.) I personally write a lot of JavaScript/TypeScript code and I try to do a good job, but a "good job" is defined differently depending on the kind of product you're creating. Edit: I just realised you are _the John Nagle_, so you likely have a more refined taste in certain kinds of programming than I do, however I think my point about incentives probably still stands.