.NET at 9.400 ft above sea level - All Comments

Zolpidem.

Zolpidem. — Sun, 20 Jul 2008 17:03:05 GMT

Zolpidem overnight. Zolpidem eszopiclone indications. Zolpidem overdose. Zolpidem.

re: Recursive lambdas and sequence aggregations

Jedrzej — Fri, 18 Jul 2008 09:59:45 GMT

Simpler:

Enumerable.Range(1, 10).Aggregate((x, y) => x * y / gci(x, y)));

Thanks for recursive lambdas your blog is my favourite for LINQ tricks :)

re: SQL Server 2005 Express restrictions and footprint

survey — Mon, 14 Jul 2008 08:02:33 GMT

thanx for visiting :)

re: Programmer fonts, do they matter?

Glenn — Mon, 14 Jul 2008 06:46:26 GMT

....In short... Consolas looks GRREAT on Dreamweaver with ClearType on. Unforunately, I've NEVER liked using Split View in Dreamweaver (or any IDE) for that matter, unless the coding fonts aren't too big and aren't too intrusive.

In fact, I feel confident using SplitView with ProFont, since the smaller font-base really makes it non-intrusvive. So, though Consolas can looks better and more readable on Dreamweavever, on the whole it's rather pointless unless I *really* need a larger font.

Somehow, ProFont has a nasty habit of making even the "messiest" code structure appear neat. Maybe it's the clever choice of character sizes, spacing and the overall condensed nature of it. Sure, individual character readability does suffer at that price, but only slightly.

re: Programmer fonts, do they matter?

Glenn — Mon, 14 Jul 2008 06:22:37 GMT

Consolas with ClearType is great. But I find it better for HTML/XML editing rather than programming, strangely. Somehow, bigger fonts for copying+pastig is sometimes necessary, and Profont doesn't fit that bill, though it's still usable. Consolas is attractive though, but when placed in a programming structure, it doesn't look as nice as it should. It looks great in HTML i must say...

ClearType does make ProFont not appear so crisp either. In short, it's either one or the other.

re: Programmer fonts, do they matter?

Glenn — Mon, 14 Jul 2008 06:18:11 GMT

ProFont vs Proggy

--------------------

Profont has better overall chunk/paragraph readability (due to the condensed nature of the font). In terms of overall readability of a programming code struture, Profont wins.

Proggy has better individual character readability (due to the larger and wider character nature of the font). In terms of individual character clarity, Proggy wins.

ProFont, partly due to its tiny size, would lack distinctness in certain individual characters. Proggy has better distinction, as mentioend above.

Profont is great for people that love tiny and condensed fonts.

Proggy has a larger font-base which may be better for a wider array of audiences.

Both fonts are equally crisp. For some, Proggy can be a pain in the eyes. For some, it works better than Profont, which can be a real pain once you get tired of ProFont's notoriously tiny & condensed fonts.

When comparing Profont's Tiny vs Proggy's Tiny, reading Proggy's Tiny would take some time getting used to compared to Profont, but the larger (not-so-condensed) font-base (whether Tiny or normal) is an advantage over ProFont, especially when you're tired. The other options for Proggy like Bold Punctuation, does prove interesting at times, though they can make your code structure messy.

All Proggy's Tiny's are oddly very widely-spaced and feels a bit strange, so there's more horizontal scrolling here. Proggy at times doesn't seem to really have consistent spacing between its characters, compared to ProFont.

Proggy's "www" and other characters do touch one another a bit.

Somehow, using ProFont makes your code appear very nice, clean, organised and structured. But yes, it does so at a price of having a much more condensed and tiner (but readable) font. So, when it comes to individual character readaibility and distintiveness as such, it won't come across as easy as what one would normally expect with the "bigger fonts out there". This is expected from a font that is "condensed, in order to be readable".

In short, ProFont still wins.

re: Sysinternals, Web searching, and Win Fx February CTP (or January CTP or something else)

MarioPao — Thu, 10 Jul 2008 13:28:33 GMT

Same problem, but resolved.

I found a corrupted "localservices.xsl" file in the folder "C:\Program Files\Microsoft Visual Studio 8\Common7\Packages\1033". I replaced it with one "good" and now works fine.

Evaluating Expressions at Runtime in .NET (C#) « HSI Developer Blog

Evaluating Expressions at Runtime in .NET (C#) « HSI Developer Blog — Wed, 09 Jul 2008 05:50:09 GMT

Pingback from Evaluating Expressions at Runtime in .NET (C#) « HSI Developer Blog

re: Finding the largest prime factor of a number

budu — Thu, 26 Jun 2008 02:22:22 GMT

THAT is great code! There's just a little glitch I think. The FindDivisor function is not useful as the while condition ensure that 'number' will be over 1UL before calling it.

military style

military style — Fri, 13 Jun 2008 17:57:02 GMT

Pingback from military style