Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Comment Re:Why bother? (Score 1) 421

Fair enough. With MEB 2014, I sent genuitec a few nastygrams over their decision to punt on SVN support. I'm there with you. But I did get it to work well and you can always use Tortoise--that's what my team uses. Do you do a commit every 15 minutes?

As for your troubles with WebSphere--well, that pig is something I have been able to jettison many times for all the alternatives so if you're still stuck with WebSphere you have your own set of problems.

Also, frankly, I think you are being sandbagged if people can claim that 25% of their time daily is waiting for MEB. I think, frankly, that has to be bullshit--they are exaggerating.

Also, if you have to leave MEB, then there is the fabulous free Spring Tool Suite which does lots of what MEB does. I understand that, technically, .NET can connect to any database vendor's driver. But you also know that when you're in a MS shop you end up--because of support and tools such a VS--end up being a 100% MS shop. It just happens. I doubt MSDN is going to give you oodles of pointers on how to configure .NET and solve esoteric problems on Postgres, MySQL or Oracle. It's not in their best interest to support the competition. So, bottom line, the decision to become an MS shop is a higher cost point and so fewer and fewer shops are choosing that. I look back on my decision in 1999 to become a Java fiend as the best decision I ever made and I stand by that assessment to this day. The last product I worked professionally on that came from Microsoft was VB6 and it constantly fucked up. Certainly, your mileage may vary but I have found my salary spiraling up and up without end because I know Java and the JEE ecosystem and its many open-sourced brethren so well.

Comment Re:Why bother? (Score 1) 421

Rick, I just upgrade my team to MyEclipse 2015 and we have not had any problems. What problems did you see?

As for database connections and the price of any given database, I consider that orthogonal to this discussion, as you can in the Java world choose to use any DB you like, including SQL Server.

My experience--albeit limited--in the .NET space is that Microsoft tools have an affinity for Microsoft-built comrades. If I'm not mistaken, I believe Sharepoint requires SQL Server.

Comment Re: Why bother? (Score 1) 421

If you need help getting some counseling, I'm here for you.

Denial is a tough row to hoe but I'm sure, with therapy, you can make the transition to another language. There's always PHP or Python if the thought of finally breaking down and learning Java is too painful for you. Or perhaps Go or Hack might offer an easier transition for you...

Comment Re:Why bother? (Score 1) 421

I understand all about Mono but the monkey is still, after three major versions, missing huge chunks of what .NET purports to do, such as complete support for WF 2.0 and any real support for WPF. I understand what a pain it must be to work against the beast from Redmond with the monkey but you know as well as the rest of us that in Mono you are working on another Symbian.

Neutrinos are into physicists.