Many of the same advantages hold for any other language's frameworks, with the added benefit of using any other language.

Perl is valid if you know it and want to use it. Otherwise, not really.

There is a port of mechanize to Python as well, if that is your main reason to use Perl.

Whatever you can do in "disgusting hacks" can be done just as quickly in a way which won't make you want to vomit when you look over the code again later.

I would really like to hear from more people who use Circus in production. It seems interesting.

Tried it and I can tell you it's not production ready. It would randomly go rogue on our production servers and would start falsely detecting a worker crash and start launching more.

It took us a long time to trace it down and we quickly switched to runit and supervisor on a few servers. All of our problems went away.

Circus author here.

I am interested in any form of feedback on the issues you had. Falsely detecting a work crash sounds very weird and unprobable because Circus uses the system PID list to check on processes - so I wonder what happens in your case.

I have never had the slightest indication that anyone actually looked at my Github account listed at the top of the resume, let alone that this ever helped me get any job I've had. So I'm inclined to treat this as an urban legend.

Happens all the time, e.g. with postings for positions that are really intended to be filled internally, or with perpetual postings which do nothing but solicit people to go into a resume pool when there is no specific job.

It wouldn't be funny because it's not even surprising for job searchers to be jerked around, just normal

So much the worse for using Android. It's past time that we have proper Linux on phones without interposing all the Google-Java stuff.

I believe this was referring to the Android kernel patches, not the Java-based userland.

Java, or rather Dalvik, has absolutely nothing to do with the kernel or graphics stack in Android.

They have openly discussed their intention to build an X-compatible layer on top of Wayland for remote windows for years, it is really sad that FUD has prevailed about how they want to take our remote windows away.

XWayland exists, but it's not the issue. We want to run native Wayland apps remotely.

Maybe you do, but then, maybe you have no idea what you're asking for and why it makes no sense.

A Linux monoculture is never going to happen. But what would actually be wrong with it?

As I said, it means that code would be written to Linux specifically. What works on linux, what is fast on linux, etc., would be what people write to.

So if someone invented a new kernel that is better than linux, it would have two problems: The usual problem of getting adoption and interest in a new project, but also the problem of all existing code being designed with linux in mind.

Whereas today, people generally try to write code that runs well not just on linux but also on other kernels. Not because they have lofty ideals necessarily, but because there are other kernels.

If we had only linux, that wouldn't be the case.

This is the basic question of standards. Open source is great - as I said above, I have been a huge supporter for a very long time - but standards are an orthogonal issue to open source, and just as important. Writing to standards instead of the bugs/idiosyncrasies of a single implementation is the only thing that makes it easy for new implementations to show up. And standards are dead when there is a single implementation.

A Minix monoculture never happened. But what would actually have been wrong with it?

Think of all of Tanenbaum's design decisions that Linus ended up changing. One big reason we know, in detail, what would have been wrong with a Minix monoculture is that it never happened.

Assuming that Minix adopted a reasonable license and fixed outstanding issues that make Linux currently better, I'm asking you to tell me what's wrong with that. We have a de facto monoculture of Windows on the PC right now and I don't think that's better.

I didn't say what sort of Minix monoculture we might have wound up with. In particular, who says the licensing would have been fixed? Without Linux's success how many people would have thought there was a problem?

I think success is mentioned because of all the people who have begun to enter the industry just to cash in somehow.

They didn't get rich programming, not at all. They got rich owning successful companies. The fact that they did some of the programming for some MVP or other is almost incidental. They were not getting paid huge salaries for cranking out code and they certainly weren't the only ones involved. If you can pay someone to do the same kind of work on an MVP and then you win the same kind of lottery, it is not necessary for you to have any direct programming input.