That's a pretty extreme take. I've been using the Mac since about 2001. I like Tahoe and a well designed Tahoe app can look really nice on the platform. There are bugs, inconsistencies and other issues, but it doesn't feel that different than many previous macOS / OS X releases
I believe you can do regular hard edged intersections. You can see in his operator list some are listed as “smoothSubtract” and some are just “subtract”
It’s just easy to do the melding thing with SDFs so a lot of people do it
The reason this happens is because big companies get their software pen tested. Part of the pen test report will include something like “accessible from jailbroken devices.”
The pen test results get put into the ticket system as immovable entries. Engineers will question them, only to be shot down by the cyber security department who organized the pen test. The engineers will eventually accept that they cannot convince cyber to drop the issue, and implement the jail break detection.
Why does cyber mandate it? Because no one in a large company wants to accept the risk, even imaginary risk. They want to be able to say, when security is breached, “we did our due diligence. Look at the report, we implemented everything in it”
Why do firms offering penetration testing keep putting junk like this into their reports? Because their automated tools list them out and they’re getting paid to find issues. The more the better.
Depends what you see as “abusing” the system. By working from home, I can take a walk in the garden when I find it hard to think, it energises me. At my office I can (and do) take a walk in the car park, but inevitably I leave the office with a headache caused by constant noise and fluorescent lighting
At home, I can put my family first if needed. When I’m at the office and something comes up at the kids’ school that I need to deal with, it’s a mad dash to get away soon enough that I almost have to drop everything and run
The times working in the office has been good as a software engineer: when we are prototyping on physical hardware I do not have at home. That’s it
It’s great if people love to go to the office. That’s fine. It’s managers that enforce it who are the problem — the people who work for you aren’t children and if you feel like you can’t trust them to make the decision to work from home, why on earth would you trust them in your office?
You seriously think this clown cares about any of this? I don’t know a single person living comfortable life who woud speak like that, only some miserable sod living in a shoebox who hates everyone around them.
My son regularly borrows my iPhone 14 Pro for shooting video, and I inevitably have to do a large AirDrop transfer to him of all his footage. We usually see about 10 GB per minute, which is really fast
We have some sort of hybrid policy. Every single time I have showed up at the office, I either end up socialising far too much and get nothing done (I find it extremely hard to work next to people without talking to them).
Or nobody is there and I end up having driven (40 minutes each way) to the office to have Teams meetings with a wonderful view of the car park, under fluorescent lights, using a cheap low-resolution office monitor. When I could have been having those Teams meetings with a view of my garden and a much nicer monitor I have invested in
"Are you ready for that quarterly meeting? Heard Tracy will connect from the conference in Toledo. Hopefully I don't get a crappy seat in the conference room."
"I'll take the meeting from the desk."
"Nice. Lunch later?"
"Yeah. Talk then."
Wow. Another day of building relationships and sharing knowledge.
Sure. I catch up with many of them on weekends anyway — we hike together, our families know each other, some live nearby etc.
Regarding knowledge sharing, that happens equally well via Slack. (Actually, I'd say a screen share works better than over-the-shouldering someone else's screen in person)
I've been hoping for Apple to return to "thin" and it's nice that they're trying. I don't know whether I would buy this, but my current iPhone 14 Pro feels like a brick — thick stainless steel
When I go for a run, it's uncomfortable to have in a pocket depending on what running clothes I am wearing. The heaviness makes it feel far more likely to break all the times I have dropped it (and I have dropped it many times, without a case)
Safe area can account for things that are not just a notch. It's used across Apple platforms to indicate anything that might need to occupy a dedicated region on the screen: notch on iPhones, home indicator, iPadOS traffic light buttons, menu bar, curved edges of displays, and so on
Your container views can extend the safe areas for their children as well. In our apps, which allow users to run their own custom projects, we increase the safe area for our UI so that users can avoid it in their own rendering
Safe area is a fairly neat and functional API. The unfortunate thing is the older `CGDisplayCopyAllDisplayModes` API is just lumping all resolutions together
That's obvious: the descriptive term is obvious in what it represents on your screen, so has a low cognitive overload for all the new generations of people learning these APIs.
Encoding bad practices for decades, on the other hand, just reflects the pains of the old generations.
I've been diving into Claude Code after reading articles constantly praising its abilities. But I think perhaps it's better suited to web development
Using it for iOS development is interesting. It does produce working output (sometimes!) but it's very hit-or-miss. Recently I gave it a couple hours to build a CarPlay prototype of one of my apps. It was completely unable to refactor the codebase to correctly support CarPlay (even though I passed the entire CarPlay documentation into it). I gave it three attempts at it. Then I intervened and added support for CarPlay manually, following that I added a lot of skeleton code for it to flesh out. Claude was then able to build a prototype
However, over the next few days as I tried to maintain the code I ended up rewriting 60% of it because it was not maintainable or correct. (By "not correct" I mean it had logic errors and was updating the display multiple times with incorrect information before replacing it with correct information, causing the data displayed to randomly refresh)
I also tried getting it to add some new screens to a game I develop. I wanted it to add some of the purchase flows into the app (boring code that I hate writing). It managed to do it with compile errors, and was unable to fix its own build output despite having the tools to do so. Instead of fixing the build errors it caused, Claude Code decided it would manually verify that only its own changes were correct by running `swiftc` on only files that it touched. Which was nonsense
All that said, there was a benefit in that Claude Code writing all this code and getting something up on the screen motivated me to finally pick up the work and do some of these tasks. I had been putting them off for months and just having the work "get started" no matter how bad, was a good kick start
reply