I didn't advocate against understanding your computer, I advocated against complaining about not understanding it if you're not competent to understand it. Don't ask that the capabilities be minimized so it is easier to understand. Nerds should succeed at understanding, others probably shouldn't bother. And if they really want something easier to understand, something that intentionally is less capable, they should seek that from a niche hobby OS and not the world's main server OS.

It's funny that all those complaints against DST only happen when it's turned off in autumn . . .

It might be funny, but it's not true

Are you mentally ill?

How so? There are still distributions that don't have systemd. There are also some distributions talking about forking so you have two choices.
It sounds like you're more angry at open source politics than systemd or Pulseaudio.

And rightfully so too. Linux never was a democracy, it's tyranny of the capable coders.

No I saw it. And in your reply you disagree with a choice Debian made which is entirely up to Debian and internal Debian politics, but you think it shouldn't be forked?

You can't have it both ways. Either you support systemd's inclusion, or you support the fork. Either way your comment has nothing to do with systemd and everything to do with your opinion on how Debian should do something. This is the very essence of politics, except that linux distributions are not a democracy.

Actually it makes a lot of sense when you think about it. Do you routinely code a new windowing system every time you write an application, or do you code with some toolkit or framework which provides you an easy way to display a window? Do you write a new sound card driver every time you want the computer to beep?

No. Programming is done with APIs, repetitive tasks are done with libraries, and critically tasks which are required to be done every time something happens should be managed by an application and not coded individually every time.

The init process itself is basic. A master process tracks children, a filename decides when to start a service, and a script then manages that start-up. So why is it that sshd which can be started with a single command requires a 200 line script to get going at boot time? Why is it that most of those lines are duplicated. From the point of view of a programmer, and an end user (who has on several occasions debugged problems which were the result of an init script not working properly), a 6 line upstart file, or a 10 line systemd file are far better for something that accomplishes the same thing.

The other problem is that the init scripts are effectively programs that manage the process itself, and they are often based on very manual tasks. I've lost count the number of times I've typed in "service xxxx start" got "service already running PID blah" as a response, and then typed "service xxxx stop" only to get a "Failed" message. Much of the task of the init system which is now manually programmed on a per application basis and maintained manually for each distribution really should be passed on to some helper application.

Sysvinit definitely has it's share of problems. People just put on rose coloured glasses in the wake of the politically charged systemd comments.

If changing the time by one hour gives you a heart attack then you were really a time bomb to begin with.

Ah, more "programming requires a special mind" bullshit. Back in the 80's, you couldn't throw a rock without hitting a kid under 12 who wrote computer programs as a hobby on their home micro. There were countless children's books on computer programming -- even one mentioned in this thread that changed the life of a young future Slashdotter. That's how difficult it is to learn to program.

Look, I get it. You only have one skill, and you know how easy it is for others to pick-up. That's scary. The only reason people think you're smart or interesting is that you know how to write computer programs. Why, if we brought programming to the masses, you wouldn't be special.

When you give non-programmers good tools, they do amazing things. (User jbolden has a cool story about that, which I'd love to hear more about.) You want to stifle that just to protect your ego?

Make it DST year round. Daylight in the evening is much better than the mornings. You're going to work in the morning anyhow, who cares how light it is? You get out of work and still have daylight left, awesome.

You could argue the same thing about universal phone or gas or electricity service. Even with internet access some customers cost more than others, but get charged the same.

The idea is that in exchange for being allowed to have a monopoly, forcing you to pay whatever the charge because they are the only game in town, they have to do certain unprofitable things like provide service to remote areas or free service to certain poor households.

Don't blame high prices on having to give out some freebies. They account for a tiny fraction of the service provider's costs. The reason you pay so much is lack of competition.

How many computers do the public libraries in these areas have, and how many people want to use them? I have no idea, but a relative works in a public library and the computers are always fully booked by job seekers and people trying to interact with the government. Time is strictly limited and they always complain that they can't get everything done.

Companies and apparently the government love to make people use the internet because it lowers their costs, but there are not enough public computers to go around.

What algorithm are you using? There may be a more efficient approach (er, as in fewer triangles, not less time).

That still doesn't answer my question about what you think is lacking in WebGL.

Firstly, small companies can easily lure talent if what they offer is interesting and their culture is appealing. I would much rather work a 100k job that is interesting in a good company than a 120k job that's boring in a faceless corporation with MBA culture. They'd have to offer maybe 150k and even then I won't be as motivated. Lots of geeks are motivated by interest more than by money.

Secondly, yes we need to make a difference between software architects and programmers.