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

Looking Forward: Support for Secure Shell

blogs.msdn.com

Post reply on HN
Print view View original

201–210 of 404 posts

Re: Looking Forward: Support for Secure Shell

#201

Post by pjc50 »

matthewmacleod wrote: post #173
WorldWideWayne wrote: post #160

Earlier quoted context omitted.

Supporting developers means making their lives easy by giving them streamlined systems and frameworks, not throwing a hodge-podge of of command line utilities at them or exposing them to the messy bazaar of the FOSS world. I'd say Microsoft has been been more pro-developer than most and I'm super glad that I chose to live primarily in their ecosystem because they make my life easy compared to the mess I have to put u…

I would say that's a minority view at best. There are two worlds in desktop software development – the "open-source-unix-y" world, and the "Microsoft" world. The former has typically meant having a broad range of excellent tooling; it's certainly been a bit messy, but that's mostly because of the ease with which things have been able to change and develop. Even development in the Apple sphere has always involved the…

The dichotomy has long been "large number of single-purpose tools that can be combined" versus "single monolith that could theoretically be scripted but rarely is". The monolithic system doesn't have to worry about mismatches, seams and fragmentation, but is also brittle.

Re: Looking Forward: Support for Secure Shell

#202

Post by 72deluxe »

jadeddrag wrote: post #3

I'm looking forward to MS just dropping their OS entirely and using linux as their back-end. Basically, Microsoft might be better off creating their own linux distribution running a "microsoft windows" windows manager.

But you'd have no backwards compatibility. No software would run. You'd have to use systemd and be subject to the infighting in the Linux world, with short-lived projects and the CADT development model that appears to exist there. At least with Windows you can still write in the classic Windows API and it'll still work.

Your comments is naive, I feel?

Re: Looking Forward: Support for Secure Shell

#203

Post by dragonwriter »

sangnoir wrote: post #159
nogridbag wrote: post #80

Earlier quoted context omitted.

I believe they also have Windows 10 Enterprise, Windows 10 education and if we include the phone OS: Windows 10 mobile and Windows 10 mobile enterprise.

This is correct - there are 6 Windows 10 SKUs[1]. 4 if you exclude the mobile SKUs. The "only 2 SKUs" was just a rumour/wish. I'm echoing speculation I read elsewhere: the reason for the numerous versions is Federal Money. The US government demands that it pays the lowest price the vendors offers an item for. Since Microsoft likes to offer discounts to universities, the government would be entitled to the lowest disc…

> The "only 2 SKUs" was just a rumour/wish.

Its only two consumer-facing desktop SKUs, but that's the same as Win 8.1. Its still down from Win 7, though.

Re: Looking Forward: Support for Secure Shell

#204

Post by jfuhrman »

digler999 wrote: post #165
wumbernang wrote: post #144

Earlier quoted context omitted.

Couldn't agree more. As a die hard Unix guy and ex Slashdot-esque zealot (colloquially a bit of a twat). Yet I'm knocking out PowerShell all the time now and dread having to log into the pile of CentOS kit I have lying around. It is arcane. Even after 15 years I spend most of my time in the manpages or working out another damn config format. Literally did a two liner to scrape a web page, parse it and call a REST end…

> The only thing I still hate is windows update. all those "2 liners" don't mean much if you have to reboot your box every 2 days to apply more emergency 0-day security patches.

What platform does not have 0-day security vulnerabilities? Hurd?

Re: Looking Forward: Support for Secure Shell

#205

Post by 72deluxe »

talideon wrote: post #59
jadeddrag wrote: post #3

I'm looking forward to MS just dropping their OS entirely and using linux as their back-end. Basically, Microsoft might be better off creating their own linux distribution running a "microsoft windows" windows manager.

Come back to us when you've found a way to implement the good stuff that Windows has, such as IOCPs: https://msdn.microsoft.com/en-us/library/windows/desktop/aa3... And no, epoll isn't enough.

Or still-supported DDE, COM program embedding, easy-to-configure ODBC etc. etc. etc.

Re: Looking Forward: Support for Secure Shell

#207

Post by jfuhrman »

wumbernang wrote: post #144
halo wrote: post #128

Earlier quoted context omitted.

>Wishlist: tmux, emacs, vi, netcat, shell option for vi-mode, rc-file with preferences, ncurses library, something simpler than curses, zip and unzip No thankyou. I can certainly understand including SSH support, but I don't want what is pretty much the only remaining viable non-Unix platform to start bundling horribly dated and clunky Unix-like commands and bloated GNU tools.

Couldn't agree more. As a die hard Unix guy and ex Slashdot-esque zealot (colloquially a bit of a twat). Yet I'm knocking out PowerShell all the time now and dread having to log into the pile of CentOS kit I have lying around. It is arcane. Even after 15 years I spend most of my time in the manpages or working out another damn config format. Literally did a two liner to scrape a web page, parse it and call a REST end…

>two liner to scrape a web page, parse it and call a REST endpoint with the parsed data as JSON in PowerShell

Can you post this 2 liner? Sounds interesting.

Re: Looking Forward: Support for Secure Shell

#208

Post by wumbernang »

currysausage wrote: post #169
wumbernang wrote: post #144

Earlier quoted context omitted.

Couldn't agree more. As a die hard Unix guy and ex Slashdot-esque zealot (colloquially a bit of a twat). Yet I'm knocking out PowerShell all the time now and dread having to log into the pile of CentOS kit I have lying around. It is arcane. Even after 15 years I spend most of my time in the manpages or working out another damn config format. Literally did a two liner to scrape a web page, parse it and call a REST end…

> Literally did a two liner to scrape a web page, parse it and call a REST endpoint with the parsed data as JSON in PowerShell. This sounds cool. Can you recommend terse resources for getting to know PowerShell? Is MSDN the best place to look for docs or are there better places to go?

TBH I couldn't find a decent book or resource and sort of hacked my way around for a year or so. It had a good build in manual (get-help). This is a good poke at the fundamentals of my example:

Scrape a page:

   $flight = " LH3396"
   $url = "http://bing.com?q=flight status for $flight"
   $result = Invoke-WebRequest $url
   $elements = $result.AllElements | Where Class -eq "ans" | Select -First 1 -ExpandProperty innerText
Hit a REST endpoint:

   $body = @{
       Name = "So long and thanks for all the fish"
   }

   Invoke-RestMethod -Method Post -Uri "$resource\new" -Body (ConvertTo-Json $body) -Header @{"X-ApiKey"=$apiKey}
Sources:

[1] http://stackoverflow.com/questions/9053573/powershell-html-p...

[2] http://www.lavinski.me/calling-a-rest-json-api-with-powershe...

Post reply on HN