HN user

ctolkien

54 karma
Posts0
Comments26
View on HN
No posts found.

I read it as "we will be adding features that make sense for VB (which might also make sense for C#), rather than keeping it in sync with C#".

Allowing it to evolve on it's own, rather than being C#'s ugly little brother.

ThinkPad X1 Carbon 10 years ago

Picked up my SurfaceBook the day they were launched - there were definitely teething issues, sometimes the detaching process would fail, there were sleep issues (not sure if Intel cops the blame for that one).

All of these issues have been resolved with firmware updates by about 3 months after launch - reliability has been rock solid from then on out. Can't recommend it enough.

Much like the real world and real people, there's no guarantee that the most popular concepts will be technically correct.

MacBook Pro 10 years ago

I've a SurfaceBook, I didn't think I'd use the touchscreen at all when in regular "laptop" mode. I end up using it _all the time_. It really is super intuitive to just reach up and touch the screen.

Project.json is getting pitched, but until the successor arrives, it's still the only way to do .Net Core dev.

Can you do this in Powershell quickly? I don't know, I am actually curious.

You can basically do the same thing with Powershell. I don't know of a 'built-in' module to handle XLS->CSV conversion, so you need to bring one in:

  Install-Module ImportExcel
Then:
  ls *.xlsx -r | %{ Import-excel $_ } | ? { $_.Name -eq "Miller" } | sort
That's my naive, Powershell noob approach anyway.

There's another option however, where you can leverage Excel itself (granted, this is likely to be a Windows only approach):

  $excel = New-Object -com excel.application
And you can now open XLS/XLSX files and operate on them as an actual excel document (including iterating through workbooks/ worksheets, etc.). It's all just objects.

Omnisharp existed as a community project well before VS Code. It's great to see MS adopt and build on it.

Eh, I like the Powershell angle here. By default everything is named in lengthy, self explaining names, but there's shorthand aliases for everything.

In reality, no one is using `get-childitem` instead of `ls` or `dir` (both of which are simply aliases for `get-childitem`).

Not really arguing against your point - however when in Powershell, as everything is an object, you don't end up using the same "string heavy" techniques that required grep with more traditional shells.

You don't need ReSharper, you can step into the core .Net libs from Visual Studio and it will download what's required.

If you want to step into the source code of other projects however, I don't think that scenario is handled yet. Perhaps a feature to be added to NuGet.