This whole ARM thinggy comes as no surprise...
This is gonna cost Intel an ARM and a ...
As mentioned in there, some clever peeps spotted an ARM compatiblility in macOS (or OSX as it was then) back in 2016! Surprised this hasn't happend earlier...
🤣 OS flame wars... I guess it's been a while...
ShovelKnight wrote on 2020-07-29, 12:57:
I guess it depends on what kinds of customizability we're talking about. macOS doesn't support silly-looking UI themes, for example.
Yes agree, thats what these conversations always boil down to... customisation and how it looks... does macOS support any theme other than dark, and erm... not dark though? 😉
ShovelKnight wrote on 2020-07-29, 12:57: On the other hand, it has some extremely useful features that I sorely miss in Windows, such as very fine-grained control over custom keyboard shortcuts (which could be system-wide or per application) or built-in GUI scripting.
You can do all this in Windows afaik, there certinaly may be some reserved keys for various things in various OS's , but nothing a script can't do in most cases invoked by a non-reserved key. Can you give an example of what you mean?
Software developers regularly use automation wrt to the UI for testing purposes, especially regression testing.
The ability to perform UI automation (while certain api's/sdk's do provide varying degrees of this out of the box) is kinda the responsibility of the developer who writes the program (specifcally when writing the UI) to support it unless going the full-on black-box route (in which case UI automation will work with everything...caveat... but have many problems along the way such as varying screen sizes and window/button locations). If anything, nix is the worst for this as there is no 'standard' desktop environment so you need to pick the GUI toolkits/window manager you want to support and stick with those.... or have releases for; macOS... Windows... and then any number of nix distros (which is a support nightmare and somewhat wasted since nix users account for probably ~1%).
VileR wrote on 2020-07-29, 15:06:Probably because PowerShell is freaking horrible as a general-purpose CLI environment. If most Windows tutorials were written f […]
Show full quote
appiah4 wrote on 2020-07-29, 08:37:To be honest, I don't know why there aren't more Windows tutorials that use the PowerShell.
Probably because PowerShell is freaking horrible as a general-purpose CLI environment. If most Windows tutorials were written for PS, they'd be 10 times as long just for the sheer unwieldiness of constructing PS command lines, and every task would probably perform ten times slower too for that matter.
I'm sure it's good for *something*, or they wouldn't have made it, but for the life of me I couldn't tell you what that is. No idea if the concept is at fault ("everything is an object"), or just the implementation (making correct/optimal usage too non-obvious). All I know is, whenever I've tried using PS for anything more than a trivial task, I ended up tossing it and going for a different solution. Typically the latter has always proved much faster and easier.
Mind you, I'm used to Windows and prefer it as an OS, and I've never been afraid of CLIs or of learning new languages and environments. Even so, I'll take bash any day over TurtleShell. And cmd.exe works just as well given the right toolset (Swiss File Knife, AutoHotkey etc).
naaa.. PS is freaking awesome and very very powerful imo... I'm not really into the whole cmdlet thing, however I use it 99.999999% of the time over the command prompt mainly due to it supporting unix commands as well as standard dos/cmd.exe syntax... so batch scripts work and you can basically call .Net stuff in there without having to write (and compile) a program.
There are huge numbers of tutorials on powershell (it is a massive area)... just gotta look in the right place... it's certinaly a PowerUser's program, and I hear (although don't know myself) that sys admins love it.
Bruninho wrote on 2020-07-29, 16:29:Does Windows allow you to use a different terminal CLI ? Not that I know; the only options are CMD or PS. "But there is WSL2..." yes, except that WSL is kind of a linux environment.
A CLI is just a "command line interface", so if someone wants to write an interpreter to parse the syntax of said CLI... it can exist on any OS. Natively thats another matter.. each OS picks their native CLI and subsequent syntax. The problem arises when scripts for said CLI syntax want to access filepaths etc which are accessed and governed by the OS. Of course paths too, can be converted but that comes with a lot more issues since the OS decides where to put things like User documents (C:\Users\{user_name}\Documents for win, /home/{user_name} in nix etc). Since many scripts inevitably hook into some functionality within the OS, they tend to be written for the OS (or follow the FSH aka File System Hierachy standard)... e.g. I could write a bash script and run (most of it) in PowerShell as long as I am not expecting the documents folder to be in the /home/{user_name} location (although I can still do "~/Documents"). Same for running a batch file on nix (if there was a cmd.exe equiv interpreter on nix) and I wasn't expecting user programs to be in C:\Program Files... as they are in /bin or /usr/bin etc...
My personal ramblings wrt to OS's...
I use all 3 OS's mentioned both professionally and non-professionally... I think most of the criticism levied against any particular OS is because people have limited exprience or don't really know how to use and/or script in said OS's.
I like macOS, and out of the box, I find I am most productive in it, however customisation is somewhat difficult (you need to go off piste to really get the UI customisation that other OS's provide as standard)... once I have setup nix or windows with the scripts and tools (and look) I want/need, I am as productive (if not more) in those OS's. macOS mentality is definately "It's our way or the highway", but then they do appear to put most effort into getting "their way" to be as fluid as possible... Certinaly for some reason I care less about the look when I use macOS and can just get on with stuff, however every now and then they do something which is really annoying, and usually there is no easy alternative so if you don't fix it to the way you want (if that is even possible, which it always isn't)... you are screwed. tbf though, I haven't experienced that happening recently (I think lion or moutain lion changed something that really annoyed me although I can't rememeber what... I just remember sticking with snow leopard for ages until going to El Captian).
ime I have yet to come across a desktop OS (certainly mainstream desktop OS) which is limited in any of the regards mentioned in this thread (although I'm sure they exist). Even Workbench (Amiga) had UI and non-UI automation functionality.. in fact ARexx was a very powerful tool which was incorporated into pretty much every Workbench application (functionality came with Intuition afaik, Workbenchs' GUI toolkit...tiz only what I have read though, I would be lying if I said I have done development in Workbench so no first hand experience with that).
I know non-windows users like to think windows is awful and that their OS is competitive... but the reality couldn't be futher from the truth... just look at the market share of each OS. Windows has a massive one, and as a result there are loads and loads of programs on it... also most software hooses (unless their customers request it, or they are looking to work only in a market with a certiain OS) will default to Windows as that is the safe bet to get customers... and thus monies to feed the famile etc.
Personally... shove me in front of any OS, give me a book which outlines it's command line standard and/or scripting support and in no time I would probably be happy and do everything I needed to (providing the OS supports it of course... which it probably would).... maybe not templeOS... although I really want to give that a try.
/useless_contribution_to_thread