I can understand avoiding the grim truth by denying that the problem has truly been solved by ~700 lines of C. I believe I'd feel embarrassed and defensive too if something I'd worked on turned out to be flawed in a painfully obvious way.
NEW WINDOWS TERMINAL REDDIT SOFTWARE
However, it's my contention that this incident is primarily about the latter.Ĭasey, rightly, already had some pent up rage about the former asymmetry as well.īut it was a human manager/dev? within that small team, not Microsoft writ large, that got defensive about the software he was responsible for. I don't disagree that the former is abusive. a 3-4 man open source team within microsoft The person that quit the project (and possibly the internet at large) wasn't a microsoft employee. What this guy did might discourage participation and make folks more defensive to avoid losing face in a big public way over a mistake or silly gotch-ya. They've helped me and many others out, it has been genuinely refreshing. I have found the Microsoft folks to be very helpful and generous with their attention on Github Issues. It's not so nice when this stuff is very public with harsh judgement all around. I think it was counterproductive at best and rather mean at worst.Īs for whether it really is "difficult", one has to ask for whom? For someone that is intimately familiar with C++, DirectX, internationalization, the nature of production-grade terminal shell applications and all their features and requirements?Īnd even if it is "easy", so what? It just means Microsoft missed something and perhaps were kind of embarrassed, that's totally human, it happens. That said, he did literally admit he was being "terse". Now that you have enabled telnet you should be able to start issuing commands with it and using it to troubleshoot TCP connectivity problems.Whether or not you see his behavior as polite, I guess, is a matter of how you read people and the context of the situation. In some cases you must run command prompt or powershell as administrator in order to issue the telnet command, otherwise it will give the same error as if it was not enabled at all. If this was successful you should have a prompt similar to the below: Welcome to Microsoft Telnet ClientĪlready have telnet installed but still failing? Simply open command prompt or powershell, type ‘telnet’ and press enter. Verifying that the telnet client is enabled When complete it will display as below, you can now close the window.Click the OK button to proceed, this will display a screen while the changes apply.The “Turn Windows Features on or off” window should open, scroll down and select “Telnet Client”.Click the start button, then start typing “Turn Windows features on or off”, and select this option, as shown below.Enabling the telnet client through the graphical user interface That’s it, after a few seconds telnet should be ready to use. dism /online /Enable-Feature /FeatureName:TelnetClient Run the below command in command prompt with administrator permissions.
You can enable the client either by command line or through the graphical interface.Įnabling the telnet client through command line 'telnet' is not recognized as an internal or external command, operable program or batch file.
NEW WINDOWS TERMINAL REDDIT UPDATE
Update October 21st 2015: I have also created a video showing the process:įirstly you need to enable the telnet client, if you don’t enable it you’ll get a result similar to the below message when trying to use it. With telnet we can get a better understanding of what’s going on. It may be that the connectivity is fine but there is a problem with the web server, or that the web server is stopped and the port is not listening at all, for instance. This is great when you’re trying to troubleshoot network connectivity problems, for example, say we have a web server which should be listening on port 80 to serve HTTP traffic but we are not able to load a web page, by using telnet to connect to the web server on port 80 we can verify the connectivity. By default the telnet client in Microsoft’s Windows operating systems is disabled, this is unfortunate as it is an extremely useful tool which can be used for testing TCP connectivity to external hosts on a specified port.
0 kommentar(er)
