I also have the gut feeling (in part due to SwiftCrossUI, which I didn't try yet) that we are getting closer to a "GNUstep but for SwiftUI". I.e. something that provides a similar experience to SwiftUI on other platforms (Linux/Android, Windows, Darwin itself?). Half of GNUstep (Foundation) is already provided by Apple itself. I love the new cross platform version, it is *so* useful to me!
OK, so I just came up w/ the design for the NeXT Mac Pro, a Cube (ok, the original Cube idea is owned by someone else)! As you may know, the original NeXT Cube had space for four whole motherboards. In practice I'm only aware that either one or two got used (two w/ a NeXTdimension gfx card, the setup I have). But I think the original idea was that it would house 4 individual computers/board, connected by the Mach kernel (Mach ports!) to form a singular compute unit. #WWDC
I kinda hate how people are actually using MacBookPro's. If you are a photographer or scientist who is actually mobile, that's perfect, thumbs up. But there are so many devs who just have them sitting clamshell, as a desktop 98.9% of them time. This is just an incredible waste of resources, in particular the awesome display which goes when the compute has to go. Not good.
Now transport that to the modern times. #AppleSilicon mainboards are fully integrated machines and can't really be modular in the traditional way. But what if you'd have a machine that essentially houses 4 MacBook Pro's w/ Mx Extreme's! The M5 is released? Don't throw away your computer, just upgrade one, or all of your blades w/ the new one. Kinda like you replace the drives in your Synology if capacity suffers.
It is interesting how many people still live in the old FOSS world. When meanwhile all the rules changed and code got and gets stolen at an industrial scale. Didn't you realise yet that your particular license doesn't matter anymore? I don't really think this will kill FOSS, due to the inherent advantages regardless, but everything done is now essentially public domain, no attribution required. (unless some hero stands up and does proper lawsuits)
@whitequark Looks like Swift, except in Swift, you rather link a 6MB big argument-parser lib that statically types out all the possible options 🙈 (but really, the `match` looks like how Swift's `switch` works)
At least skim over those before touching Unix/Posix API's. I'm not really shocked how little people know about very basic things like pipes and how they work, but it's a problem those books can potentially fix 🙂
@obrhoff@frederik Ich verwende kein Insta aber ich vermute mal du hättest das Produkt gegebenenfalls auch anders gefunden und gekauft. Oder hat bei dir die Insta Werbung eine direkt Conversion ausgelöst?
@obrhoff No, I’ve played with that for years and it never made any meaningful difference. I think for Indies specifically themselves are the best promotion.
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 ...
@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.