eevee

What most fascinates me about this whole kerfuffle is your adamant refusal to take responsibility for anything. All I've seen from you is continued insistence that nothing is your fault, accompanied by pages of nigh incomprehensible "evidence" that doesn't seem relevant to anything that's actually happened.

The facts of note seem to be: (1) you are, for whatever reason, in charge of freenode; (2) the very first moment you attempted to make use of that position, you destroyed freenode.

That is a *catastrophic* management failure on your part, and the fact that I haven't seen so much as a "my bad" from you is appalling beyond words. Despite how much you claim to care about freenode, you are clearly more concerned with your own image.

Okay. Now malware addons are signed, and nothing has been accomplished.

This "bizarre policy" was software signing, which is in fact a security feature.

I don't understand what "getting their act together" means here, when you're posting it on an announcement that the problem has already been fixed. Should Firefox proactively remove all security features that risk ever posing some modicum of inconvenience to users? Because that would be... all of them.

but hey, that's what CWs are for

It's bad that the runtime is fragmented. Google will fix it by creating a new runtime

"Once the commercial world catches up to python 3..."

fwiw, lack of PyPy support is one of the most common reasons I hear for people being leery of Python 3. Of course the people using PyPy aren't the people excited to move to Python 3, if they're effectively mutually exclusive.

What do you do when a value passes between major versions which have different implementations of its type? What do you do with the `int` type, which was actually two separate types in Python 2? What do you do when the binary representation of strings changes (as it did in the 3 series) and you want to pass that into Python 2 land? What do you do about extension modules written in C, which many popular Python libraries use to speed up hot code? Do you include copies of both standard libraries, meaning you now have duplicate modules and may get one or the other depending on the tag in your file? Which version of Python 2 do you target? What happens when there's a bug in one Python 2 implementation but not the other? How do you handle having two C APIs at the same time?

You mention C++ as though it worked out great, but C++ is still full of sharp edges and features that interact weirdly with its C legacy, and it has never completely replaced C (especially for libraries). And that's despite having a few advantages that made it possible in the first place, like having a completely different stdlib built on top of the C stdlib, and producing machine code rather than compiling for a VM on the fly.

The default text size in every browser, as far as I'm aware, is actually 16px. The text on Hacker News is 12px, because virtually every designer decides they know better than the browser settings.

Which one are you thinking of as the "default"?

Overall, I don't think Doom 2 is actually much more abstract than Doom 1. I suspect the real difference is that all of Romero's levels were clumped together in the shareware episode of Doom 1, which is what everyone remembers. Sandy Petersen (who does the really abstract weird stuff) did episodes 2 and 3, but his Doom 2 levels were strewn throughout the game, even in the Earth-like sections that you'd expect to be more realistic.

"Yes, hello, Nintendo? Let's talk business. I'm a starving artist and I want to sell some Pikachu buttons."

Why not? It's your work. You can't really be competing with Nintendo, because they can't create that same picture, because they don't employ you. Also you are extremely unlikely to be making a material impact on the bottom line of a multi-billion-dollar international media company.

Also, this is a thing many people already do, so I'm really advocating that it's fine for them to continue doing it.

You seem to be assuming that derivative work doesn't require hard work of its own. I tried to make the point that this game is itself a derivative of other things, without which it couldn't exist.

Even if you did do that: why would anyone buy it in lieu of the original?

Undertale doesn't have achievements, leaderboards, modding, or multiplayer. I think it has cloud save, but it's like a 6-hour game so that's not a particularly alluring feature here.

I'm not talking about putting someone else's art on buttons. I'm talking about artists putting their own art on buttons.

I hope you can imagine why I might not want to reinstall the OS and have to redeploy half a dozen other things, just so this particular one gets easier.

You lost me right around the point where you compared x86 vs x86_64 to a toaster and a teapot.

Nothing about Ruby forum software necessitates a 64-bit kernel. (Which I have, incidentally.) According to Docker, nothing about Docker necessitates a 64-bit kernel either! It's an entirely arbitrary requirement, inherited by the forum software for support reasons rather than technical reasons, and for some reason you are blaming me for not meeting it.

I certainly believe that people manage the 30 minute installation. I would've been much happier if I managed it as well.

