11–20 of 62 posts
The tone and attitude of this post is basically the epitome of Jr/beginner dev. If your audience is non-programmers and one wants to be the “big shot”, ply this tact, but tech readers will overwhelmingly find this attitude cringeworthy.
It got so bad that we mostly ignored them. It wasn't good for either VLC or QuickTime.
This seems like a needlessly aggressive and poor take. Its a cool bug that they discovered; but going into "Apple's audio engineering team is, at least on some level, incompetent (or incompetently run; I'm not blaming the employees here, but rather the organization)" is just unproductively mean. "and obvious in a sine sweep frequency response test, which is the most basic test you can run end-to-end on a completed au…
This makes me cringe. I consider myself an experienced software engineer, but I don't think I'll ever criticize other's code like that.
At Apple we would see this tone all the time from people on the VLC project. It got so bad that the senior people would refer to them as DCS, Drunken College Student. It got so bad that we mostly ignored them. It wasn't good for either VLC or QuickTime.
This seems like a needlessly aggressive and poor take. Its a cool bug that they discovered; but going into "Apple's audio engineering team is, at least on some level, incompetent (or incompetently run; I'm not blaming the employees here, but rather the organization)" is just unproductively mean. "and obvious in a sine sweep frequency response test, which is the most basic test you can run end-to-end on a completed au…
It's a dev enjoying some hyperbole for something cool they fixed on a chat platform.
> They have a stupid off-by-one bug in the middle of their bass enhancer AND NOBODY NOTICED NOR FIXED IT IN OVER A YEAR. The mocking tone of this post is really not necessary. An engineer made probably one of the most common coding errors that nobody noticed because real world impact is minor to non existent. The devs should be trying to build a relationship with Apple, not mocking then each time they find a minor bu…
These devs didn't even notice it until they tried to rip into the inner workings.
I mean, considering the source isn't open. Yeah, you need to do that.
This seems like a needlessly aggressive and poor take. Its a cool bug that they discovered; but going into "Apple's audio engineering team is, at least on some level, incompetent (or incompetently run; I'm not blaming the employees here, but rather the organization)" is just unproductively mean. "and obvious in a sine sweep frequency response test, which is the most basic test you can run end-to-end on a completed au…
It's not an official Asahi communication. It's a dev enjoying some hyperbole for something cool they fixed on a chat platform.
This seems like a needlessly aggressive and poor take. Its a cool bug that they discovered; but going into "Apple's audio engineering team is, at least on some level, incompetent (or incompetently run; I'm not blaming the employees here, but rather the organization)" is just unproductively mean. "and obvious in a sine sweep frequency response test, which is the most basic test you can run end-to-end on a completed au…
It's not an official Asahi communication. It's a dev enjoying some hyperbole for something cool they fixed on a chat platform.
This seems like a needlessly aggressive and poor take. Its a cool bug that they discovered; but going into "Apple's audio engineering team is, at least on some level, incompetent (or incompetently run; I'm not blaming the employees here, but rather the organization)" is just unproductively mean. "and obvious in a sine sweep frequency response test, which is the most basic test you can run end-to-end on a completed au…
It's not an official Asahi communication. It's a dev enjoying some hyperbole for something cool they fixed on a chat platform.