Pelican is a static site generator. This means that it generates static HTML files using templates and content as input, which can be then uploaded (via rsync, for example) to a plain vanilla web server (I use nginx).
So far the experience has been fairly smooth. The web server setup is much simpler, since there's no application to run. And it's forced me to re-think what kinds of information I want on my pages. For example, in an effort to avoid regenerating the entire site every time I publish an article, I created standalone index pages for tags, categories and archives rather than display the counts on every page.
That being said, the move does come with some drawbacks, in that some common features are a bit more difficult to implement. One example is comments; because the pages are static, you cannot simply tack on the comments when the page is generated. Not efficiently, at least - it would require regenerating a batch of HTML pages every time someone added a comment, which isn't very scalable past a certain level of traffic.
(Interestingly, some people do exactly that - they regenerate their entire site when a new comment is submitted. And though I certainly don't get nearly enough traffic on my blog to have any real concerns about the efficiency of this procedure, it's still an assault on my sense of aesthetics).
Is this a big deal? Objectively, of course not - I don't think I've ever seen someone access my site with a text only browser. But I can't shake the feeling that I've lost something, that I've given something up.
Like I said, it's doable - but would I ever actually go to the trouble? Probably not. But I'm still allowed to feel a little sad.