LOL! Based on the .net developers I have worked with so far, I concur.
Example: The company I currently work for hired a ".NET Expert" to come help us get moving with our first .net project. On the first day, we were discussing data caching. .Net Expert: Put it in the asp.net cache object (like application scope in tomcat). Me: Well, what about data that is not global? It may vary by user. .NE: Put it in session scope ME: Can we cache it in the Data Access Layer? That way, it is not managed in the application. In Java, I would let iBATIS do it for me. .NE: Oh yeah, not a problem, we can have the DAL do the caching, easy, easy, easy. His solution: Pass the page object into the DAL when you create it, then it can do the caching using the asp.net cache objects. >blink< >blink< I had to leave the room to keep from throttling him. Larry On 6/30/05, Leon Rosenberg <[EMAIL PROTECTED]> wrote: > On Thu, 2005-06-30 at 08:48 -0400, Ed Griebel wrote: > > This is scary indeed. For Western NY, there's 2x .net jobs compared to > > plain Java, and 8x more .net than j2ee. > > > > However, consider that MS has marketed hard that any kind of > > development with Microsoft can now be tagged ".Net", which inflates > > the figures. At least that's my story :-) > > > Hehe, I think my story is better: The "so called" .net projects end in > disaster 8x more often then java projects, therefore they are in > continious recruitment to replace people they just fired... > > :-) > Leon > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
