←back to thread

535 points raddad | 4 comments | | HN request time: 0.201s | source
Show context
typon ◴[] No.11389194[source]
This might be the most exciting news I've heard in a long time. Being able to use Visual Studio and .NET for web development while using zsh and all the other Linux tools? Dreamland.
replies(3): >>11389261 #>>11389399 #>>11389628 #
sfilipov ◴[] No.11389628[source]
The only reason I can't really use Windows as development OS are the inferior terminal emulators. As good as ConEmu is, it is still worse than Terminator etc. Unless I can run a native Linux terminal emulator, it doesn't make much of a difference to me. Also, the filesystem differences don't help.

I was also running into Haskell compilation problems that were fixed by running Ubuntu in a Vagrant environment but speed was slow. There isn't good NFS support on Windows either (there is some).

replies(2): >>11389712 #>>11390512 #
dogma1138 ◴[] No.11389712[source]
I would call powershell anything but inferior.
replies(2): >>11390030 #>>11390120 #
ljani ◴[] No.11390030[source]
I'm always put off by the ~five second startup time when I open PS to start learning it. Any tips for speeding it up?
replies(4): >>11390112 #>>11390258 #>>11390819 #>>11392608 #
1. adiabatty ◴[] No.11390819[source]
On my i5-2400 with 8 GB of RAM and a 7200 RPM hard drive, it takes six seconds to start the first time and four seconds to start subsequent times.

On my i5-3550 with 16 GB of RAM and an SSD it takes a couple seconds to start the first time and less than a second for subsequent times.

Both machines are running Windows 10.

Right now, the machine with the spinning rust is loading a bunch of files with an I/O priority of "background" because it just got booted into Windows; that might slow it down a bit because of the seek times and I don't know if Windows is willing to starve background I/O for seconds at a time to speed up interactive requests (I doubt it).

Update: once all the background preloading is done, PowerShell restarts in three seconds on the spinning-rust machine.

Long story short, I think getting an SSD will be the thing that makes PowerShell start acceptably fast.

replies(3): >>11391382 #>>11391749 #>>11391796 #
2. keithpeter ◴[] No.11391382[source]
Ancient Thinkpad dual-core with 512Mb RAM and 5400 legacy spinning rust disc running OpenBSD 5.9.

Left click in fwvm, select xterm, window appears in less than my blink response time.

Seriously: I think I might pop Win10 on an old Dell i5 that came with Win7 and play with this.

3. ljani ◴[] No.11391749[source]
Many thanks for the comparison! I'm indeed with a 7200 RPM disk. I guess I should invest into some new hardware soonish :)
4. JeffreySnover ◴[] No.11391796[source]
We did a lot of work on PowerShell startup in this next release - I think you'll be happy.

Jeffrey Snover [MSFT]