Notices by Helge Heß (helge@mastodon.social)

@inthehands Essentially this:
```
thing.a = 5
thing.a = 5
thing.a = 5
```
should modify nothing but `a`. But those could also be composed values, the key thing is that you can assign as often as you want w/o side effects.
That's what makes a property to me, not whether it is computed or stored.

@inthehands No, the operation should just be idempotent, i.e. have no side effects. Like this:
```
final class Mehr {
var _x = 0
var y = 0

var x: Int {
set {
_x = newValue
y += 1
}
get { _x }
}
}
```
I wouldn't consider `x` a "property" here because calling it 10 times will have side effects unrelated to it. This would be fine:
```
final class Meer {
var _x = 0

var x: Int {
set { _x = newValue * 2 }
get { _x / 2 }
}
}
```

@inthehands Interesting. A property to me should have no meaningful side effects. I've seen people doing KVC properties and wondering when they run into issues because a property setter also set like 10 other unrelated things.

@inthehands I think the bigger issue/question is that properties are supposed to be idempotent. That's what makes it a property to me.

@BeAware @tychotithonus Wait for it if your “open source” models don’t manage to preserve the licensing terms of the original data.
It does take same balls to admit using such openly 👍

@inthehands It does, it predates OSX by years. It came to NeXTstep 3.2(?) as part of EOF

Oh, and I learned that the history of Foundation is dating way back to the beginnings of OSX. WTF 🙃

Ugh, the What’s new in Swift got me excited for a few seconds. I was fully prepared to finally see Linux cross compilation and debugging from within Xcode, the same like what we have for Darwin.
But it looks like what’s new is what’s old, we have had that cross compilation for years (probably for more than 5?).
“fremdschämen”

@inthehands Yes, but you have to do the I/O to write it to a file, and then load it into a buffer, then delete the file. I'd like the byte representation of an in-memory db w/o doing any I/O.

@finestructure @inthehands This is not the ask, SQLite has an in-memory DB which that stuff is probably using.
The question is how to serialize that in-memory SQLite DB to say a `Data`. I think the only way is to backup the DB to a file, then load the file into a Data and drop the file.

It is a bit unfortunate that one can't backup to and restore a #SQlite database from a byte buffer. Otherwise one could also use it to send serialized data over the network 🙈

Did you know that you can write #PostgreSQL stored procedures in #SwiftLang? "Bringing Swift to the Backend of the Backend’s Backend!"
http://www.alwaysrightinstitute.com/plswift/

How do you trigger undo on #visionOS? On regular iOS you shake the device for undo. Do you shake your head for undo with the glasses?

@inthehands @maxd @finestructure Which is also very similar with tests.

@inthehands @maxd @finestructure This is a really good one on static typing, in case someone didn't read it yet: https://blog.metaobject.com/2014/06/the-safyness-of-static-typing.html

@dgoldsmith My question wasn't why you think _whether_ they are doing it, but _why_.

@dgoldsmith Why do you think they even plan to do federation?

@inthehands I'm not kidding, literally every time I touch a Ruby project, be it Fastlane stuff or Jekyll, it simply won't work. Yes, I'm a noob about it and don't care about Ruby, but that's how it works for me. I usually end up getting it running somehow, but don't necessarily know why 🙈

@inthehands I have to fight with Ruby literally every single time I have to touch it, it is a mess too.
Python might have an unusual excuse: The original idea was “batteries included”.

@inthehands If it would be hidden completely that would be OK, but this is just bonkers. Afterthought? It was available from day 1. (and the issue is non-existent w/ the XDR)