Daniel Jalkut on Twitter: "I've been waiting 7 months for the @Wordpress team to commit a fix I submitted to the XMLRPC API. It's affected my opinion of the project and diminished the odds I will submit future patches:
Weather at time/location of posting — Clear with a temperature of 64.45°F and 63% humidity.
smokey
via
Micro.blog
@cleverdevil @danielpunkass I know it’s not a representative sample, but Daniel’s bug reads like every other WordPress bug I’ve been interested in :-( I once reported a dataloss bug (post truncation at a non-BMP character) that, yes, was a edge case at the time, and I certainly didn’t come with a patch, but…dataloss…; it at least finally got fixed several years later after emoji became popular. In a similar vein, from the other side, one of my big regrets is that we never were able to get an acceptable JavaScript security model to allow landing your do JavaScript support in Camino, Daniel. It was thrilling to see you come in out of the blue with it, and that patch continues to haunt me, a decade? later; I kept looking at that bug over the years and wish I had known who I would have needed to talk to or poke to get an answer as to how we’d accomplish the JS “password sandboxing” in Gecko :-(
Comments (2)
Weather at time/location of posting — Clear with a temperature of 64.45°F and 63% humidity.
@cleverdevil @danielpunkass I know it’s not a representative sample, but Daniel’s bug reads like every other WordPress bug I’ve been interested in :-( I once reported a dataloss bug (post truncation at a non-BMP character) that, yes, was a edge case at the time, and I certainly didn’t come with a patch, but…dataloss…; it at least finally got fixed several years later after emoji became popular.
In a similar vein, from the other side, one of my big regrets is that we never were able to get an acceptable JavaScript security model to allow landing your do JavaScript support in Camino, Daniel. It was thrilling to see you come in out of the blue with it, and that patch continues to haunt me, a decade? later; I kept looking at that bug over the years and wish I had known who I would have needed to talk to or poke to get an answer as to how we’d accomplish the JS “password sandboxing” in Gecko :-(