I should try to get a #FuckingXcode tag going. Because fucking #Xcode.

Run a test suite, all the tests get green checkmarks next to them. Then write a test that fails. To debug the test, run just that one test. All checkmarks remain while you run that one test, despite others not running. If you break another test, it looks like it still passes. If you use cmd-opt-ctrl-g to rerun the last test set run, it LOOKS like they all pass, but they don't. Xcode keeps stale pass icons instead of removing or greying them out. If don't remember you're not running the entire suite… ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

Fucking Xcode.

@shadowfacts #fuckingXcode just does that anyway. During my SwiftUI adventure last week, I was routinely typing a line ahead, drink my coffee, wait for it to finish, often wrong, then go fix it. Extra fun is the compiler can stop the mouse from moving. The mouse is a low-level, real-time interrupt. HOW?!

I've literally spent the last 15 minutes just staring at my screen and seething at #fuckingXcode

I'd like to redo my little project in a sane language & environment, but:
A) Objective-C: Also uses Xcode, tho I could just set it up, quit, and call xcodebuild from shell. Meh.
B) JS: Fuck. Yeah, it'd work, but it's so fiddly I prefer to get paid for that.
C) Scheme: No GUI. I could build it in SDL, but kinda the point was to use stock GUI.
D) Python + Tkinter? Bleh, slow, but maybe.

I spoke too soon. #fuckingXcode reported an error 10-20 lines after where it actually was, then while trying to find it ate all memory, crashed Safari & other apps but not itself. Had to reboot completely.

Giving up on this #swift bullshit again for a while.

I've seen Eclipse behave this badly, never any other dev tool in 40 years of programming. Just the shittiest thing anyone's ever shipped.

Awesome. A one-line error took #fuckingXcode 192 seconds to build & find, then #swift syntax "service" (much like a bull services a cow) kept eating all CPU and even slowed the mouse down!, and a couple minutes later crashed me back to login.

Really they've improved Xcode so much, it used to glitch the screen then force reboot.

Mostly, my Swift project builds in 15-30s, which is stupidly long when an equivalent Objective-C program compiled so fast I couldn't time it, but say 150ms, 100x faster.

But I just added one line setting a background color, and it's now 4 minutes into build, 4 CPU cores pegged at 100%. I don't think it's gonna succeed, but I'm curious to see what happens.
#fuckingXcode

In case you need to do this nonsense:
https://paste.debian.net/1206857/
#fuckingXcode
debian Pastezone

Grr. Argh.
#fuckingXcode

Trying to update #fuckingXcode before a reboot, and it's just stuck at 75% in updater.

UUUUGH. Apple's dev tools experience really doesn't get the love the rest of the system does.

@joerebelloharley Well, England's like 20 years in the past in fashion, but even so flannel's been dead longer than that, beanies not around since the '50s.

A Mac's the last of the UNIX® workstations. For developers, it is to toys like Linux what they are to non-OS like Windows. The touchbar experiment's happily dead, the bad keyboards are dead.

But this new OS version has so many bad design problems in Finder, etc. I'm going crazy.

I just want my stable Mach+BSD to run #fuckingxcode in.