Yup. That's it. Be done. In the spirit of the new rule, I'm just going to go with Eclipse. My prior exposure to it and lack of exposure to anything else for Java programming lends itself to an immediate decision. The tradeoff? IntelliJ, which might be a perfectly wonderful IDE, costs money. I don't want to buy an IDE. NetBeans, while free, doesn't seem to have half the add on tools that Eclipse does.
Decision made. There is still a mountain to learn. What is the Nuget analog in the Eclipse world. As best as I can tell, it's Maven, but talk about a god awful tool compared to the simplicity of managing Nuget packages in Visual Studio. This doesn't mean Maven is a bad tool. On the contrary, it means I'm a lazy neophyte (Total NOOB) in the land of Not Microsoft.
I have two goals that I need to meet in rapid order: Rebuild TesterCraft.com using Eclipse and Create a Selenium testing framework in Eclipse.
Blips on my radar: stuff I'll probably get to, but I'm just not there yet.
- What the heck is Jenkins?
- Protractor