|
What is wrong with posting this video link and how are most of the posts on this site, unlike Facebook? I don't use Facebook, so I wouldn't know.
|
|
|
|
|
Message Closed
modified 31-Jul-15 12:14pm.
|
|
|
|
|
How was that comment constructive? What point are you trying to make?
The video is pretty cool, even if it is old.
|
|
|
|
|
Well the reply was to another thread. Have no clue how it appeared here.
|
|
|
|
|
Context is everything, I guess. Thanks.
|
|
|
|
|
Such kids really keep their teachers on their toes!
|
|
|
|
|
So I started a new project at work.
We're still running on VS2010, but we were planning to upgrade with VS2015.
Just my luck that my project started pretty much on the release date of VS2015.
I was given a choice, go with all the new tech in VS2015 or stay in the jurassic 2010.
I choose 2015.
Piece of crap crashes randomly when typing some HTML and Knockout (in a Razor file).
I now find myself copy-pasting code to Notepad++, making my changes and copy-pasting it back into VS2015
|
|
|
|
|
Given the choice between latest and greatest and older tried and true, when it comes to IDEs I always go with something a little older. The bugs have been worked out and it's in a more solid state.
|
|
|
|
|
Yes! One generation behind, always... that is safe. I don't waste time (money) debugging their stuff. I let the early adopters do that for me. I'd rather finish my project and go home on time.
|
|
|
|
|
yep... I have enough work, I don't need to make more for myself
|
|
|
|
|
Indeed. I do the same with hardware as well.
|
|
|
|
|
|
Usually I'd agree, but 2010 is a little too tried and true.
I've worked with 2010 for five years and I love it, but I'm missing out on a lot of stuff that I'm using in 2013 (CE, privately).
I expected some issues with 2015, but not a constant crashing while typing plain old HTML (currently even Notepad does it better than VS2015!)...
I mean, this stuff was tested, right...?
|
|
|
|
|
Sander Rossel wrote: I mean, this stuff was tested, right...?
Good one!
I'd only take a newer IDE IF there are things that I'm missing that I need, otherwise, it's just not worth dealing with other people's bugs. Let someone else find them.
|
|
|
|
|
Sander Rossel wrote: I mean, this stuff was tested, right WTF do you think YOU are doing, haven't you reported the bug(s) yet, tcha you can't get good help these days!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
This was a long time ago, but the last time I was on a team that reported a compiler(!) bug to Microsoft, it didn't get fixed. After chasing the support person for a while, they finally admitted that they'd been able to confirm the bug, but had been told by the developers to back off because they were too busy getting the next release out to worry about our compiler bug.
We ended up having to work around their bug to get our release out.
Every time I'm tempted to report a bug to MS I remember that experience, and refrain from wasting my time.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
Sander Rossel wrote: I mean, this stuff was tested, right...?
By 'tested', if you mean 'Works on My Machine', then, yes, it was 'tested'.
I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone - Bjarne Stroustrup
The world is going to laugh at you anyway, might as well crack the 1st joke!
My code has no bugs, it runs exactly as it was written.
|
|
|
|
|
I've ported a moderately-sized C++ project to it (a C++-only version of WinFract); it seems stable so far.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
I recently moved from VS2010 to VS2013 - I would recommend VS2013, so far I have had no problems and it is a big improvement on 2010.
The beauty is that we can open 2010 projects in 2013 change them and then reopen them in 2010 if we want to(2013 does not 'convert' the project to 2013).
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Yeah, 2013 is great. I use the Community Edition for private stuff.
Unfortunately that wasn't an option at work, so I got to pick 2010 or 2015.
2010 was a bit to old for my taste. Been using it for five years and I love it, but I'm missing out on good stuff that's in 2013.
So I decided to go for 2015, but I didn't expect it to fail as even a simple HTML editor...
|
|
|
|
|
What's the good stuff in 2013? I'm stuck with 2010 and haven't played with anything new in a while.
|
|
|
|
|
I couldn't say right from the top of my head.
It's just a better overall experience.
I guess intellisense for HTML and JavaScript is a lot better.
Editor just works a bit better.
There's a few new options.
I'm sure you can find some articles comparing version x to version y though.
Funny how I like 2013, but I can't really say why
|
|
|
|
|
|
The two big things that made a difference are:
The ability to select a dark theme so that I can have the background in black - takes me back to my speccy days .
Secondly the ALt-F12 funtionality to peak at a method - it opens a second small split screen under your selection and even allows you to amend the original method. This second ability is a huge time saver where in 2010 you had to navigate away to look at a method you can now see it directly under your code.
There are probably lots of other useful features however these two are the two that have so far helped me the most.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Thanks! Unfortunately, I'll probably be stuck going with 2015 when/if I get to upgrade.
|
|
|
|