Web Development

Google Chrome arrived yesterday as a Windows beta with a comic explaining multi-process tabs and a reputation for speed. Another browser is the last thing some people wanted. For web developers and security folks, it is a big signal: the rendering engine wars are back. Mac and Linux versions do not exist yet. This is a Windows-only beta — but the design choices are worth studying regardless of platform. What Is Different Separate processes per tab — one crash does not take down everything Sandboxing ambitions — harder for web content to touch the system V8 JavaScript engine — fast enough to change how web apps feel in the browser Minimal UI — the address bar doubles as search, fitting Google’s habits Incognito mode — private browsing without digging through menus Silent auto-update — patches ship without a user-facing version bump Chrome uses WebKit for rendering — the same engine family as Safari — with Google’s own V8 replacing JavaScriptCore for script execution. ...

By late 2007, a lot of “enterprise” work still happens on small internal web apps: timesheets, inventory lookups, simple ticketing, phone directories. You do not always need Java or .NET. Sometimes you need PHP, MySQL, and a Windows server that the IT team can actually maintain. That is common in broadcasting, education, and mid-size offices — anywhere IT support sits close to the users and budgets are tight. Why Internal Tools Matter Desktop apps are expensive to deploy. Browser tools win when: ...

My first websites did not start in a text editor. They started with Microsoft FrontPage 2003, CoffeeCup HTML Editor, and a lot of trial and error in Internet Explorer 6. That was normal in the early 2000s: visual editors lowered the barrier, and the web was still small enough that a personal page or a company brochure site could ship in a weekend. By November 2004, the tools are better — but the habits matter more than the brand on the box. ...