Isn't the main problem that while systemd might solve problem, it's sharply going away from the simple solution that worked to make Unix good?

Systemd isn't simple. If it's not simple, I don't think I want it on my Linux.

PA and Gnome isn't simple either. And creating more problems (albeit while solving others). I believe the same thing will be true about systemd.

It seems weird that you can't upgrade if you delay. Really weird.

Does that mean that when they finally made a car with comfortable seats, it sold out? :)

(My main problem with buying an S is that the seats actively hurt my back. Maybe because I'm 6'4. I don't know.)

Also, does Tesla need systems developers? :)

The UK government really don't like it's people.

Pity Scotland didn't manage to leave.

Turn it around instead. Let the people see all official documents and plans.

Isn't it very likely that something very basic like the pythagorean theorem was discovered more then once? Probably several times in the region we now call India.

We know of the greeks because we got to copy their stuff before it was burned, but we burned thousands of equal amount of historical accounts, philosophy and science from other sources. We've had long-lasting cultures who mainly destroyed other cultures and all their records.

We were just lucky the romans thought that the greeks were cool. If that hadn't been the case, all that would have been destroyed as well.

You can't go from to 5.0.1? (Not that 5.0.1 is worth it, but...)

Since Lollipop has a lot of bugs and nothing of the new features is any better than the old ones (lockscreen, face recognition, calendar... I hated all new changes), why would you upgrade?

5.1 might be worth it.

It shouldn't be impossible to go fully functional using only C++. Is it a challenge? :)

This is true. But I don't think you can be a good programmer if you only know one single language in one single paradigm.

I usually program in a mix of functional, object-oriented and iterative; whichever solves just this problem the best at the moment. (Bonus if it also creates the most readable code. Which is, of course, part of 'best'.) I don't think I could do that as well if I hadn't programmed in both assembler, lisp, C, C++ and LPC.

(I'm not sure what ARM C++ is; I write C for ARM but except the hardware registers that I hide away in hardware layers, there's nothing special over the C. Well, it doesn't have things like printf, signal or exit. But it really isn't a different programming language than say C for DOS.)

I wrote a C compiler in interlisp once. That was fun. (To lisp.) (As a project.) (After learning LISP for about three weeks. It could probably have been much better LISP, but the principles in LISP and functional programming are actually really easy to understand. Easier than being able to read all the parenthesis...)

Writing such projects - as well as doing things like implementing a scheduler or a TCP/IP stack - makes you understand things a little bit better. :)

Yes. I constantly have problems with libraries, especially overcoming bugs and limitations. Most of the time I have to (sadly) reinvent the wheel, because it didn't have spokes or someone thought triangular wheels were the best thing ever.

This is brought up now and then on Slashdot. Treating programming languages like something actually hard to learn.

Specific programming languages are irrelevant.

Programming paradigms and levels are relevant. But if you know a language in one paradigm, it's easy to learn another one. If you know C, the step to Python is fairly close. Lisp or Erlang is a little more distant, but it's not impossible far to learn in a few weeks.

If you can't pick up the basics of any computer language in a few weeks, I get the impression you're not really sure of what you're doing.

So it's irrelevant if you already know the language. Except for very confused recruiters. The question is, can you get good at the skills needed at the job within a few weeks? You wont know the projects or the libraries in the new company anyway, picking up a new computing language isn't going to be the hard part.

But then again, ASN.1 isn't a programming language more then TCP/IP is a programming language, so maybe the question is more confused than that.

(Languages I have encountered in my professional career: V2 BASIC, 6510 assembler, ABC8* BASIC, dBase 4, x86 assembler, 680x0 assembler, Batch files, Pascal, C, C++, Shellscripts, Pike, ECMAscript, Java, Flash, ARM assembler, and Python. In that order. I have done ASN.1 in the form of SNMP, but I really don't think I would call it a programming language.)

What is the problem with licensing everything for global use? Can someone explain?

I thought the population growth right now was in India, where they speak a lot of English. Of a sort.

And there's no way a closed-wall country like China could have their language exported to the world, no matter how many they are. Especially since the trade language, in China, is English. (Of another sort.)

But here's to hope that the regional languages lives on, because some sort of crippled international English with a vocabulary of 400 words should not be your primary language.

Two restaurants I really liked in Berlin, I talked to the owners about TripAdvisor:
Neither was listed. I wanted to add them and tell others about how nice they were.

They asked that I didn't put them (back) on TripAdvisor. Apparently people use sites like that to blackmail restaurants into service.

That's why we can't have anything nice.

Either TripAdvisor owns up and starts cleaning up false reviews, or it will get completely useless.

Maybe the "star" rating system needs to go, and only allow reviews. Rate restaurants on how well-written the reviews are, and people can read for themselves. It should make it a lot more work to actually sink a restaurant.

If they show it, and then something happens at one theatre, they will still get sued for millions.

I bet they would show it if there wasn't a huge culture of suing everything out of everything.