unicron

You've obviously never dealt with ancient IE versions and script loading then...

It's 100% not true. It's also a pain in the arse if you serve everything over SSL like we do.

That is learning to build web applications. It is different to learning to code.

It would still be no good. If you drop one, it's dead. If you drop a Barclays PDQ, you pick it up and continue the transaction.

It's a very complicated application with a huge amount of HTTP endpoints. We're talking over a million lines of code.

I agree entirely with this approach.

Especially when I consider that we're delivering a 350KiB minified Javascript hit on initial load just for jquery and a load of plugins.

This is a gimmick or a hack. Not much better than what you will see on hackaday.com

I did a LOT of POS work a few years ago for small businesses. An iPad/iPhone would be dead and broken in less than a month for most retailers. You need pretty hard wearing industrial grade kit if you don't want to throw it away 3 times a year. That flimsy card reader is almost comedic - you'll break it and your device.

If it's your revenue collection equipment, it makes sense to buy something that will last i.e. was designed for the job rather than sit there not being able to take cards.

That appears to be standard practice for "model bound" systems where the internal "domain model" is bound directly to the HTTP protocol. You get this issue with ASP.Net MVC as well on most of the trivially implemented projects out there.

This is not really a "framework bug" as such. It's just crap application architecture.

At the core of this issue is a simple misunderstanding on what the "model" part of MVC actually is. The model represents ONLY the request or "form model", not the data model. There should be a mapping of 1:1 between the request and the "form data model" always with no exception. The controller is responsible for translating that into something useful or doing something with it involving the domain/data model.

Unfortunately where the usual CRUD approach is required, ignorance reigns supreme and the shortest path, not the most correct path tends to appear.

I write this as someone who works on a rather large ASP.Net MVC application (100+ controllers) and has seen this many times already.

Can you please allow us to get a sample of what we're going to get before we have to enroll.