FSMaxB @FSMaxB@mastodon.cloud

@rjraymond @TheFreePenguin @kev Two objections:
1. There's a difference between "not quite perfect" and "totally off the mark"
2. Nobody is perfect, but some people acknowledge that fact and strive for perfection. Some people acknowledge their mistakes and apologize if they have done something wrong, but other people just announce their return without acknowledging anything and without further comment.

@can @TheFreePenguin @kev And even if there were a way all of his posts could be explained away as purely a failure to express himself diplomatically (which I don't think there is), he still utterly failed to acknowledge that what he said wasn't "ideal", nor did he apologize. There seems to be no understanding of what he did wrong, nor any remorse or pledge of positive change.

@can @TheFreePenguin @kev And even without that post, there have been many more like it that show a total disregard for other human beings. Not just with disabilities in particular, but mostly people of the opposite sex to his.

@can @TheFreePenguin @kev No, literally what he said was:
"If you'd like to love and care for a pet that doesn't have normal human mental capacity, don't create a handicapped human being to be your pet. Get a dog or a parrot. It will appreciate your love, and it will never feel bad for being less capable than normal humans."

At the very least you can fault him for thinking of them as "less capable than normal humans", no room for interpretation there. The pet comparison being very much implied.

@TheFreePenguin @kev Source: https://web.archive.org/web/20161107050933/https://www.stallman.org/archives/2016-jul-oct.html#31_October_2016_(Down's_syndrome)

(context: http://ebb.org/bkuhn/blog/2019/10/15/fsf-rms.html)

@owl IEEE-754 is mentioned in RFC 8259 (https://tools.ietf.org/html/rfc8259#section-6)

@owl it does recommend IEEE-754 double precision floating point numbers for good compatibility with other implementations, but things like NaN or infinity are explicitly not supported.

@owl JSON is not simple. You will know that if you have ever tried parsing or printing floating point numbers.

Also it's completely underspecified. A parser that only ever parses empty strings, empty Arrays, empty objects, null and every number as 0 is still in compliance with the RFC (although it is not following it's recommendations ...)

@chimerror @owl actually ASCII has only 128 characters, one of which can't really be used if you're passing the string around C programs that work with explicit string lengths ...

@owl My girlfriend uses it to mean "Lazily lying on the bed on your back with the head hanging over the edge". Essentially "lazing around". 😂

@owl (x86_64 that is ...)

@owl You can build one from second hands parts for pretty affordable prices!

@dilletanteo Do you know the trailer song? So catchy! https://www.youtube.com/watch?v=QhzDi6gSWdA
But yeah, many of the Ghibli movies are great (although this one technically isn't made by them). My favorites are "Hotaru no Haka" and "Mononoke Hime".

@owl On one of my projects I switched to jemalloc using the jemallocator crate and tuned it to always use MADV_FREE instead of keeping the pages around.

Before this switch, glibc malloc kept 3-4 times as much memory around than was actually used and my application was constantly killed by the OOM killer.

It's absolutely crazy how much allocators can be configured and how much of a difference it can make.

Any default configuration for an allocator must be a heck of a compromise.

🤔 Maybe I'm looking for Ruby, now that I think about it.