111–120 of 139 posts
Earlier quoted context omitted.
thats a shame if true, they really should be dog-fooding that horrible agent ui in xcode to bring it up to a usable state
The UI got a massive overhaul in the new Xcode beta. It’s no longer confined to the sidebar.
Earlier quoted context omitted.
A lot of devs are tricked into using it because it’s official
I love how it doesn't even support reasoning output or edit tool diffs. (Yes it can show diffs sometimes when using the 100% official flow but not when using ACP)
Earlier quoted context omitted.
I love how it doesn't even support reasoning output or edit tool diffs. (Yes it can show diffs sometimes when using the 100% official flow but not when using ACP)
It also doesn't support Computer Use or Browser Use among other deficiencies
If you want to help improve the security of OS software through the magic of memory safe languages, the team that did this work is hiring: https://jobs.apple.com/en-us/search?search=Spear&sort=releva... Knowledge of Swift not required. If you know your way around OS software, can reason about the security of the code you write, and are excited about writing exhaustively tested software, we’d love to talk to you. We’r…
Earlier quoted context omitted.
What kind of windows programs are these? HiDPI is more than a decade old. A desktop application, no matter what OS it is, should always be tested with different scaling factors.
Oh my sweet summer child. Even software being written TODAY isn’t being tested in HiDPI. Win32 still makes it difficult.
Earlier quoted context omitted.
Life without retina displays is possible, but pointless.
Lower DPI is quite okay with good font rendering (FreeType, slight hinting, subpixel rendering). I have both kinds of devices.
Earlier quoted context omitted.
These days I mainly write Rust but I did write a semi complex iOS app and enjoyed Swift. I just didn't love how slow the type checker was and how it got lost. I recall having to break things into smaller bits to help the compiler, and there were some oddities about the language. The gap between the two languages is quite small, it just makes me wish Apple was also all-in on Rust
I see Swift as a more approachable version of Rust. If somebody is mulling over Rust but finds it too difficult to grasp, they could start off with Swift first and then move over to Rust. One of the main advantages of Rust is a more developed and thriving ecosystem.
Earlier quoted context omitted.
It also doesn't support Computer Use or Browser Use among other deficiencies
Sure but the basics should be down before tackling those, and they're not.
Earlier quoted context omitted.
I see Swift as a more approachable version of Rust. If somebody is mulling over Rust but finds it too difficult to grasp, they could start off with Swift first and then move over to Rust. One of the main advantages of Rust is a more developed and thriving ecosystem.
It has an unfortunate name though, maybe a short shelf life. Rust++ doesn’t seem inviting either.
If you want to help improve the security of OS software through the magic of memory safe languages, the team that did this work is hiring: https://jobs.apple.com/en-us/search?search=Spear&sort=releva... Knowledge of Swift not required. If you know your way around OS software, can reason about the security of the code you write, and are excited about writing exhaustively tested software, we’d love to talk to you. We’r…
Of course in an alternate universe where macOS (and iOS etc.) was based on Multics rather than Unix, it would have had essentially zero buffer overflows - which are hard to create in PL/I but hard to avoid in C. Even Apple's Pascal compilers from the 1980s had range checking...
But legacy C code can/should absolutely use things like clang's -fbounds-safety (has been in clang on macOS for years) etc. Fil-C is another option.