▲ | monooso 6 days ago | |||||||
> "Lots of people use it" doesn't make it good. I didn't say it was good (or bad), I said it's a perfectly viable approach. > Lots of people in the past have written "successful" web applications as loose PHP files with little structure, no classes, using associative arrays everywhere (including me when I was starting out), but today it's generally agreed upon that this is not a good idea. You're right, which is why, in 2025, no experienced developer builds web applications in this way. Plenty of experienced developers build web applications using the active record pattern. >Are there any hidden advantages I'm not aware of? You mean aside from others having a different opinion about the relative pros and cons of active record, or personal preference? | ||||||||
▲ | bakugo 5 days ago | parent [-] | |||||||
> Plenty of experienced developers build web applications using the active record pattern. Yes, but why? Why was the "loose PHP files with no framework" pattern abandoned, but not active record, when in many ways it's a remnant of the same era with many of the same drawbacks? > You mean aside from others having a different opinion about the relative pros and cons of active record I'm asking what the pros are. | ||||||||
|