> FYI: Not sure if the author will see this but some spelling mistakes in the article. [0] E.g. s/reslease/release/

Thanks, I saw it :)

I know you're trolling, but FYI the `static` before function has nothing to do with the `static` return type. Like other programming languages the term `static` is used to denote two things.

And other programming languages get away wihout overloading the term.

It's not an excuse for slacking on language design.

"static" itself is originally an overloaded term, and still remains such to this day in C++.

The term is overloaded, which is a bit unfortunate.

However, the unfortunateness is static.

WP recently said they'll support 5.6 for an unknown amount of time. So not soon

Still no support for my audio interface over USB… You can add it, but no signal comes true. I know about virtual audio routing, but I'm so sad this bug hasn't been fixed after years…

Your device must support one of the common audio protocols to work in OBS (for Windows WASAPI for example). There's also an ASIO plugin available.

OBS will probably not add any specific code to support non-conforming device(s) without an external maintainer willing to keep the needed code updated over the years.

> solely on the The Pulfrich effect

Did you read the whole post? There's

- The Pulfrich effect

- The way human eyes are built

- The case of astigmatism

- Studies targeted towards computer screen use

I have enough of astigmatism to have it corrected in my glasses and yet the colour scheme I found the most comfortable over the years is Zenburn. Though I do prefer the high contrast version with darker background.

The only time I managed to use a light theme for an extended period of time was a couple of years in a room with weird lighting and reflective screen of an imac. That's when I was using Solarised Light, because my Zenburn just couldn't provide enough contrast.

Then I moved to a different room and it was back to Zenburn.

> 'What am I becoming?' rather than 'What am I getting?'

That's a great insight. Thanks for sharing!

Hope you're in a better place now!

Is it really a question of whose responsibility it is though? If you're feeling stuck, it's your right to find ways getting unstuck. If that means changing jobs, who can blame you?

Unless you're a manager at your company it's not your responsibility to fix it.

No, it's not a question of whose responsibility it is—it's always leadership's responsibility. However, I have a tendency to think myself really smart and capable. Y'know——overconfident. And because of that, I try to offset it by refusing to believe it's anyone else's fault but mine. Like I mentioned, it helps keep me honest WITH MYSELF. Otherwise, I feel like I wouldn't have enough commitment to tackle hard tasks, I'd just chalk failure up to someone else, which is worse IMO.

Anyway, my habit of keeping myself honest sometimes backfires and when it does it manifests as running my head into a brick wall over and over until I'm REALLY sure that I can't fix it. But... I think I'm about there in this instance. Other devs are noticing the same thing I'm noticing, so I feel like I've got good evidence that it's a fundamental leadership issue here.

There definitely are stages before being stuck. I worked for three and a half years in that company, and only felt stuck for the last year.

I went to all three stages you describe, feels very familiar.

I feel like company's like that are shooting themselves in the foot: the delivered product is of lesser quality, developers aren't happy and quit sooner or later.

Looking at it from a manager's perspective, I think you'd want to do everything in your power to prevent such situations. Feels like there's a general lack of future perspective in many companies.

The only benchmarks done before adding it to the core were on maths-heavy code samples, something PHP is seldom used for.

You can read about it here: https://stitcher.io/blog/php-jit