Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
No it's not but it shows where they are going if they even bother promoting it in the first place.
VS 2010
VS 11
They are about to launch new developers tool and they are talking about ****ing colours and pixel removals to supposedly make it good, there is no need for this tulip - keeping IDE familiar is far more important for productivity than engage in such whacko jacko ideas.
They are about to launch new developers tool and they are talking about ****ing colours and pixel removals to supposedly make it good, there is no need for this tulip - keeping IDE familiar is far more important for productivity than engage in such whacko jacko ideas.
They probably think software developers are good at coping with change. Just be glad it doesn't use the ribbon.
There's also a good deal of science behind use of colour - UX design is a proper field in its own right which is one thing the open-source community really needs to learn.
They probably think software developers are good at coping with change. Just be glad it doesn't use the ribbon.
WHS
I totally ****ing hate Ribbon tulip - made products from 2010 unuseable
Visual Studio team already made mistake in VS 2010 to use effing slow WPF just to prove it's ready for real world usage only to show that it's not and now they are going even further.
If it wasn't for new .NET CLR in it I would not even consider upgrading to that tulip, will have to get automated builds or something whilst still using VS 2008 for development.
Comment