I discovered yesterday that Windows has a command line package manager in Powershell that can install, uninstall and update basically every software you might ever want to install on a Windows PC. winget search"" winget list winget upgrade
I own my own instance. Your “license” is not accepted. Your instance sharing content with mine is an automatic agreement to my instance’s terms.
1.2 Grant of License: By uploading User Content, you grant Saik0-Lemmy a non-exclusive, royalty-free, worldwide license to use, copy, distribute, publicly display, and modify your User Content
See how silly this is? Your license means nothing. It’s just wasted screen space. And nobody is pissed. People are just trying to talk sense to you.
I actually thought PS was gonna be better than cmd… turns out consistency is a lot better in cmd… can’t make heads or tails in PS. I still use cmd to invoke stuff in PS, but only if there is no other way.
Well, it’s under a permissive license, so there is little he can do legally, except maybe sue them for not mentioning the original project, which I’m sure they will add and that will be that eventually.
That’s true. A little recognition would’ve been nice and I think that’s all he was asking for. Microsoft had a whole team work on it when they could’ve just given him a job to maintain it.
It’s their choice. I’m sure they also had this in the works as well, but it eventually didn’t work out (why pay another dev when we can have the ones already working for us do this as a side project… they basically just have to clone the repo and change a few things, that’s it).
As I said, he can sue for not mentioning the original project, but not much more… maybe he’ll think a bit more about what license to choose when publishing big projects like this publically.
And you never dug any further to see WHY you’re being denied access or WHY that file is not found.
Simple example, some distros will block regular user access to /root. That doesn’t mean that you can’t access those files, it just means that YOUR user can’t see them WHILE you’re logged in with that user… which is why bash file/dir completion will not work if you cd to /root/path/to/dir. Log in as root in the terminal and it works just fine. Some even might out right not see the files if you’re logged in as a user, instead of root, regardless if that user in the sudoers file or not (you type in the exact path to a dir/file in the terminal and it won’t open/cd to it). In those cases, even sudo won’t work for some things, you just HAVE TO work with root.
To be honest, this is very rare and has happened to me like once or twice (on some distros). In most situations/distros, sudo will work just fine.
I know instantly how to get the packages I need in Linux but I had to do some research to enable the webcam in Windows 10.
The idea that one OS is easier than the other is misattributed familiarity.
I discovered yesterday that Windows has a command line package manager in Powershell that can install, uninstall and update basically every software you might ever want to install on a Windows PC.
winget search ""winget listwinget upgradeThey pulled a corporate and rewrote an opensource project to embed it into windows
CC BY-NC-SA 4.0
Do you really need to license your comments?
© 2024 [email protected] - All Rights Reserved
(Plz don’t sue me for making a derivative work based your comment and violating the license kthxbai)
I love it when people get pissed off about nothing that even affects them.
CC BY-NC-SA 4.0
Yes sir I’m super pissed off how dare you do something goofy on the internet!
I dun gooed
I own my own instance. Your “license” is not accepted. Your instance sharing content with mine is an automatic agreement to my instance’s terms.
See how silly this is? Your license means nothing. It’s just wasted screen space. And nobody is pissed. People are just trying to talk sense to you.
idgaf
CC BY-NC-SA 4.0
I had a feeling this tool and its syntax was much too simple and elegant for it to be created by Microsoft.
I actually thought PS was gonna be better than cmd… turns out consistency is a lot better in cmd… can’t make heads or tails in PS. I still use cmd to invoke stuff in PS, but only if there is no other way.
Well, it’s under a permissive license, so there is little he can do legally, except maybe sue them for not mentioning the original project, which I’m sure they will add and that will be that eventually.
That’s true. A little recognition would’ve been nice and I think that’s all he was asking for. Microsoft had a whole team work on it when they could’ve just given him a job to maintain it.
CC BY-NC-SA 4.0
It’s their choice. I’m sure they also had this in the works as well, but it eventually didn’t work out (why pay another dev when we can have the ones already working for us do this as a side project… they basically just have to clone the repo and change a few things, that’s it).
As I said, he can sue for not mentioning the original project, but not much more… maybe he’ll think a bit more about what license to choose when publishing big projects like this publically.
They copied the open source project AppGet and screwed the developer. It’s an interesting read.
Exactly. OP’s meme makes no sense to me. My experience has been that using Linux is a never ending series of file not found and access denied errors.
And you never dug any further to see WHY you’re being denied access or WHY that file is not found.
Simple example, some distros will block regular user access to
/root. That doesn’t mean that you can’t access those files, it just means that YOUR user can’t see them WHILE you’re logged in with that user… which is why bash file/dir completion will not work if you cd to/root/path/to/dir. Log in as root in the terminal and it works just fine. Some even might out right not see the files if you’re logged in as a user, instead of root, regardless if that user in the sudoers file or not (you type in the exact path to a dir/file in the terminal and it won’t open/cd to it). In those cases, even sudo won’t work for some things, you just HAVE TO work with root.To be honest, this is very rare and has happened to me like once or twice (on some distros). In most situations/distros, sudo will work just fine.
To enable the webcam on windows you just…open teams and start a call or use one of the apps that use the camera…
Unless the vendor decided to lock it down until you manually unlock it with the administrator account. Then even Teams can’t see it.
It is almost like those Linux users are not really as technologically capable as they claim to be.
Or they are just lying and haven’t used Windows in over a decade.
Even on Linux, to use the webcam you just plug it and open gnome cheese or Google meets…
Ok great so the webcam works easy without researching on both OSes.
Unlike what arthurpizza claims.
How do you know if you don’t already know the package name?
I have to always Google for the package name, which similarly is what I do to find a Windows installer but instead of the name it’s download link.
Or
Or
Thanks!