Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How about make microsoft terminal can be used on mac osx or linux #563

Closed
ghost opened this issue May 8, 2019 · 11 comments
Closed

How about make microsoft terminal can be used on mac osx or linux #563

ghost opened this issue May 8, 2019 · 11 comments
Labels
Issue-Question For questions or discussion Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@ghost
Copy link

ghost commented May 8, 2019

How about make microsoft terminal can be used on mac osx or linux.

I am using both windows and linux .

the new microsoft terminal looks good.

can it be ship to mac osx and linux ?

@DHowett-MSFT
Copy link
Contributor

Hi! Thanks for the interest. Since we depend on some parts of the Windows platform, that’s not an option for us. Sorry!

@DHowett-MSFT
Copy link
Contributor

#504 dupe

@DHowett-MSFT DHowett-MSFT added Issue-Question For questions or discussion Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. labels May 8, 2019
@dinfyru
Copy link

dinfyru commented May 8, 2019

t_t

@zinking
Copy link

zinking commented Jun 5, 2019

with windows having 2 kernels now, I'd suggest seriously consider support other platforms. I might moving back to windows because of this.

@miguelusque
Copy link

Hi all,

First of all, thank you for this great product. I ❤️ it.

About the following comment:

Since we depend on some parts of the Windows platform, that’s not an option for us. Sorry!

I understand that you make use of some parts of the Windows platform, but I was wondering if there is no equivalent to that functionality in other Operating Systems, like MacOS or Linux.

Is it so tight the integration with Windows OS which makes so hard to port to other OSs?

Thanks! And congrats again for the great work you are all doing!

Regards,
Miguel

@zadjii-msft
Copy link
Member

@miguelusque See #6074 (comment):

From #4235 (comment)

We're dependent upon C++/WinRT and XAML Islands (UWP XAML) for our UI. We're also using DX/DWrite for the text renderer. Unless those are ported to linux sometime, then I'd say there's very little chance we ever support linux.

s/linux/macOS/

@miguelusque
Copy link

Hi @zadjii-msft ,

I understand the current status, thank you for your swift reply.

Nevertheless, Microsoft has proven to be able to develop software which runs on multiple platforms, i.e.: Microsoft Visual Studio Code, Microsoft Teams, Microsoft Office...

Therefore, I am keen to think that it is not because of technical issues why a MacOS/Linux version is not available yet, but a matter of other priorities and/or project planning.

Once again, congratulations for the great work done.

Regards,
Miguel

@zadjii-msft
Copy link
Member

Visual Studio Code and Teams are Electron applications which are fundamentally web apps, so they're trivial to make cross platform. However, they do come with the burden of the entire Electron runtime, and that's something that we weren't comfortable with on the Terminal team. We wanted to make sure to build a native application so that in the long run, the Terminal would have a smaller memory commit and be far more performant than we could ever get with Electron.

Office on the other hand has been around for decades and has an enormous team of engineers. I'm not sure what tech stack they're using, but I'm sure that once they got the apps running cross-platform, it was easier to maintain that. Plus, with their larger teams, it's probably easier for them to maintain two different UI stacks (one for Windows and one for OSX). They likely have a team of engineers for the Windows version and a separate team for the Mac version. With the 4 of us on the Terminal, I'm not sure it's really feasible for us to try and support an entirely separate UI stack.

If WinUI, DirectX, and WinRT were available on OSX, then it would be trivial for us to port the Terminal to MacOS. Those are all critical components in how the Terminal is built. Replacing any one of them with a cross-platform solution would be an enormous undertaking, if it's possible at all.

So you're probably not wrong. There might be replacements for each of those components. We could use (whatever the UI stack on OSX is), OpenGL, and (something?) to replace them. But it absolutely is not a priority for us when we'd rather work on improving the developer experience here on Windows first and foremost. We'd rather be working on hyperlinks in the Terminal (#574 #204), or adding support for a default Terminal application (#492), or tab tearout (#5000), or application theming (#3327), or Mark Mode(#5804), or Quake Mode (#653), or any of the other 1000 open issues on this repo. Adding support for OSX would mean pushing a bunch of those features back by at least a year.

So that's where I'm coming from.

@tracker1
Copy link

@miguelusque you might want to take a look at hyper It's not quite the same, but offers some similar features and is cross platform. It's what I tend to use in Linux. On mac I use iTerm2 and on Windows I'm using Windows Terminal.

@danielktdoranie
Copy link

How about make microsoft terminal can be used on mac osx or linux.

I am using both windows and linux .

the new microsoft terminal looks good.

can it be ship to mac osx and linux ?

LOL no thanks ha ha ha

@DHowett
Copy link
Member

DHowett commented Sep 8, 2020

@danielktdoranie was it necessary for you to let everybody subscribed to this repository that you don't particularly care for somebody's rejected feature request? No? Well.

@microsoft microsoft locked as resolved and limited conversation to collaborators Sep 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Issue-Question For questions or discussion Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

8 participants