>Is systemd going to be an obstacle when people want to port applications to
GNU Hurd or other Unix-like systems?
I suppose you mean “programs”. See my comment about the word
“application”.
We have always had system-specific features and programs and they are by
themselves not an obstacle to portability, but it is an obstacle to
portability when other programs require these features or depend on these
programs (instead of having them as a so called “optional dependency”).
For instance, using systemd to start an UNIX service (for instance the HTTP
server lighttpd) is not an obstacle to portability, We can readily use
System‐V style init or Upstart in another system (which may be just another
installation of the same distribution, a different distribution, or a
different operating system). It would be an obstacle to portability if
lighttpd did not work without systemd.
>Do you know any other inconveniences of systemd?
I can not comment on the vices and virtues of systemd, but there is plenty of
discussion in the web.