Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Härder, T.: DBMS Architecture – The Layer Model and its Evolution
jespersh722535dNah man, the db wars were the shit
netikras2202835dTimes are changing. Arguments are changing.
AlmondSauce776835dHeh, there's lots. It tends to go thus:
- Everyone uses their own thing
- Religious arguments ensue over which is best
- Some kind of standard (or a few standards) emerge, these slowly become generally accepted and then used without much question
- Few years / decades pass
- Someone says "Hey, this standard way sucks, look at my own thing I made instead!"
- Everyone else also makes their own thing
- Rinse and repeat.
It happens with everything - languages, filing systems, operating systems, paradigms, design patterns, database patterns, heck even in CPU architectures (with the like of riscv we may even see that kick off again in the medium to long term.)
cursee1870535dwars is in our blood :3
Lor-inc382834d@AlmondSauce That's just how things improve. You create a bunch of solutions, some of the less terrible ones become standard, you go on to "improve" something else, when the faults of the current situation become serious issues you revise it and generate a bunch of solutions again most of which are basically worse than the current standard, then hope that the next emerging standard isn't worse than the previous one.
Pains me to say it (I’m all team .net/Azure), but you forgot a step which happens during “Few years / decades pass” :
- A big company realises the full potential of standard and while still supporting it adds a proprietary layer. Which is good enough to convince a lot of enterprise clients use it. It becomes defacto for couple of years, until: “Your next line”