olgeni

Too bad nobody noticed.

I'd skip the "Debian" part if possible.

Step 1: gems, npm, pip, etc. Step 2: "containers". Step 3: this.

A new drama every day.

Burnout driven programming.

Good - more diversity is needed in war criminals.

This stopped being fun after actually having to use Debian at work.

Not sure why it says "Linux/UNIX".

Straight from Black Mirror.

Sorry, but I'm really not going to explain intersectional cisgender privilege (or whatever) to the guy panhandling on the street.

Run away, parkour style.

Maybe put some effort in cross-platform software.

Sounds good - let's give this a spin :)

Looks like 17.3 from the package name. Today it might not be "way" behind, but it will be in a year or two. Or three.

I can see the point of having a "stable" kernel, but these freezes are mostly random. Back in its days, Squeeze shipped with R14A (not B). That's not stable, it's just a random cutoff. It means that whoever did the package did not even know what A and B used to mean in Erlang releases.

That's not something you can put in production.

OTP_VERSION lists minor releases, so that should be a "true" 17.3.

Arch has 18.0 - better indeed, but you need to keep an eye on GitHub to find out which is the actual latest version :|

Yes - in the beginning.

If you look here https://github.com/erlang/otp/releases you'll see that - even on Jessie - 17.1 is unfortunately way behind.

I'm actually developing on 18.0.2. At least 17.5.x would have been better.

The fact that erlang.org does not list minor releases at all probably doesn't help. One can go to erlang.org and think that 18.0 is the latest...

I recently had to develop an Erlang application targeting Debian "stable". It was humiliating at best. Countless hour were wasted trying to get around bugs in prehistoric packages, or building new (and working) packages from scratch.

Never again.

It is a very efficient process: you can basically guess the full content just by looking at the url.

Subtitles - we are doing something like that with Epson's BT-200 (also for audio description). Also, RNIB ran a trial in the UK with Games of Thrones :) [https://www.youtube.com/watch?v=P8jyRwZjn1M]

(disclaimer - I work on this stuff)

Of course it was. Let's do a couple of strikes too.

Sorry dudes, you cannot say you have a "code of conduct" unless you copy and paste from one of the two/three Big Names in the field and make a decent "voluntary" donation.

I searched for "white" and of course I found a few, as expected.

While I understand the need to pile on the subject to be counted as one of the enlightened, this kind of stuff stopped being interesting a long while ago.

Testing on Vagrant is quite useful when you are forced to deploy on Linux in the end.

I have VirtualBox + FreeBSD stable/10 but things can get weird when disk load is high (IIRC some processes can get stuck in biowr).

Owners of Mike Gancarz's original book might find the title kind of weird.

They should probably just add support for the extension pack on FreeBSD.

"Portals that mix accounts will be rejected"