Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Windows Terminal Source Code

github.com

Post reply on HN
Print view View original

191–200 of 214 posts

Re: Windows Terminal Source Code

#191

Post by Maursault »

ChuckNorris89 wrote: post #149
Maursault wrote: post #62

Earlier quoted context omitted.

This is a straw man, and also not entirely accurate. Darwin is BSD, and in theory just as useful as BSD, or FreeBSD, NetBSD, and useful to developers, and to anyone that can figure out how to install it and use it. [1] Meanwhile, Windows without hardware less than 2 years old is absolutely worthless. Thus, Linux. [1] http://www.puredarwin.org/

>Meanwhile, Windows without hardware less than 2 years old is absolutely worthless. This is false. Source: Installed Windows 11 from official Microsoft ISO on a laptop from 2016 (6 years old) and runs buttery smooth. Please stop spreading FUD like this.

If it were not true, Linux would never have become popular. Linux evolved beyond quickly fixing what Microsoft broke to take over the server space, but that was Linux's first practical reason for existing, to mitigate the problems with Windows slowly dying after about 2 years of being installed and used daily.

Re: Windows Terminal Source Code

#192

Post by pjmlp »

mattl wrote: post #187
pjmlp wrote: post #185

Earlier quoted context omitted.

Since Windows Terminal application doesn't care about Concurrent DOS ever existing, and Windows Terminal Server is actually the Windows version of X Windows based on DirectX and grown out of Citrix networking protocol, they don't apply here.

Does Windows Terminal replace HyperTerminal too? Hadn't thought about that one in a while.

That thing died long ago and is completely unrelated.

Re: Windows Terminal Source Code

#193

Post by kevin_thibedeau »

pjmlp wrote: post #164
kevin_thibedeau wrote: post #155

Earlier quoted context omitted.

They emulate ANSI control sequences originally intended for dumb terminals and the teletype bell.

Which were never a thing in MS-DOS, Windows, OS/2, Amiga, Atari,...

ansi.sys would suggest otherwise.

Re: Windows Terminal Source Code

#194

Post by Liquid_Fire »

tmottabr wrote: post #181
justin66 wrote: post #166

Earlier quoted context omitted.

> in-house code may become virally GPL licensed Without reusing any of that code, simply by osmosis? I don't know what the legal theory could be, but is that something that has ever happened in the entire history of the GPL?

no, by writing similar \ equal code somewhere that later other people looking at it could argue is a re-use of the GPL code they looked at and thus causing the whole project to became GPL. it is just them thinking it is better being safe then sorry. if they don't even look at the code there is no way to argue that they are copying it.

Just a small correction/clarification - using GPL code inside a non-GPL project doesn't magically cause it to become GPL, it just means you would be committing copyright infringement if you distributed your project afterwards.

It's still something you want to avoid, but the outcome would potentially be a lawsuit from the copyright holder, rather than forcing you to relicense your project.

Re: Windows Terminal Source Code

#195

Post by zamadatix »

briHass wrote: post #167
zamadatix wrote: post #134

Earlier quoted context omitted.

The GitHub releases section has the msix installer package too. Terminal itself can't be runas but e.g. cmd.exe or pwsh.exe inside of it can be.

How do you get that to work? I've tried changing the settings to open new terminal windows using a different identity (runas), but they are then separate from the terminal app. I basically would just like to be able to dock that new window in the existing terminal tabs, as otherwise, I might as well just launch a PoSH prompt.

You can launch into any security context but merging multiple contexts under a single window is not supported. It has to do with Windows lacking session elevation for pipes but supporting it for window handles https://github.com/microsoft/terminal/blob/main/doc/Niksa.md...

If you want to get real hacky in the meantime you can run the ssh server service and have a short alias to ssh to localhost as a user but now you have that extra abstraction between to deal with.

Re: Windows Terminal Source Code

#196

Post by mattl »

pjmlp wrote: post #192
mattl wrote: post #187

Earlier quoted context omitted.

Does Windows Terminal replace HyperTerminal too? Hadn't thought about that one in a while.

That thing died long ago and is completely unrelated.

Wikipedia says Windows 10.. but that was the previous terminal emulator in Windows, right? There was MS-DOS prompt and then cmd in NT (4?) and HyperTerminal..

Re: Windows Terminal Source Code

#197

Post by xrayarx »

It shall be noted, that it does not work on Windows Server up to and including 2019.

I would also like to add, that I am puzzled, that Microsoft has not been able to deliver a proper shell, that is comparable to …sh and delivers remote access like ssh. Yes, Powershell, but not by a long shot. And for some things you still need cmd!

Re: Windows Terminal Source Code

#198

Post by shadowfox »

Maursault wrote: post #62
melony wrote: post #57

Earlier quoted context omitted.

Mac without the userland is mostly useless. At that point you might as well switch fully to FreeBSD.

This is a straw man, and also not entirely accurate. Darwin is BSD, and in theory just as useful as BSD, or FreeBSD, NetBSD, and useful to developers, and to anyone that can figure out how to install it and use it. [1] Meanwhile, Windows without hardware less than 2 years old is absolutely worthless. Thus, Linux. [1] http://www.puredarwin.org/

> Meanwhile, Windows without hardware less than 2 years old is absolutely worthless

This seems like a massive exaggeration. I am currently running Windows 10 on a refurbished laptop I bought in 2012! (So, actual hardware is even older).

Re: Windows Terminal Source Code

#199

Post by LocalH »

pjmlp wrote: post #164
kevin_thibedeau wrote: post #155

Earlier quoted context omitted.

They emulate ANSI control sequences originally intended for dumb terminals and the teletype bell.

Which were never a thing in MS-DOS, Windows, OS/2, Amiga, Atari,...

That's not true. MS-DOS and Amiga supported ANSI escape sequences, I remember that very clearly. Through MS-DOS, Windows and OS/2 would have had some form of support available. No clue about the ST

Re: Windows Terminal Source Code

#200

Post by a1369209993 »

ossusermivami wrote: post #162
a1369209993 wrote: post #128

Earlier quoted context omitted.

> as a software dev you know that soft anonymous telemetry of how a user use what you do is very valuable to make decision on how to make things.... No, actually, on account of being a software dev, I know that telemetry is actively counterproductive when making decisions on how to make things. It makes your decisions more wrong, not less.

would you care to explain why is this ? even as OSS software maker, would you start working on features because they are "cool" or a bunch of people yelling^H^Hasking for it on twitter?

> would you care to explain why is this?

I assume it's yet another case of the fallacy of revealed preferences.

If you look at what people actually do, any insight into what they want is confounded by environmental effects (eg, they'd prefer to use feature A, but feature A is missing or inconvenient to access, so they end up mostly using feature B), selection bias (feature A is most useful to precisely the people who know how to turn off or deliberately break telemetry), and other issues (A/B testing confirms that people have a revealed preference for clicking on animated icons (because they're trying to make the fucking thing stop squirming in their peripheral vision while they're trying to concentrate on something else)).

(Talking with users is definitely possible (usually easy) to screw up, but I have yet to encounter any evidence that it's possible to not screw up telemetry-based design decisions by any means other than ignoring the telemetry.)

Post reply on HN