601–610 of 765 posts
> Finally, we see the instructions to right click. Err, control click.
Just recently I was on my iMac playing the "free guess" minesweeper where guessing is safe whenever you're forced to guess. The game needed a right-click to mark mines, and I got frustrated by Apple's magic mouse being prone to misinterpret right-clicks as left-clicks.
Now I know how to be in control with my right-clicks!
Earlier quoted context omitted.
I'm happy for OSM, that's great for you and in turn the community. But what about small open source projects? One-person projects where the idea of having several people working on securing legal non-profit status and then acquiring non-profit signing certificates from Apple is for all intents and purposes impossible? And certainly not worth just coughing up the annual $99 fee (+tax) to Apple? $99+ every year is a lo…
Outrageous is the entitlement of the current generations for not paying for their tools. Many of us used to pay for every single piece of software that we had to run on top of our already expensive computer around 2000 euros on today's money.
There are people that make Visual novels,text based games and other indie stuff(without using Apple tools most are Python,Java or Web tech) for free or a few bucks, I think they would not pay the Apple tax and either not support Mac at all or link to some instructions to workaround this limits while it is possible.
I'm very happy to have come across this sentence: > Finally, we see the instructions to right click. Err, control click. Just recently I was on my iMac playing the "free guess" minesweeper where guessing is safe whenever you're forced to guess. The game needed a right-click to mark mines, and I got frustrated by Apple's magic mouse being prone to misinterpret right-clicks as left-clicks. Now I know how to be in contr…
Earlier quoted context omitted.
This works for some type of software, but not all type of software. For example a file server or a file manager wont work. A VCS client wont work. A game engine that needs to keep track of imported resources (especially when you want automatic imports when the file is saved via a 3rd party tool - e.g. saving a model on Blender or a texture on Krita causes an automatic reimport/convert to the engine's format). Basical…
> A game engine that needs to keep track of imported resources (especially when you want automatic imports when the file is saved via a 3rd party tool - e.g. saving a model on Blender or a texture on Krita causes an automatic reimport/convert to the engine's format) A game engine isn't likely to do that in a production build. Even if it wanted to though, these sorts of "file ticket" sandboxes still has support for "d…
I actually have worked on two AAA game engines that did exactly that. The entire idea was to make importing stuff easier and minimize the time between the artists editing content in their content editor and having it imported and visible in the engine.
> Even if it wanted to though, these sorts of "file ticket" sandboxes still has support for "directory ticket" and "file watchers".
How are those given exactly? You'd need to ask for permission for every directory? If you cannot have the program monitor the directories, how would it know that a file changed before asking permission? Or the permissions will be asked at startup (since it is very common to edit existing content instead of only importing new content - the editor remembers the original paths for all content and can start monitoring it at startup).
TBH this all sounds like a UX nightmare, especially when the entire goal is to make the process smoother.
Earlier quoted context omitted.
And no open source software either unless the authors cough up the apple tax.
Not too relevant here, but I think the main thing keeping regular people from installing open source software is that most OSS is an unpolished usability nightmare compared to commercial counterparts.
Why does it even matter if it's a usability nightmare if the user wants it they should be able to install it if it's open source.
Earlier quoted context omitted.
This works for some type of software, but not all type of software. For example a file server or a file manager wont work. A VCS client wont work. A game engine that needs to keep track of imported resources (especially when you want automatic imports when the file is saved via a 3rd party tool - e.g. saving a model on Blender or a texture on Krita causes an automatic reimport/convert to the engine's format). Basical…
Sure it does! We just need sufficiently granular permissions for all of this stuff. “Do you want to give ClipboardManager access to your clipboard?” Yes. “Do you want to give TikTok access to your clipboard?” No. I agree that clicking a million permission boxes is annoying but ideally it should only be something needed for apps that don’t fit the media consumption model. The real problem is that the desktop security…
Why is it any different today? You can always only install applications you trust. It would be useful to have sandboxing for untrusted applications (especially when said sandboxing would also allow you to monitor what the application is doing), but not all applications are untrusted.
Earlier quoted context omitted.
While I also find these changes to macOS alarming and disappointing, I still vastly prefer macOS to Windows. My 2013 Macbook Pro is also still the best laptop I have ever used (I also have a 2017 Macbook Pro for work and I have to admit that the newer models rightfully earn their bad reputation). If Apple continues to head in this direction, I think the right move is to migrate to Linux. Windows is a huge step back,…
There are plenty of comparisons online showing for the same price as a Mac you can get a PC that will edit your photos, compress your videos, render your 3D architecture 3x to 4x as fast as the fastest Mac you can buy. If you're a professional might be throwing money down the toilet waiting for your mac depending on your use case. Note: I'm not a mac hater. I have 2, one I use every day and love it. I also have a PC…
In my opinion, it's simply not possible to learn how to override it by following macOS UI "hints". Every step of the way seems designed to hide this possibility, instead of giving users a warning and a clear choice.
Earlier quoted context omitted.
Yes, which is why i wrote "you cannot run unsigned software" and the part about slippery slope.
That's exactly what I'm confused about, where is the slippery slope? It's an extra step in your build process–an annoyance, not a slope. It's like if there was a requirement that macOS would not run binaries unless you stuck "APPLEISCOOL" at the front of all your binaries.
So, what follows next?
Hence the slope.