4 ms·
You're thinking about the problem wrong. You want the best language/framework for the job. If you think this idea is going to be "big", then you need to think
by jawngee 17y ago
You're thinking about the problem wrong.
You want the best language/framework for the job. If you think this idea is going to be "big", then you need to think about what tools are going to support this "big" idea best, not what is going to make you more comfortable. Satisfying your laziness(comfort) is not necessarily going to satisfy getting the problem solved in the quickest and most scalable way possible (scalable in terms of cost outlay as well as potential performance).
The fact that you think ASP.NET is beautiful is worrisome, I have to say. That you think it is MVC in some way is troublesome as well.
- ComputerGuru 17y agoThe "beautiful" part of ASP.NET is the C# and the .NET framework itself... what I meant to say is I love the language and abhor the webforms :) I don't think it's lazy to look for the hammer that fits best in your hand.... after all, if the hammer is too big for you to carry or too small for you to handle, it doesn't matter how well-fit for the job it is because to the holder it's quite useless :)