The Byte Stops Here

I was wondering if anyone has been using Git for a while, and can speak to working on a team where there is a lot of merging. What's been your experience like? Is Git mature enough?

I'm thinking of jumping ship from Subversion. While I had the same thought about a year ago, new merge functionality promised a lot in Subversion 1.6.

Unfortunately, I'm in the middle of a new development cycle where there is a ton of merging, and I have two words for Subversion: SLOW and STUPID. Subversion 1.6, unlike the SVNMERGE tool which I used for ages and worked like a charm, doesn't remember the previous merge. Its half-built. Its slow. And I've about had it.

I recently saw this video on Git. Its Linus Torvalds speaking at Google on Git, and while I have issues with some of the things he says, he's right-on when he says that SVN should have focused on merging, not branching.

Hopefully you guys can shed some lights on some of the specifics I need before I jump ship!

Joel Spolsky writes an excellent article/blog entry called "Capstone projects and time management". Its about a topic I'm very passionate about, and that is the teaching of Computer Science or Computer Information Systems at universities.Great read.

Read more @ http://www.joelonsoftware.com/items/2009/10/26.html.

We're looking for a Sr. Web Developer/ Technical Lead / Architect type person in Southern California.

You would be working on a ColdFusion-based SaaS web application. Its a very driven and dynamic company. I can't say enough! You will be working on a product that changes the lives of millions.

Obviously our application is built using best practices and a touch of practicality - Mach II, ColdSpring, and Reactor. We will probably be doing ColdBox in the future.

Read more about the company @ www.ecivis.com.

Feel free to leave a comment, and I can provide more details.

UPDATE: You can also email me at technology <at> ecivis.com.

C'mon, dude, how long have we known each other, like 5 and half years? (I love to create a little controversy, especially in times like these.)

But no, its nothing really, except that he stole my idea of comparing ColdBox with Mach II and Model Glue. Oh well, I'll continue with some other documentation about my experience with ColdBox.

Check out his great preso @ http://corfield.org/blog/index.cfm/do/blog.entry/entry/Comparing_Application_Frameworks_recording.

By now, you have probably had a chance to play with IE8. Couple things as developers to note:

First, if your website is having issues, add this meta tag while you figure out the problem.

<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

Next, if the problem persists, it may be related to code you put to purposely look for IE 7. Check those User Agent Strings.

For more details, see:

• http://blogs.msdn.com/mikeormond/archive/2008/09/25/ie-8-compatibility-meta-tags-http-headers-user-agent-strings-etc-etc.aspx
• http://www.microsoft.com/windows/internet-explorer/readiness/developers-new.aspx

I especially like this explanation by Microsoft from the 2nd link above.

Update your site to render in IE7 Mode

You may experience one of the following issues when you use Internet Explorer 8:

• Misaligned webpage layout

• Overlapping text or images

• JavaScript functionality issues and errors

These issues may occur because Internet Explorer 8 displays webpages using "Standards mode" by default, whereas most current webpages are created and tested to work with Internet Explorer 7 Standards mode.

Getting Internet Explorer 8 to always render a site or page like Internet Explorer 7 can be done by simply adding a tag. No additional changes are required.

There are two options for doing this:

1. On a per-site basis
   The site owner can add the HTTP header:
   
   <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7"/>
   

2. On a per-page basis
   The site owner can add a special HTML tag to each document, right after the tag:
   
   <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7"/>
   

The meta tag retains Internet Explorer 7 rendering behavior while still accessing all Internet Explorer 8 has to offer. This allows your site visitors who are using Internet Explorer 8 a seamless experience while you work behind the scenes to update your web properties. When your site is updated to render in Internet Explorer 8, you can remove the tag or continue to leverage the tag functionality, as it will remain as part of Internet Explorer 8 upon final release.

Note: Adding the Internet Explorer 7 compatibility tag should address most display issues. However, browser detection may also have to be updated on your site. To learn more, please read about the User-Agent String and Version Vector.

For more information on this specific meta tag update please see Some Web sites may not be displayed correctly or work correctly in Windows Internet Explorer 8. Other compatibility options are described in Internet Explorer Compatibility.