News for hackers. Stuff that matters.
Re:The sorry state of Visual Studio syntax highlighting (2012) by rwallace on Sunday March 02, 2014 @05:31AM (#7328615)
What the hell makes you think your dislike of the Visual Studio syntax highlighting system makes it okay to be so bloody rude? Would you be happy if everybody who disliked your work said "fuck you, ulam2"?

I'm not saying that sort of language is never appropriate - it's a fair response to patent lawsuits, for example. But let's keep feedback on user interface issues a bit more civilized.

Re:The sorry state of Visual Studio syntax highlighting (2012) by koobarbara on Sunday March 02, 2014 @07:12AM (#7328855)
Because it helps fishing views, obviously
Re:The sorry state of Visual Studio syntax highlighting (2012) by ulam2 on Sunday March 02, 2014 @05:46AM (#7328653)
i am here to share my opinion.
Re:The sorry state of Visual Studio syntax highlighting (2012) by chucknelson on Sunday March 02, 2014 @05:30AM (#7328611)
I know, pointless comment, but some syntax highlighting issues hardly seem worth a "fuck you". Article title would be much better without that.
Re:The sorry state of Visual Studio syntax highlighting (2012) by wila on Sunday March 02, 2014 @05:40AM (#7328633)
Post is from 2012, but still it is weird to be so inflammatory about the inabilities of customizing a specific part of syntax highlighting.

Unless you have actually written syntax highlighting code parsers yourself better as what is in Visual Studio I am of the opinion you do not have any rights to be that rude.

Re:The sorry state of Visual Studio syntax highlighting (2012) by seanmcdirmid on Sunday March 02, 2014 @05:50AM (#7328659)
I've written more than a few syntax highlighters (as well as semantic highlighters and entire IDEs based on incremental parsing and type checking). This is one of those features where eclipse is quite ahead of visual studio, but its quite a minor feature it makes sense that isn't a high priority.
Re:The sorry state of Visual Studio syntax highlighting (2012) by wila on Sunday March 02, 2014 @06:57AM (#7328817)
You're the author of the post? Can't seem to see who author "Sam" is at that blog, but I did notice that not only did the author write the complaint, but also wrote code to address his issues in a later post.

http://lolengine.net/blog/2012/12/01/announce-vslol-1.0.0.5-...

FWIW, I've worked on syntax highlighters myself and IDEs as well which is what prompted my reaction. The particular problem didn't seem to be a big enough problem for me to warrant the post. But hey.. what do I know, I'm not Sam, at least kudos to him that he actually did something about the issue he had besides writing the inflammatory post.

Re:The sorry state of Visual Studio syntax highlighting (2012) by seanmcdirmid on Sunday March 02, 2014 @07:03AM (#7328833)
Not the author of the post but have been frustrated by this before.
Re:The sorry state of Visual Studio syntax highlighting (2012) by sidcool on Sunday March 02, 2014 @05:43AM (#7328641)
So one person does not like syntax highlighting of Microsoft and he/she uses expletives. Bugger you, sir, for writing this article.
Re:The sorry state of Visual Studio syntax highlighting (2012) by gus_massa on Sunday March 02, 2014 @07:30AM (#7328909)
The article discusses a few workarounds. I didn't like the tone, but it's interesting, not only a long rant.
Re:The sorry state of Visual Studio syntax highlighting (2012) by merrua on Sunday March 02, 2014 @05:45AM (#7328647)
I keep forgetting that is a worse swear word in american english. 2 years later though the situation has not improved.
Re:The sorry state of Visual Studio syntax highlighting (2012) by mseepgood on Sunday March 02, 2014 @04:55AM (#7328515)
why do you need colors at all?