Sequoia not allowing Composer to install Laravel

There is no reason to have F-Secure or any third-party AV app installed. You should uninstall it.

scanmaster wrote:

I'd been developing for decades on PC and switched over to Mac in February. Everything was really fast and smooth setting up my dev environment and ran well until I reset the Mac and updated to Sequoia. Now I'm told by the system that the 'operation is not permitted' when trying to install Laravel via Composer. I've tried changing the owner to my account but same issue. Does anyone know how to fix this as I can't get anything done?

What's Laravel and what's Composer? Those don't sounds like Mac developer tools. Apparently they are PHP tools. PHP? In 2024? What's the benefit to trying to run all of that on a Mac?

You should be able to get it working, but you are going to have to use your Mac in an atypical fashion. First, that means no updates. You can expect the Laravel/Composer people to have no idea about anything Mac-related. So if Apple releases a new update, you can expect it to have lots of problems. With these open-source frameworks, that applies not just to the project you are trying to use, but also to each and every dependency.

So when it all comes crashing down, as it will at least once a year, it's going to be your job to fix it. Mac developers will have never heard of those tools. Laravel/Composer developers will have never used a Mac.

scanmaster wrote:

Laravel's a PHP framework I've used for well over a decade now, Composer is a PHP dependency management tool - Composer can be installed with Brew and laravel is OS agnostic.

Ah yes. I see brew mentioned quite often. Whenever someone posts a question about some basic command line like "ls" or "cd" not working properly, it's always Homebrew. Always.

The whole reason I got a Mac is to develop IOS apps with Quasar as the frontend and Laravel for the API as Apple doesn't let you build for them unless you use a Mac.

Quasar? Another new one. 😄

And why not PHP in 2024? It's still used by around 80% of the websites in existence. It's fast, stable and fully OOP compliant with a massive community (a good percentage of which use Macs). What are you using for your APIs? I doubt using node for SSR is going to be any better or faster than PHP and will need updating far more than a PHP back-end.

SSR? Is that Server-Side Rendering? Apparently that is people discovering that they don't have to do everything in Javascript?

But you said you got a Mac to developer iOS apps. That doesn't have anything to do with HTML rendering. If you want to build a website...just...write the HTML? All this sounds like some kind of crazy Rube Goldberg web server. Just write your HTML and serve it on AWS CloudFront. If you need something dynamic, or a REST API for your app, do that in Lambda.

The bottom line is, I will fix it, but Apple need to remember there are literally millions of developers using their hardware to create websites and don't just use it as an 'appliance'.

Now you're talking websites again? Which is it?

Apple supports using Xcode to develop iOS apps. If people want to develop apps using Electron of whatever else is hip that day, that's on them. But if that is the path you take, you have to realize that your Mac isn't just an "appliance". It's running a crazy open-source Rube Goldberg app development platform that will collapse every time you update the operating system. You can choose to become an expert in those tools and be the person that tirelessly keeps them updated for years with no pay.

Or you can let someone else do that and run the oldest version of macOS that Apple will allow. That's true even if you're using Xcode. Currently, Apple requires developers to be running Ventura or later. So that's what I use for production builds on my primary computer. I do have a newer computer running whatever the latest version of macOS is currently released and/or in beta.

For websites, it really isn't much different, except that Apple doesn't provide any official website development tools. You're on your own there. I strongly recommend AWS. AWS is worth it for the SSL certificates alone. Did you know that Apple and Google are pushing to further restrict SSL certificate validity to 30-90 days? I'm on AWS, so I don't care. But that might be a big deal in your case.