Posts by cocoaphony@mastodon.social
(DIR) Post #APoFfUY468hll0Fmgi by cocoaphony@mastodon.social
2022-11-20T22:52:20Z
1 likes, 0 repeats
Oh look, these functions are identical. Better merge them into a generic!But as they evolve, they have slightly different behaviors, so time to add more options!(I think I'm in that Gru presentation meme right now.)Maybe I should have thought just a *little* harder about how these two "identical" functions were going to evolved before replacing them with a generic. Since this entire process played out over…um…30 minutes…maybe it could have been foreseen.
(DIR) Post #APuQOf5RtOXat2dQfY by cocoaphony@mastodon.social
2022-11-22T23:25:33Z
1 likes, 0 repeats
The people I work with are the best people. They brought me this today: https://westling.dev/b/extremely-linear-git
(DIR) Post #AQ4BqI3pXamvqiC3SC by cocoaphony@mastodon.social
2022-11-28T14:11:07Z
1 likes, 0 repeats
I love value types so much for correctness. Local reasoning make so many things clear. Some quirks when mutating aggregate data structures, but still, very nice.Value types and performance... we dance again, you and I.
(DIR) Post #AQ4BqJtciVoPXdQvp2 by cocoaphony@mastodon.social
2022-11-28T14:14:50Z
0 likes, 0 repeats
I'm doing very foolish things like passing a large value to a mutating method of one of its own properties. You'd think fixing that would improve things dramatically. Nah; the compiler already inlined it for me so it didn't matter. It's very smart. Which makes finding what the compiler couldn't fix even harder.Not a complaint there. The compiler is doing its job really well. I just wish I had (even better) Instruments tools to figure it outLooking forward to move types. They'll help too.
(DIR) Post #AQJXV9FmCg6OobVIq8 by cocoaphony@mastodon.social
2022-12-06T00:36:14Z
0 likes, 0 repeats
@nicklockwood @davemurdock wouldn’t that break SwiftUI? I was pretty sure a key rule is that body doesn’t change; it’s a pure value. State impacts how it’s rendered, but it shouldn’t change its value.
(DIR) Post #AQJZpCOQRMfGFhEokq by cocoaphony@mastodon.social
2022-12-06T01:22:25Z
0 likes, 0 repeats
@shadowfacts @davemurdock @nicklockwood the only confusion here is whether referencing .body counts as “a render/update loop.” I’m guessing that the SwiftUI folks have realized they we won’t follow the rules and have coded very defensively in a way that makes that work out, but it doesn’t change the rules.I think there’s a (non-random) reason randomElement is a method, not a property.
(DIR) Post #AQJbOoiY2gklCfCLLc by cocoaphony@mastodon.social
2022-12-06T01:51:42Z
0 likes, 0 repeats
@shadowfacts @davemurdock @nicklockwood I mean the other way around. There’s no promise that the only reason that “body” is accessed is for re-render, or that it will accessed exactly once per render loop. I expect this happens to be true, however.
(DIR) Post #AR4X9Ho6qtE1P2FrQO by cocoaphony@mastodon.social
2022-12-28T17:01:12Z
1 likes, 0 repeats
Big-O matters, but it's often memory that's killing your performance.: https://cocoaphony.micro.blog/2022/12/28/bigo-matters-but.html
(DIR) Post #ARGrjxbZG0HGnn66m8 by cocoaphony@mastodon.social
2023-01-02T21:16:20Z
0 likes, 0 repeats
Trying out chat.ai again as a super-google trying to find a good USB-C hub that has a DisplayPort 4k output and some USB-C and A ports. And it looked really good at first, until I realized that not single one of its initial recommendations has DisplayPort output...After being corrected, it did get me on a bit better track (only one of its later recommendations was completely wrong, and also no longer made).Eh...It does still seem useful, but it's wrong so often.
(DIR) Post #ARGrjy4HXFFKEqX2X2 by cocoaphony@mastodon.social
2023-01-02T21:24:52Z
0 likes, 0 repeats
That said, a really interesting side effect of how it uses conversational output, and even keeps chat histories, is that I really want to go back and let it know how its advice turned out, and say thank you when it is helpful. I don't think there's anything bad about that. We're a family with a history of putting googly eyes on the printers.
(DIR) Post #ARGrjyWHr7eDdhdPBQ by cocoaphony@mastodon.social
2023-01-02T21:29:48Z
0 likes, 0 repeats
It's not really chat.ai's fault that it can't find a good USB hub for me. I suspect there isn't really one that I'll find ideal out there, and the one's that are close are unreasonably expensive because they have more features than I want. I suspect, however, that no mater how many restrictions I put on it, it will always keep recommending products, even if it has to make them up, rather than admit it doesn't have a good answer for me. And I think that's a weakness.
(DIR) Post #AScby0YTSt5u8FxFbs by cocoaphony@mastodon.social
2023-02-13T01:02:56Z
1 likes, 0 repeats
In no way judging the account. I'm sure they're very nice people. I have no idea. But somehow I feel judged.
(DIR) Post #ASjx34m8evfvoUK7LE by cocoaphony@mastodon.social
2023-02-16T14:42:15Z
1 likes, 0 repeats
I don't often speak well of Feedback Assistant, but I want to call out a great feature that was added at some point: background sysdiagnose upload. Apple seems to have backed off demanding a sysdiagnose for everything, even feature requests (thank you), but sometimes sysdiagnose is a reasonable tool. Making it so much easier to attach has been a welcome improvement.While the feedback process is still horrible, the tool at least is now pretty decent.
(DIR) Post #AZhiIyuUYtqHYAuvY0 by cocoaphony@mastodon.social
2023-09-12T12:02:18Z
0 likes, 2 repeats
@ZachWeinersmith I spend an unfortunate amount of time helping new coders with ChatGPT-generated code. Repeatedly, the code is worse than nothing. It takes them down the wrong road (often a nonexistent road), making it harder for them to find the right approach. Code-reviewing AI code is very difficult because its mistakes are not like the mistakes human coders make.You should not use an AI to write code you couldn’t have easily written yourself. You must be able to carefully judge its output.
(DIR) Post #AcaUR4meGqLMrnAWgq by cocoaphony@mastodon.social
2023-12-07T14:58:40Z
0 likes, 2 repeats
A reminder: When that major security bug shows up in one of your dependencies, and you need to ship a fix right now, that's not the time to discover you're 3 years and 6 API-breaking changes behind the version that has the fix.Upgrade your dependencies when you don't *have* to. That way, when it is critical, it will be fast and low-risk.This is *especially* true about that risky upgrade you've been avoiding. Take the hit now when you can schedule it. Don't let others schedule it for you.
(DIR) Post #AlOkMcuEL4mBGuTgKe by cocoaphony@mastodon.social
2024-08-27T16:44:03Z
0 likes, 0 repeats
@interfluidity bad.The 2A has been overrun by a willful disregard of history. Gun control existed in the 18C and was relatively common in the 19th. Our Court chooses to ignore the history. It cherry-picks based on what individuals feel probably was true rather than anything that was.The 1A concerns you point to have to do with failure to enforce existing anti-monopoly laws. While maybe 18C lawmakers didn’t imagine Facebook, it’s because they didn’t imagine Standard Oil, not the Internet.
(DIR) Post #AlOlQ3TE84m4U02tzk by cocoaphony@mastodon.social
2024-08-27T16:55:54Z
0 likes, 0 repeats
@interfluidity Standard Oil (as Exxon) did exactly what you're describing. The whole world of climate change denialism, based directly on the tobacco cartel's "just asking questions" about lung cancer.A constantly repeated point in the founding generation was about aligning powerful interests against each other. (Some argued for abolishing powerful interests entirely, but the ones who won the Constitution took the "opposing powers" approach). 1/
(DIR) Post #AlOmVuZOEaQiZOHjBA by cocoaphony@mastodon.social
2024-08-27T17:01:56Z
0 likes, 0 repeats
@interfluidity The 18C and early 19C was filled with outrageous clickbait. That was no surprise.But the assumption was that there would be powerful parties opposed to each other and that would be ok. That's why I point to monopoly and cartel power.In fairness, the major newspapers today also align, even though they compete, because they're all owned by billionaires. So that seems different, like the alignment of Congress and President.
(DIR) Post #AlOnSCYdVvCd9bj9km by cocoaphony@mastodon.social
2024-08-27T17:18:40Z
0 likes, 0 repeats
@interfluidity I think this is definitely in line with the principles the 1A was premised on. Clearly, the only people the 1A was really imagined to apply to were white, male landowners (who the Founders generally envision as the "all" in "all men are created equal"). But within that group, there is a clear assumption that one could only be so powerful. Even today, Rupert Murdock doesn't have so much power *personally*. He has it because we invented corporations and gave *them* rights.
(DIR) Post #AyEdDBAk7k6d5HBKWO by cocoaphony@mastodon.social
2025-09-15T13:21:45Z
0 likes, 0 repeats
@nina_kali_nina makes sense. He’s just using the teletype’s encoding directly (which does make sense even if it is obnoxious). I don’t know why I imagined he was trying to make it easier on the operators. :)