narshe

5 ms·

1.
by narshe 11y ago
It's coming. https://github.com/Microsoft/vscode/wiki/Roadmap
2.
by narshe 11y ago
VSCode has no visual editor. Carmack has used Visual Studio for a long time. 2 references from the top of google results. There are many more out there. https://twitter.com/id_aa_carmack/status/21187594150 http:&
3.
by narshe 12y ago
That is going to be one expensive web browser.
4.
by narshe 13y ago
I worked at a place (but not on the team) where someone used the Ebonics ( http://en.wikipedia.org/wiki/African_American_Vernacular_Eng... ) version of Lorem Ipsum to fill in a large amount of text on the app. They forgo
5.
by narshe 13y ago
Yes, 64 bit would be nice. There are a lot of complexities that go along with that though. No plugins would work. There is a reason that browsers aren't 64 bit and flash will never be updated to 64 bit. It's possible, just a ton o
6.
by narshe 13y ago
Why combine? Because the server side infrastructure is a lot more flexible with MVC (than WebForms) and follows how HTML is supposed to work. If you're developing an API or service, use WebAPI instead. It solves most of the issues peop
7.
by narshe 13y ago
The reason it doesn't allow you to do JSON GET requests is because of the possibility of hijacking. http://haacked.com/archive/2009/06/24/json-hijacking.aspx Not allowing this by default is a good t
8.
by narshe 13y ago
I understand the complexity issue, and how large corps deal with that stuff... There are other ways you can chunk that stuff up though. Maybe you don't have a choice. I don't think you can fault Visual Studio for not handling that
9.
by narshe 13y ago
What do you need 34 assemblies for? Seriously?
10.
by narshe 13y ago
I think your issues are the reason there are other alternative frameworks that have come out; and there are a lot of them. Use one of the alternative .NET web frameworks if you don't like MVC proper. I'm not a fan a Razor either.