You will need to use the builtin Calendar and Mail apps to link up multiple accounts

Ah, this explains why I can’t ask Siri for the weather forecast anymore.

Now I have to go outside to find out. Fine.

M1 does only support one display natively; I think you can get around this with a usb hub. You can also airplay to displays/tvs that support it (anything you can plug an apple tv into, and many newer tvs). You can also use an iPad as a separate display if you have one.

There are a lot of nice things you can do, especially if you own multiple apple products (like, you can airplay music or video to your computer from your iPhone, or copy-paste between devices that share an Apple ID)

Some stuff is annoying though. Linux support on M-series chips is still evolving (though very usable), it’s really not super straightforward to record the audio of your Mac (think screen recording that also captures whatever audio is passing through your AV Devices) because of implementation decisions way back.

Generally, I use a Mac though; because I get enough utility out of stuff like AirPlay, AirDrop, iCloud, and other random stuff that you kinda need to “just know about” to make up for the downsides of not being able to completely control my system.

Nix/nixpkgs is pretty well supported on Mac, though, so it’s not like I’m forced to use all the default binaries MacOS ships with.

Also, their displays are really really good on the Macbook Pros and the speaker quality (especially on the 16") is by far the best sound quality I’ve seen come out of a laptop. That doesn’t matter if you have a Mac Mini, though.

Normally there’s a separation between raw SQL and commands being issued by the UI to avoid what you’re describing (SQL Injection).

For example, the UI might call /posts/new with a JSON body describing the new post, this might look like,

NewPost {
  title: String,
  body: String,
  author: UserId
}

The Lemmy server then going to receive that “message” from the UI and use it to execute something like INSERT INTO posts SET title='my post' body='thoughts and stuff, I dunno' author_id='my user id'

This is fine.

What’s actually the problem is if you do something more complex, like if the UI queries for all posts by a set of authors where the time they were submitted was between some specific date range with contents matching blah blah blah and some other criteria. Make a the right query and you might hit a situation where the database behind the Lemmy server doesn’t have the data organized (think, like, a library; how things are organized by author name, or book title) in a way that makes finding matching results an easy thing to do; and instead the database need to look over every. single. post. multiple times to gather up the right results.

Now do this 1000s of times in quick succession.