3 ms·
One of the reasons listed was better security by having no code executed on the server. That argument falls apart if you're willing to have some code running.
by mseebach 17y ago
One of the reasons listed was better security by having no code executed on the server. That argument falls apart if you're willing to have some code running.
- jrockway 17y agoThe webserver and OS are not code? Oh, you mean world-accessible PHP scripts. That's easy to fix by letting your webserver handle authentication to /admin.
- mseebach 17y agoCode that has write-permission to anything fancy. I'm in pedantic territory here, I don't particularly mind the idea of generating static files. My personal opinion is that having a dynamic frontend with fast caching for the most popular views is a better solution for that vast majority of CMS/blog (ie: dynamic) sites out there. What I do mind, are "I use semi-obscure technology X, here's why X is better than established, proven and hugely popular technology Y in every conceivable way" style ego-boosting articles. I'd rather read a show and tell about how this technology solved a real-life problem for you. I also enjoy the honesty of acknowledging the shortcomings.
- tptacek 17y agoNah, sorry. You're taking the logic here too far. Having no code accessible pre-auth is a huge win. Only having to worry about the authentication attack surface is a drastic improvement over Wordpress, which stores admin accounts in the same database table as anonymous blog commenters.