>massive 2 year headline topping legal battle >explicitly because BSD contained actual UNIX AT&T code >entire point of mach was to create a unix-like replacement kernel for BSD so they could remove all traces of actual UNIX code from BSD >mactoddlers unironically call osx UNIX in 2016 the year of our lord stallman, hallowed be your name, your kingdom come, give us each day our daily freedoms, and forgive us our proprietary programs, for we ourselves forgive everyone who is indebted to us, and lead us not into the evil malevolent morally bankrupt wasteland that is cuptertino
GPL programs can be sold at a profit. That's how Redhat operates, and the guy who develops Aseprite does the same (you can compile the latest builds from his github freely, or buy an installer from his site)
But yeah no OSX is not built on Linux and is a heavy derivative of BSD. The UNIX namesake means nothing anymore as unix-likes have become industry standards.
yeah whatever. the important point about an os is that its a unix-like, dont care if its aix, solaris, hpux, linux, osx, bsd, whatever. the point is, unix-likes are awesome, sure some are better than others, the point is they're not a piece of shit os like m$. theres far too much "oh linux is fabulous" going on here, linux is awesome BECAUSE first and foremost its a unix-like.
I actually isn't based on Linux. If anything, it's Linux's brother. Both are effectively clean room clones of AT&T Unix. Also, AFAIK, many open source licences don't forbid sale of the software, you just have to give the source for free.
1. Mac OS X is based on Darwin/XNU, which is based on BSD. 2. You can legally sell "free as in freedom" software. Even if it's licensed under the GPL. If it is licensed under the GPL, however, you must release your source code, and your users must be free to modify and redistribute your software under the same terms.
>>52378405 I use cygwin daily and works just fine. Powershell is something entirely different to unix and requires you to write scrips you can't run outside of Windows so it's not anywhere close to serious - it's a joke.
>>52378406 It does not exist to interact with windows api - it exists to interact with POSIX api, which is properly supported.
>If you know Unix and those tools do what you need them to do on Windows - then you are a happy guy and there is no need to learn PowerShell (unless you want to explore).
>My original intent was to include a set of Unix tools in Windows and be done with it (a number of us on the team have deep Unix backgrounds and a healthy dose of respect for that community.) What I found was that this didn't really help much. The reason for that is that awk/grep/sed don't work against COM, WMI, ADSI, the Registry, the cert store, etc, etc. In other words, UNIX is an entire ecosystem self-tuned around text files. As such, text processing tools are effectively management tools. Windows is a completely different ecosystem self-tuned around APIs and Objects. That's why we invented PowerShell.
>What I think you'll find is that there will be lots of occasions when text-processing won't get you what you want on Windows. At that point, you'll want to pick up PowerShell. NOTE - it is not an all or nothing deal. Within PowerShell, you can call out to your Unix tools (and use their text process or PowerShell's text processing). Also you can call PowerShell from your Unix tools and get text.
>Again - there is no religion here - our focus is on giving you the tools you need to succeed.One last comment. If/when you start to learn PowerShell, I think you'll be pretty happy. Much of the design is heavily influenced by our Unix backgrounds so while we are quite different, you'll pick it up very quickly (after you get over cussing that it isn't Unix :-) )
>>52378585 >What I think you'll find is that there will be lots of occasions when text-processing won't get you what you want on Windows And what I am finding is there are tons of occasions when cygwin does help me to get what I want. Also repeating text-based does not help you prove your point (even if said by original creator) when cygwin actually has proper support for X. What this wall of text means is cygwin does not help you to interact with Windows - and that's true, but cygwin exists exactly to create non-Windows workspace while still running Windows.
>>52378434 >Powershell is something entirely different to unix and requires you to write scrips you can't run outside of Windows
The entire point of it is managing Windows servers, linux servers already have their own tools, do you even understand the purpose of PS?
Either way I find it far better than the "teehee i'm so clevur" backronyms and in-joke meme tier names the open source community made for so many basic linux commands.
PS is what UNIX/linux should have strived for, just not attached to Windows. Every command is Object-Action, Get-Item, Add-Module, etc no fart and poop jokes "just because" the dev that made the tool was 12. Dude that made it is an old-school UNIX guy, and he basically created what a CLI should've been from the start.
Makes my life easier since it's plain english, so training jr. admins is piss easy. Lot of times I don't even need to tell them the command, just tell them what to do and they can actually figure it out easily on their own without even having to resort to google.
>>52378657 >The entire point of it is managing Windows servers, linux servers already have their own tools, do you even understand the purpose of PS? We are talking about working in unix-like environment on Windows. I am calling powershell a joke in context of that - and I am calling it that because it doesn't move Windows one millimeter closer to being unix-like.
>>52378405 to expand, Powershell was created as a unix shell clone because they found out a shell and the coreutils (Microsoft SFU/SUA/Interix) can't do shit against an api.
the only thing you can manage is IIS. IIS is Microsoft's only text file based application
so instead they got a team of ex-unix guys, made a shell, built it on .net, allowed it access to wmi and gave it native remoting
>>52378434 https://www.youtube.com/watch?v=3-M2NhmFwso&t=2m (2:00-11:00) http://www.jsnover.com/Docs/MonadManifesto.pdf take it from the guy who worked at IBM/Tivoli as a unix guy, then joined Microsoft to make Powershell. A total UNIX shell clone that does what Interix, Cygwin, mingw and others couldn't.
>>52378613 >but cygwin exists exactly to create non-Windows workspace while still running Windows So, you're saying you like to smell your own farts. Why not commit? What do you need Cygwin for, if it isn't doing Windows work on a Windows box? It just sounds like a bad excuse to use something obscure to sound smart. You can't admin your own box, you can't admin your network.
>>52378585 Tools aren't just tools. Tools are physical or mental extensions for fleshy monkey-like lumps of watery shit that are born incompetent at everything but picking fruit and slamming smaller animals against the ground.
Without tools, you're just a chimp that has the brain to plant its own fruit trees and raise animals in captivity so they may be beaten to death and consumed raw. Not much of an improvement over picking and hunting from what's already there. If your tool doesn't extend you well, you're that chimp compared to someone with a tool that extends them well.
For most people, a bunch of APIs are a little harder to work with for a filesystem, since they're analogous to our library perusing, paperwork filing culture. The windows system is more like querying the elder for knowledge and praying to the untouchable gods for change. So, it doesn't extend most people that well. The learning curve is obnoxious, it leaves you a chimp, so you can understand the religious fury, can't you?
>>52378681 When I said ms once did that I was talking about that failed posix implementation during the nineties not ps And I agree even though I use Linux that if you work on windows you should be using PS not cygwin
>>52378681 >So, you're saying you like to smell your own farts. >Why not commit? What do you need Cygwin for, if it isn't doing Windows work on a Windows box? It just sounds like a bad excuse to use something obscure to sound smart. >You can't admin your own box, you can't admin your network. I don't admin windows server at all. I would never want to admin Windows servers. I work with linux a lot, and I am also forced to run Windows on my workstation because software. Cygwin just makes the environment more friendly for me. This was never about managing Windows servers.
>>52378717 I said cygwin isn't integrated into the system. And using it is ridiculous. As people say here use power shell.Wine is not perfect to run on Linux and cygwin is just like that Calling me retarded won't save your ass anon
All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.
This is a 4chan archive - all of the shown content originated from that site. This means that 4Archive shows their content, archived. If you need information for a Poster - contact them.
If a post contains personal/copyrighted/illegal content, then use the post's [Report] link! If a post is not removed within 24h contact me at firstname.lastname@example.org with the post's information.