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

I sometimes wonder whether the sole USP of BSky is that it is American. It's not meaningfully different to Masto. But you get a proper company backing it, with the goal to make a lot of money out of it. Not that communist crap where you sponsor or not as you see fit ;-)

@rhysmorgan I assume most of those people have been Americans? I don't know a single non-tech person on BSky, while I know quite a few on Masto. But yes, even more on Twitter.
The "having to choose an instance" is just boring non-sense. You can just do mastodon.social if you don't care.

@rhysmorgan The argument is weak, the same people don't realise what they are getting into w/ BSky either. It's essentially the same like opting for mastodon.social, except much worse. There are not options in the the first place, *if* you care 🙃
Maybe a value proposition of BSky is that "we are exactly like Twitter". But then you wonder why people want to see the same thing happening over and over again ...

@obrhoff Fittingly it’s the other way around 🙃
The AppKit coordinate system is a proper one as you learned it in school. (same for RealityKit btw)

@fluchtkapsel @inthehands This is like saying Signal is bolted on IPv4 which was never meant to be secure. Sorry, but this is non-sense. Both PGP and S/MIME are perfectly viable and proven standards to provide proper E2EE.
But as usual standards have to be *implemented* and made usable. E.g. Apple has done the former, but didn't invest in the latter.
It works for Signal and WhatsApp because they are silos. That's not necessary w/ email.

@inthehands Email has e2ee since essentially forever. The claim it not being designed for this is a little misleading.
Is it supported well? No! Why? Because the vendors either want your data or promote a different platform for secure communication.

@joe @mcc We also had Objective-TCL. Storing pointers as strings, you bet! https://wiki.tcl-lang.org/page/Objective+Tcl

@lambdageek @joe @mcc JavaScript is prototype based which is pretty cool for such a popular language, it doesn’t have messaging though, which is more important in the
context.

@mattiem @calicoding Ref counting actually is expensive because it is thread safe, it’s the global interpreter lock of Swift.
(and it doesn’t just affect user types, all the cow types use it)

@joe @mattiem @calicoding Even if there is some atomic instruction doing the thing, the cores would still have to synchronize ie flush their pipelines, no? I don’t know much about such low levels and some info why it isn’t expensive would be welcome 🙃
Or how expensive compared to a simple rc++ increment.
My assumption is that RC is massively more expensive, is that wrong?

@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.