Devices we worked with for a project (thankfully not on GCP) are welded shut once built. They are designed to run for years on an internal battery then need to be recycled. They would all be paperweights in this scenario!
HN user
ctolkien
Still rocking my 3770K here too - that thing is rock solid.
MS has x86 working on ARM however: http://www.zdnet.com/article/microsofts-x86-on-arm64-emulati...
This telemetry is tracking the `dotnet` commands used (i.e, how the CLI tool is used).
https://blogs.windows.com/windowsexperience/2017/07/24/ms-pa...
Paint isn't going anywhere.
45% off currently.
Was ~$19 AUD ($14 USD)
They are position this for use in script sharing.
You might have a nix shell script, using a bunch of traditional GNU tools which does some "stuff" - you can now consolidate that workload onto a Windows Server.
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.
Yes, we launched our start up on ASP.NET Core - https://www.comparelearning.com.au/
(We're based out of Sydney Australia - not SF).
Overall, it was a positive experience and I think even with the current warts (in particular around tooling), it's a nicer stack than MVC5.
I blogged about some things we learned here: https://chad.tolkien.id.au/lessons-learnt-going-into-product...
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.
Did not know this, thanks.
I used Chrome on Windows and iOS
Chrome on IOS is really Safari under the covers.
Much like the real world and real people, there's no guarantee that the most popular concepts will be technically correct.
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.
Yes, the store is just one distribution model. The web, or whatever is also fine.
Not true. The -r flag I specified is for "recurse", will search current and all sub-directories.
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.If you're referring to the telemetry in Win10, similar telemetry was patched into Win7 a long time ago.
Omnisharp existed as a community project well before VS Code. It's great to see MS adopt and build on it.
V2 is currently in beta.
In the coming weeks, a more stable release candidate will be coming out, with the final product landing not too far after.
-- https://blogs.msdn.microsoft.com/typescript/2016/07/11/annou...
I found it really clunky. I wanted a thing, and it made me wait nearly two days to get that thing
That "thing" isn't officially released yet, hence the hoops.
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.