If you believe Pulse is rock solid or used by the entire world, I can only imagine that you don't get out much. The rest of your comment seems to be responding to something that I didn't write, so I guess I'll ignore it.
Replies like yours make me wish the reply button was disabled until you actually read and understood the comment to which you were replying. You obviously did not.
After having repeatedly run into the limitations of SysV init, I'm all for replacing it with something smarter, but I'm torn between these two.
I've used Upstart on Ubuntu, both as an admin and as a developer. I like that the commands and configuration files are clean and pretty easy to understand. A few things bother me, though:
- The model of starting all dependent services when their dependencies start is backwards. I don't necessarily want init to launch every daemon under the sun the moment I mount their data filesystem. I'd rather have it mount the required filesystem when I ask for a particular daemon to start.
- As of a year or so ago, the documentation was mainly an incomplete bunch of blog posts. Once I found them, it was pretty easy to configure daemons that behaved like the venerable ones that are often used as examples, but it was difficult to learn how to match Upstart's features (some of which are undocumented) and events (also largely undocumented) with an unusual service's behavior
- Debugging was difficult, mainly because so few events are well documented and it's not always clear which of Upstart's features are implemented in in any given version. (I hear the latest release offers some event tracing tools that would improve this.)
I haven't used Systemd at all, but the common points that come up again and again in every writeup I encounter have me forming me some opinions already. I really like the idea of the load-as-needed dependency model. A few things have me quite worried about the implementation, though:
- Configuration is reportedly difficult to understand. That always leads to frustrating, time-wasting, messy problems.
- The code is reportly rather complex. That usually leads to chronically buggy software, which is not what I want in a process as important as init. It also tends to hamper portability, which could make Systemd a poor candidate for replacing init on other unixes, which would relegate it to being yet another OS-specific hassle for coders and admins all over the world. I'd prefer something that could reasonably be adopted everywhere, or at least by most of the operating systems I have to administer, even if a few features weren't available on every platform
- I recently learned that the guy behind Systemd is the same guy who brought us PulseAudio. I don't want to get off topic here, but this gives me little hope that Systemd will ever work well outside the lead developers' development machines. (Pulse is around 10 years old now, and every time I give it another chance, it proves itself intolerable.)
"How much freer could Android be? The entire platform is open source.
Let's see... how many of my android devices have come with the complete source code required to modify, rebuild, and run the software that came installed on them, without any loss of functionality?
And that's the point. The Android Open Source Platform might be Free, but our phones are not running the Android Open Source Platform; they come with derivatives of it that usually depend on proprietary, closed-source differences. The result is that I don't have a reaonsable way to verify that my device is doing what I think it should be doing, or to keep it updated with security patches, or to be sure that I have disabled every bit of privacy-invading crap that hides in those commercial ROM images. The closest I can get is replacing most of the stock software with an open source alternative, which is not the same thing and (if I can manage to find one at all) usually means breaking several bits of functionality that I paid for when I bought the device.
I didn't know that name until I read it here. You mean to tell me that the guy behind systemd is the same guy responsible for PulseAudio? Oh, hell. I had hope for systemd until I read that.
Irrelevant. We're not asking for their driver code, we're asking for documentation on the hardware that we buy from them, so that we can write our own driver code.
Sadly, warning about certificate changes is practically useless today, since so many of the major sites have a bazillion different certificates, any of which might be the one you get at any given time. I stopped using Certificate Patrol for google sites because it was raising alarms almost every time I visited one.
Thanks for the link to the votes. Despite my disgust at the outcome, I'm pleased to see that my representative voted to defund the spying.
Maybe this will give me the motivation to stop channeling my instant messaging through google servers.
"CSI" convinced people that the crappiest image can be enhanced up to a perfectly clear picture in a few clicks.
Nah... we've been convinced of that since Blade Runner at the latest. Probably much earlier.
Mostly true, yet for some of us, a physical keyboard is more important than a third day of battery life or 720p video playback. The Sony-Ericsson SK17i (SK17a in North America) did a pretty good job of combining a real keyboard with a compact form factor. I hope someone improves upon that idea in the next year or two.
Looks like there's a free 8051-specific IDE that uses SDCC, though I haven't used it.
At least the Ubuntu release names tell me the order in which they are released. When people talk about Debian releases, and they often do so without mentioning the release number, I often have to search the web to figure out whether they're talking about something old, current, new, or very new.
All the accounts I've read indicate that this was a problem between two or three individuals, and that PyCon handled the complaint they received professionally, reasonably, and quickly. Why would it affect anyone's decision to attend a future PyCon?
I would downvote the question if I could, as it seems to be about as useful as a "first post" comment. I wonder if the submitter just wanted to see himself published on slashdot.