half-broken

There are so many layers of bad, half-broken stuff to deal with, encapsulated in new, half-broken stuff.

For me, the problem with emacs is that (1) it's slow and (2) so many features are half-broken.

Porn sites are janky, unpolished, often half-broken, and prone to suddenly disappearing as quickly as they appeared.

Very, especially when you realize how much of the arcane half-broken functionality is purely due to specific regulation thresholds.

So that's basically allowing operations on a half-broken object, just so that you can test it without creating all the dependencies?...

As someone who spent 18 months of his life deploying Openstack at scale, I'm confident in pointing out that devstack is, like most of Openstack, half-broken.

Also, they are able to mask problems for quite some time, and when they finally implode you have a half-broken sector on your hands with cascading effects and unemployment and defaults and...

Ah, I should've thought twice about that - I'm not even attempting reproducible builds in my own work, but I've often seen my Dockerfiles have apt-get-induced shenanigans due to the particular day or half-broken mirror I happen to be running the build from.

I continue to hope that at some point the pendulum will swing back the other way, probably when we reach a point where significant markets are so fed up with short-lived, poorly supported, half-broken junkware that they understand the benefits of paying for something better.

Microsoft seems to have largely given up even monitoring the app store; half the top/new games on the lists for the last several months have been blatantly pirated material, either blatant copies of whatever iOS/Android fad is running at the moment, or actual emulator ROMs of old console games running in a buggy, half-broken wrapper.

The worst I have seen was a team of several hundred people who, on $200 half-broken laptops, were running - in parallel - 500MB Excel files for hours every day, which basically did a few linear operations on about 30 variables, before joining the results in a superfile itself taking up to 20 minutes just to open on a gaming-specced desktop.

>The worst I have seen was a team of several hundred people who, on $200 half-broken laptops, were running - in parallel - 500MB Excel files for hours every day, which basically did a few linear operations on about 30 variables, before joining the results in a superfile itself taking up to 20 minutes just to open on a gaming-specced desktop.