|
No, as a language implies keywords and grammer/syntax. Headless clucking is more akin to the language of politicians than of sailors.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
I swan to flip you the bird for that one but I would just duck it up and raise the wrong (chicken) finger.
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
|
|
|
|
|
I feel that I must balk balk balk at making such ostrich of the imagination.
|
|
|
|
|
Only because everything else tastes like them.
Software Zen: delete this;
|
|
|
|
|
Only when crossing the road.
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
MVC - does anyone actually like it?
The phrase "Sledgehammer to crack a nut" comes to mind.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Imagine using the same processes to build a doll house that the architects and builders of skyscrapers use.
On the other hand imagine a skyscraper construction company using the same processes that a doll house builder uses?
You'd never step foot in that skyscraper.
And that is what is being done with so many projects like Facebook (built on PHP and bad processes).
Doll house builders should not use skyscraper techniques and vice versa too!
|
|
|
|
|
How often does the Doll House get used as a Skyscraper?
"Well Jim, this Doll House is fantastic. Make a enough to stick in 1000 people."
|
|
|
|
|
maze3 wrote: How often does the Doll House get used as a Skyscraper?
Every time a developer utters the words;
"Now this is just a proof of concept..."
|
|
|
|
|
F-ES Sitecore wrote: Now this is just a proof of concept..."
Exactly!
Every prototype is the product.
|
|
|
|
|
Seriously: Many years ago, an IBM salesman told me that when they used their very fancy tool for prototyping user interfaces, with surprisingly functional back end stub functions, they had orders from above to always leave out at least one essential function from the prototype.
The mock-up prototype was so good that several times the customer had been so satisfied with the mock-up that he said: Great, I'll take that one! - unwilling to pay for the work of developing "the real thing". But if it was fully functional, why not let them have it? Much because the demo was run at a huge mainframe, interpreting APL code. A small toy house thing runs with good enough performance, but it doesn't scale.
I really hate those projects that develop from prototype mock-ups that grow cancer and becomes completely unwieldy, because no proper future-friendly, scalable implementation architecture was ever drawn up. The prototype was created to get a go-ahead; that takes quite different qualities that a long-term architecture.
So if you consider me somewhat sceptical to the "agile" approach, there may be a grain fo truth to it
|
|
|
|
|
Got any tip on how I can explain that to my boss? Developer became manager trying to micromanage everything not getting me being a fan of "The right tool for the job" including "Process complexity dependent on the result complexity".
|
|
|
|
|
Forogar wrote: does anyone actually like it? I don't dislike it. It works great for what I need. Maybe you aren't familiar enough with it?
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
If you mean "Marvel Vs Capcom" then yes!
|
|
|
|
|
Yes.
But then only when appropriate, not as a silver bullet. Knowing a design-pattern means that you can also identify the places where you don't need it.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Didn't you know MVC stands for "Malformed Vulgar Coding"
Definitely dislike it !
|
|
|
|
|
The design pattern or Microsoft's framework?
|
|
|
|
|
Nish Nishant wrote: The design pattern or Microsoft's framework?
This is the best reply/question to the OP because :
1. MVC the pattern doesn't make anything more difficult. It could even be considered the beginning of OOP -- since if you think MVC (the pattern) makes things difficult you probably don't understand anything about OOP.
2. MVC (Microsoft's ASP.NET Framework) does have a bit of complexity but that is actually more related to all the technologies that you have to swallow in one bite. As soon as you create a ASP.NET MVC you get the MVC pattern plus, jQuery, Bootstrap, JavaScript, C#, CSS, Bundling and Minifying and other things thrown at you and so then yes some people feel overwhelmed.
|
|
|
|
|
Absolutely, along with most of the various permutations (MVP, MVVM...).
Unless you mean MVC.NET and Razor, in which case not so much.
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
Actually, I love it. From when I first learned Castle Monorail 15 years ago, my first thought was " This is the way my brain thinks"
I find webforms much more sledge-hammery.
Truth,
James
|
|
|
|
|
I converted to Microsoft's framework years ago. I believe it was still alpha, at the time. I absolutely love it. I was also trained on Java Servlet Pages in school and these used the MVC pattern and I quite like those. I have developed WebForms applications and WinForm applications as well. MVC, in any form, is a tool and you have to understand how, and where, to use it. For the vast majority of my development, it is the perfect tool. The conversion from WebForms took a bit, but once I invested the time I wouldn't return to WebForms unless I had to.
|
|
|
|
|
Quote: I was also trained aaah! There's the rub!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
if you are referring to Microsoft's MVC.Net I love it.
It took a while for me to switch from webforms, the design pattern and extras (like routing, minifying, jquery, etc..) that get included in the starter template could be overwhelming but once I got the gist of it I never wanted to go back to webforms
It plays very nice in my mind with Xamarin, as the structure and design of an app and a webapp seem very familiar and correlate to each other
|
|
|
|
|
I enjoy working using MVC for my projects.
What I do not like is all of the overhead of the templates, so I will stick to developing as a SOC project that may vary within as the needs and refinements are built. One page could be MVC and another could be MVVM. Heck, my last MVC CMS actually utilizes a straight ASPX page complete with code-behind.
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
|
|
|
|
|
I have used MVC for straightforward projects but I have to say that it can become too complicated for some applications. In these cases a good mix of javascript and json does the job a lot better than MVC or some of the other frameworks (Xamarin. I'm thinking about you...)
I'm a great believer in the KISS principle.
We're philosophical about power outages here. A.C. come, A.C. go.
|
|
|
|