And Web deployments must suck, or we wouldn't need Docker. Right? I mean, the whole appeal is that we can take all this arduous ad-hoc crap and just shove it in a box. Unfortunately, it's still arduous ad-hoc crap; we just don't have to look at it as often now.

Last time I complained about this, a few people said exactly the same thing, but naming a different product.

It also warns you if you try to use gmail to send mail, because gmail throttles you to only sending 2000 emails per 24 hours.

I observe that they'll happily charge you $99 to install it on your machine for you.

Actually I suggest writing less code, assuming that Docker is a whole lot of code and "what if we write down dependencies" is more interface than code.

The operative word is needs, since Docker is the only supported way to install this particular software. Which is, I cannot stress enough, a forum.

Sorry, I forgot to painstakingly document the innumerable hours I spent reading documentation (or trying to find critical documentation that didn't exist). I didn't think that would be a compelling read.

Yes, my OS is slightly "weird" for reasons I did not choose. Funny story: while I was trying to figure out what the hell RVM was doing, I mostly ran across people running OS X who had the same setup: 32-bit OS on a 64-bit chip. (And for what it's worth, Python native extensions build for the architecture of the Python executable — you know, the thing that has to load them — rather than the architecture of the machine.)

I never complained that it didn't work with an old database. Ubuntu's versioning was just a fun surprise. I don't see why it wouldn't work with Postgres 9.1; I just figured I'd do the upgrade while I already had my foot in the door.

Maybe if installing Rails apps is still a huge headache after the fourth or fifth time I've done it, something is wrong with Rails. Maybe.

I have a fairly mundane server running the latest Ubuntu LTS with all stock vendor packages. If your app is such brittle crap that this is the "server from hell", well, it's no wonder everyone is using Docker.

This has never caused any problems before. I'd actually completely forgotten about it until RVM or Ruby or RubyGems (I haven't decided yet who to blame) choked.

And it wasn't my choice — I started out 32-bit to save RAM on what used to be a fairly dinky plan. Some years later, Linode said I oughta switch to a 64-bit kernel for some obscure reason I can't remember.

The new coroutine stuff is really just syntactic sugar for "yield from", which has been around for a few versions now (and in turn is little more than syntactic sugar for "yield"ing repeatedly).

But you don't return more than once from a coroutine. You can suspend it as often as you like, and that's what "await" does.

The GitHub repo suggests there's been Python 3 support for a while: https://github.com/filmackay/blpapi-py

I've run into my fair share of Python 3 roadblocks, but you'd be surprised how far you can get by making a little noise and sending the occasional patch. Library authors are much more willing to prioritize Python 3 support if it looks like people actually need it :)

fwiw:

    >>> codecs.encode(b'Python', 'base64')
    b'UHl0aG9u\n'

The encodings still exist; hex works too (or hex_codec in older Python 3s). Python 3 just restricted the encode/decode methods to always go str to bytes or bytes to str.

OP here. You say this all, and yet, if I google for "unicode strip accents"...

Top-voted answer uses NFD, one below it uses NFKD: http://stackoverflow.com/questions/517923/what-is-the-best-w...

NFKD: http://www.perlmonks.org/?node_id=835238

NFD: http://www.perlmonks.org/?node_id=1105025

NFD: http://www.perlmonks.org/?node_id=485681

NFD: http://drillio.com/en/software/java/remove-accent-diacritic/

NFKD: https://gist.github.com/j4mie/557354

Two and a half of the first six results blindly apply NFKD to arbitrary text. All of them use normalization.

Sad state of affairs.

I have no idea why you keep going on about various other countries' naming laws, when the passage in question wasn't even talking about enforcement at all:

> Facebook likes to think of names as a one-to-one mapping. You have one name, and that name is how people refer to you at all times. It’s a very WASP notion of how names work, and the reality is far more complex.

Facebook, as an American company, inherited its ideas about names from mainstream American (i.e., WASP) culture. This was a poor choice, because those ideas do not also cover how some other cultures treat names. That's all this is saying. Your interpretation of this as "inflammatory" and "mischaracterizing history" is frankly baffling.

Forget what the article says, about some people not even being allowed to use their own names — what's really important here is that we not write anything that remotely sounds like blaming white people.