Is this proof that systemd is completely broken?

[Tom H]

On Sat, Jul 12, 2014 at 12:08 PM, Sam Varshavchik <mrsam at courier-mta.com> wrote:
> Tom Horsley writes:
>> On Sat, 12 Jul 2014 10:00:45 -0400
>> Sam Varshavchik wrote:
>>
>>> Now, here's my hack, which is basically a clone of that NetworkManager
>>> subpackage:
>>
>> You're willing to invest a lot more time in systemd than
>> I am :-). I just put a batch of systemctl restart commands in
>> the rc.local file with different time delays. It is
>> the only way I've gotten all the network services to start
>> reliably.
>
> Yeah, well, I don't really mind spending a few hours hacking up some script
> to workaround some stupid bug.
>
> But this is now looking more than just a stupid bug, after I saw how the
> server immediately booted up to a console login prompt, but still failed to
> respond to pings for another thirty or so seconds, until the network stack
> came up. If I wanted to boot an OS that gave me a user desktop before it
> finished setting up its network connections, I'd boot Windows 7.

Is there a rule that says that a system's network should be set up
before a getty login (which isn't a user desktop) is available?