News for hackers. Stuff that matters.

_nfin

systemd is a good thing (tm) - I recognize that and am grateful for it.

However.

In the beginning a lot of distros were "forced" to accept systemd because udev was merged into its codebase.

Systemd is great, but its group of devs are absolutely fucking terrible at public relations. Sometimes they make changes that upset users. Like the recent one that has (logind?) by default killing all user-created processes when the user logs out (this surprised people as it became a new default). Or the security incident before that where systemd made it possible for users to get access to framebuffer contents. Sometimes things happen.

It's just made worse when you go to the systemd group with your problem and they act like what they've done is correct and everybody should just live with it. Sometimes we're wrong, sometimes they're wrong. Poettering writes up these really long posts which are mostly good reads, but sometimes he calls us neckbeards who want to live in an unchanging, static past.

Great project, great code, great devs - but terrible attitudes [sometimes].

Re:Open Sourcers Race to Build Better Versions of Slack on Thursday March 17, 2016 @12:04AM (#11302501)
I don't understand your point - Slack can't scale for extremely large teams well. I've watched the desktop and web app grind to a halt on the first load of a channel because it's still loading in channel history/offline messages. Beyond that, when trying to tab-complete a nickname this similarly almost freezes the desktop app. This has been my experience as part of a team on Slack that has 4000+ users. These are client-side problems, really - but I don't see how you can say Slack scales better when all of its [great] features come at a cost that limit how large a team can be. The larger the team, the more noticeable it becomes.

The history should load in progressively as needed. Switching channels within the same team should be instant. I don't know how you fail at tab-completing nicknames and commands, but somehow they made that slow. I get the feeling rendering is not on a separate thread in the desktop app.

Anyway, you're right that not everyone needs to be on 7-9 networks with the ability to talk to everyone among those. Slack is great for teams of like 500 people and less (imo).

Now that we have IPv6 – do we need TCP/UDP port numbers anymore?

I have food for thought - the title says it but I'll try to elaborate on what I mean.TCP/UDP port numbers are used to multiplex traffic to the same IP, so multiple services can be made reachable. I can't find docs when searching to understand if this is the only reason they exist but that is what I believe is their only purpose.Recently I've started learning about Tor - you can make single...

( Read More... | 11 comments | 13 points | on HN )