#Codeigniter forceon json helper drivers#

Maybe, 'oh, it's just res.cookie('token', securelyRandomNumber())' vs. Authentication can be surprisingly simple. But by delegating it to complicated framework abstractions, we tend to guarantee that we never know how our app's authentication works.Ģ. This idea keeps us from ever learning how authentication works.

While this is the circulated wisdom, I would respond:ġ. > while I am certainly no security expert I certainly don't think there are right and wrong answers here, btw. I am well aware my priorities will not align with those who work on more important things.

We mostly produce bespoke back-of-house systems that small to medium-sized companies use to manage their operations.

#Codeigniter forceon json helper drivers#

You can certainly make the case that debugging something like background jobs is harder because Laravel supports multiple different queue drivers and does have to be very generalised (though in practice I find it's a very understandable codebase), but I will happily cede some control to not have to worry about that stuff myself, much in the same way I don't want to be writing my own database adaptor.įor what it's worth, I don't work on big systems. For a lot of the things I've listed, an application-specific implementation would be far from simple. Maybe that's naive, and it's probably an indictment of my own abilities, but the framework has hundreds of thousands of users and active support, while I am certainly no security expert.

I trust Laravel's auth code more than I would trust my own. I don't disagree in principal, but in practice: