5 ms·
I wish they wouldn't use non-word characters in the names of their products. I thought ".Net" was bad enough when it came out - then C# and F#. But I don't ev
by ratsbane 16y ago
I wish they wouldn't use non-word characters in the names of their products. I thought ".Net" was bad enough when it came out - then C# and F#. But I don't even know how to type this. On this page: http://research.microsoft.com/en-us/um/cambridge/projects/comega/doc/comega_whatis.htm http://research.microsoft.com/en-us/um/cambridge/projects/co... they refer to it as Cw, Cω, and Comega. The artist formerly known as incomprehensible.
- nandemo 16y agoWell, it's not a product. "Cω is an experimental research language. There are no plans to turn it into a commercial language supported by Microsoft. It is not supported by either the C# or the Visual Studio teams. There are no plans to integrate it into any product." I guess people working in research enjoy the leeway of being able to name their projects any way they want.
- pbreit 16y agoExcept the guy gave two other examples of impossible-to-search-for Microsoft-given names: .net and c#.
- coderdude 16y agoIf you search for either of those terms in Google or Bing you find the appropriate resources right away. People love to regurgitate that these names are not searchable but somehow we've found a way. Cω isn't typeable, but that's a different issue.
- rtaycher 16y agothere are come problems with readable url's(ex stack overflow, questions with c# in the title end up looking like questions about c).
- coderdude 16y agoThere are issues if the stubs you use in your URLs only allow a-z and 0-9. You could just as easily escape each character in the stub and preserve the title of the post/question you're representing. This is a problem with Stack Overflow though, not the name of the language (C#). Wikipedia has this issue solved. You can use any Unicode character in their titles and they get used as the stub by escaping those characters. Anyway, it's not like the whole world only uses the English alphabet. This should be handled properly.
- rwmj 16y agoExcept '#' doesn't work, see: https://secure.wikimedia.org/wikipedia/en/wiki/C# https://secure.wikimedia.org/wikipedia/en/wiki/C#
- fabjan 16y agoThat's a wikimedia issue.
- phpnode 16y agonot really, the server can't see that # in the URL, it doesn't get sent by the browser. The only way they could do that is if they switched to #! style ajax urls ala twitter
- ratsbane 16y agoThe number sign (pound sign, octothorpe, etc) separates the fragment identifier from the URL. Browsers don't send characters after the # to the server. It works with Twitter because they use Javascript to AJAX in data from additional requests. http://en.wikipedia.org/wiki/Fragment_identifier http://en.wikipedia.org/wiki/Fragment_identifier
- robin_reala 16y agoC Sharp always seems to me that it should be spelled C♯, not C#. But then I’m coming from a music background.
- kenjackson 16y agoc# is easy to search for. Do a search for "c#" and your first page will be exclusively hits on the language. .NET is the same, although probably more difficult to grep for.
- jedsmith 16y agoImagine the trademark possibilities, though, once you wander away from 7-bit ASCII.
- perlgeek 16y agoomega is a word character. Insert rant about cultural imperialism here.
- ratsbane 16y agomb:~ doug$ perl -e "if ('ω'=~/\w/) {print \"It IS a word character.\";} else {print \"Maybe my language settings?\n\n\";}" Maybe my language settings?
- d0mine 16y ago$ perl -E'say "ω is " . "not "x("ω" !~ /\w/) . "a word"' ω is not a word $ perl -Mutf8 -E'say "ω is " . "not "x("ω" !~ /\w/) . "a word"' Wide character in print at -e line 1. ω is a word
- perlgeek 16y agoYou can get rid of the "wide character" warning with the -CS switch. As you demonstrate correctly, you need to tell Perl about the encoding of your script (and thus the literals in your script). `use utf8;` or at the command line `-Mutf8` does that.
- larsberg 16y agoIt could be worse. Have you ever tried to get help on Pages or Numbers from a search engine? At least stuff with funky characters are unique and if correctly quoted are handled by the major search engines.
- tomwalsham 16y agoFor example, searching for negative numbers. No amount of escaping or encoding will force any of the major SEs to read -17 as anything but an exlusion of 17 from the results.
- hollerith 16y agoKnuth's typesetting system Teχ which is rendered as TeX in Ascii and which Knuth wanted people to pronounce "Tech" being an early instance of this regrettable trend.