programming chelahmy

I registered a new domain name. While in the process of registration I checked on the new domain name that showed a default page. I should have not done it in the first place checking on a site with incomplete domain name registration. Once the registration was completed I pointed the new domain name to my web server. And I created a new "Hello World" page. However, the new page didn't show up on a browser on my laptop. However, it showed up on my smartphone. And it showed up on my son's smartphone. It just didn't show up on my laptop. It showed the original default page instead. After a few trials the default page became very suspicious to me. Searches on the Internet pointed to a potential browser malware. And I spent a few hours hunting for the malware that eventually never existed. I looked up using a different browser and I made a query using curl . All responded with the same suspicious default page. Thus, it had nothing to do with the browsers or their

Separation of concerns is the cornerstone of MVC framework. Model, view and controller are three broad concerns of web-based software development. On its early days MVC was implemented on server side. The server renders views for clients. Nowadays, most clients render views themselves. Even the terminology of client-server has already morphed into front-end and back-end . The need for back-end to handle views is diminishing. View concerns have became increasingly complex with two big sub-concerns of aesthetic and dynamics. Front-end evolves into bigger MVC concerns of itself. While back-end evolves into larger modeling concerns. Now, front-end and back-end are two separate concerns. Front-end and back-end are handled by two different teams of software developers with different specialties. Back-end evolves into something like "dinner can be served even without plates, forks and spoons, without table and chairs, and without a dinning room." Front-end is serving the withouts.