Yeah, I know the syntax is different, and I think you're right across the board. But I guess I kind of see it as just the next iteration of the old Web Pages w/

Yeah, I know the syntax is different, and I think you're right across the board. But I guess I kind of see it as just the next iteration of the old Web Pages w/ Razor functionality, just with better support for external models/code-behind, but also more package dependencies. .NET Core definitely seems to be off to a great start, and once the tooling gets better I think I'll use it much more (EF support via VS is lacking, especially if you're trying to update a model going db-first). So if the future of .NET is .NET Core first, I look forward to continuing to be a .NET developer.