Yeah, what could possibly be wrong with replacing everything with inferior reinvented wheels? ;)
Without looking at the code I can already say that this thing is broken and doesn't work right.

So what do you think is replaced again?

Putting down the code without even looking at does nothing more than disqualifying you from any reasonable discussion.

I won't discuss this here, I just added the tweet for general amusement. :)

So... that means both ntpd and time just got deprecated... at least they're now wholly focused on trying to deprecate the entire GNU operating system outright rather than just bits and pieces of GNU/Linux.

They should just fork the kernel already and create their own OS. At least GNU/Linux would still be GNU/Linux.

I still can't get that. Why do they have to reinvent/reimplement everything? Are they sick?

No their not sick; just completely perpetually misguided in the fact that they know what's best for everyone regardless if only they understand it, and everyone else is just stupid and shouldn't question them.

Don't worry Moisespedro, we can keep just about every piece of sane software out there alive through patches and project forks. We got HALd to build on kernel 3.14.4 now didn't we? Shouldn't be too hard to get anything else dusted off and working again with some effort and elbow grease.

You are going to have to explain that one.

Accepting the code without even looking at it does nothing more than disqualifying you from any reasonable discussion.

See how fun that is?

Well, for some values of "sense".

From RFC 5905:
I'll admit that my NTPD server is consuming an ENTIRE MEGABYTE of memory (RSS) on my desktop machine. Why, that's what the dbus-daemon consumes!

I can't believe that I tolerate such waste.

Did you even read the release notes? systemd-timesync is not a NTP server, it is merely a SNTP client, similar to the ntpdate command. Nothing is deprecated here. Please don't spread FUD, but actually read the available documentation.
On ssystems without real time clock, like many embedded systems, it makes sense to have a service that sets the time correctly, so that you have actual timestamps in your logs, instead of for example milliseconds from boot. Since the systemd suite contains a logger a SNTP client is IMHO a valuable addition.
Would only be fun if I had made a statement about the code quality, but I have only made statements about the general decision to add something like that to the systemd suite. I have not, I have merely pointed out that spouting "It is broken and doesn't work right, I don't have to look!" is a different thing, I would think.

I won't comment on your last post, it is a waste of time.

Right.

Now, if you were discussing embedded systems from, oh, the 1980's, then the size of the NTPD server would be a sticking point. (A whole megabyte when even a fully tricked out system might have only 64K.)

But now we are in the 21st century. ntpdate (not statically linked, so this size is too small) is ~95Kb. Any systemd embedded system will have some type of cron, won't it? So just run ntpdate on a cron job and be done with it versus creating a new specialized client.

Somehow I'm not surprised that systemd contains its very own logger. How special.

TobiSGD,

You are obviously highly technically proficient as you run Gentoo. However, as a Moderator it perhaps might be better if you dealt with violations of forum rules rather than engage in urination contests. I do note that onebuck and unSpawn are a bit more detached. Just a suggestion.

So...as a moderator, he's not allowed to have an opinion that runs counter to other forum members? Detachment aside, he's merely defending his position, and in spite of some of the baiting, he's managed to keep his cool.

Tobi is the only one actually being resonable re: systemd. The naysayers are comically ignorant and keep spewing the same FUD that was going around a year ago.

As for staying on topic, read this discussion about the link in the OP to see why it's mostly garbage.

I can't wait for systemd to be in Slackware.

Indeed. He has conducted himself very well in the debate. Again, my thoughts are suggestions, I don't want to tell anyone how to post. However, the position of Moderator does come with the responsibility of deescalating a thread if it heats up.