Oh, and it should have a nice menu system for doing things related to the site when on a page.
Oh, and it should respond to the device and browser of the person using it, with the layout and functionality adjusting accordingly.
Oh, and the images should be the appropriate size for that device, because we don't want users on cellular networks to have to download large images.
Oh, and it should display for them in their preferred language. And without having to choose the language from a menu. Don't tell me about this internationali-whatsit and local-whoozits, I said it should display in their language! (God, you developers are annoying.)
Oh, and it should mirror the smoothness of the native applications of the user's device.
Oh, and it should be built on roughly the same technologies which websites have been using for the last 15 years. And I don't want to hear about "HTML is a system for describing documents, not applications" or "CSS is for styling documents, it's not a layout engine".
Yeah, you know, jeez, why is this so hard????? Everyone is stupid and in my way.
Coming up with an algorithm is not hard. It is just time consuming and annoying because brute force is stupid to people. So, gluing code in some brain dead fashion (wtf do I do here? Oh no better solution so I will patch this patch that with stitches) is hard because it is like brutcing. There are too many "libraries" and none can do everything easily. Complex system is the end result. Then engineers spend most of their time reducing the complexity. If there was a framework that could reduce in the first stage then it is easier, not harder.
Comments
All I want to do is build a website!
Oh, and it should have a nice menu system for doing things related to the site when on a page.
Oh, and it should respond to the device and browser of the person using it, with the layout and functionality adjusting accordingly.
Oh, and the images should be the appropriate size for that device, because we don't want users on cellular networks to have to download large images.
Oh, and it should display for them in their preferred language. And without having to choose the language from a menu. Don't tell me about this internationali-whatsit and local-whoozits, I said it should display in their language! (God, you developers are annoying.)
Oh, and it should mirror the smoothness of the native applications of the user's device.
Oh, and it should be built on roughly the same technologies which websites have been using for the last 15 years. And I don't want to hear about "HTML is a system for describing documents, not applications" or "CSS is for styling documents, it's not a layout engine".
Yeah, you know, jeez, why is this so hard????? Everyone is stupid and in my way.
?? where is my queue, my asynchronous library, my database exception handler, my security check, my cache database, my socket sub/pub.
OMG. HOW THE HELL DO I BUILD A WEBSITE?
Nightmare. Hence why I rather build tool that runs over command line than building an actual website. It is damn hard.
I don't think I would call writing a bunch of glue code hard. Annoying and time consuming perhaps, but "hard"? Nah, not often.
Coming up with an algorithm is not hard. It is just time consuming and annoying because brute force is stupid to people. So, gluing code in some brain dead fashion (wtf do I do here? Oh no better solution so I will patch this patch that with stitches) is hard because it is like brutcing. There are too many "libraries" and none can do everything easily. Complex system is the end result. Then engineers spend most of their time reducing the complexity. If there was a framework that could reduce in the first stage then it is easier, not harder.