Slashdot Mirror

check-ins transpose lines on check out; complete failures to update to actual latest versions of code; and random check-outs of code with no local changes.

If you can reproduce any of those things, please email me.

can't unshelve to anything but the changeset that the shelf came from

This isn't really legible, but I think you meant to say "branch" or "workspace". But in any case, it isn't true. You can use tfpt.exe (tf power tools) and force all kinds of "unsafe" things, like unshelving an add/edit shelveset across branch definitions.

local workspaces can't be moved (say, in the advent of hardware failure on a development machine).

This is also false. Moving an existing enlistment on another computer is something we do frequently

tfpt workspace /updatecomputername workspace

(ref: http://blogs.microsoft.co.il/blogs/shair/archive/2008/09/03/using-tfpt-command-line-tool.aspx)

I work on Visual Studio. All of Visual Studio is under TFS source control. We use it every day.

To dogfood scalability, we use a single instance for all of VS. It supports every single team within VS; thousands of simultaneous engineers with hundreds of branches across multiple sites (I'm in Fargo, and TFS is in an entirely different timezone)

Start typing to make a change, only to have all but the first character thrown away as TFS laboriously attempts to check out the file first.

Since I grew up using commandline SCC, I normally use tf.exe to open files for edit. You're referring to the feature in the code editor when you dirty a controlled file, we try to go create a pending edit. I don't know if that is still quasi-synchronous or not. In any case, there are certainly work- arounds -- like using the explicit checkout gesture in the solution explorer -- prior to typing in an editor window.

But still, the main event for Windows 8 are the Metro apps, and the capabilities of their window management is quite similar to Windows 1.0, which could even display a taskbar at the same time.

I think he does mean 150GB: http://msdn.microsoft.com/en-us/library/windowsazure/ee336245.aspx#dcasl

Windows Azure SQL Database provides two database editions: Web Edition and Business Edition. Web Edition databases can grow up to a size of 5 GB and Business Edition databases can grow up to a size of 150 GB.

Here are some benchmarks - which might be out of date:
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/02/windows-azure-benchmarks-part-13-sql-azure-read-throughput.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/08/windows-azure-benchmarks-part-14-sql-azure-write-throughput.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/13/windows-azure-benchmarks-part-15-sql-azure-read-latency.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/16/windows-azure-benchmarks-part-16-sql-azure-write-latency.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/22/windows-azure-benchmarks-part-17-compare-storage-types-performance.aspx

The performance might have increased since.

I think he does mean 150GB: http://msdn.microsoft.com/en-us/library/windowsazure/ee336245.aspx#dcasl

Windows Azure SQL Database provides two database editions: Web Edition and Business Edition. Web Edition databases can grow up to a size of 5 GB and Business Edition databases can grow up to a size of 150 GB.

Here are some benchmarks - which might be out of date:
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/02/windows-azure-benchmarks-part-13-sql-azure-read-throughput.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/08/windows-azure-benchmarks-part-14-sql-azure-write-throughput.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/13/windows-azure-benchmarks-part-15-sql-azure-read-latency.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/16/windows-azure-benchmarks-part-16-sql-azure-write-latency.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/22/windows-azure-benchmarks-part-17-compare-storage-types-performance.aspx

The performance might have increased since.

I think he does mean 150GB: http://msdn.microsoft.com/en-us/library/windowsazure/ee336245.aspx#dcasl

Windows Azure SQL Database provides two database editions: Web Edition and Business Edition. Web Edition databases can grow up to a size of 5 GB and Business Edition databases can grow up to a size of 150 GB.

Here are some benchmarks - which might be out of date:
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/02/windows-azure-benchmarks-part-13-sql-azure-read-throughput.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/08/windows-azure-benchmarks-part-14-sql-azure-write-throughput.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/13/windows-azure-benchmarks-part-15-sql-azure-read-latency.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/16/windows-azure-benchmarks-part-16-sql-azure-write-latency.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/22/windows-azure-benchmarks-part-17-compare-storage-types-performance.aspx

The performance might have increased since.

I think he does mean 150GB: http://msdn.microsoft.com/en-us/library/windowsazure/ee336245.aspx#dcasl

Windows Azure SQL Database provides two database editions: Web Edition and Business Edition. Web Edition databases can grow up to a size of 5 GB and Business Edition databases can grow up to a size of 150 GB.

Here are some benchmarks - which might be out of date:
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/02/windows-azure-benchmarks-part-13-sql-azure-read-throughput.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/08/windows-azure-benchmarks-part-14-sql-azure-write-throughput.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/13/windows-azure-benchmarks-part-15-sql-azure-read-latency.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/16/windows-azure-benchmarks-part-16-sql-azure-write-latency.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/22/windows-azure-benchmarks-part-17-compare-storage-types-performance.aspx

The performance might have increased since.

I think he does mean 150GB: http://msdn.microsoft.com/en-us/library/windowsazure/ee336245.aspx#dcasl

Windows Azure SQL Database provides two database editions: Web Edition and Business Edition. Web Edition databases can grow up to a size of 5 GB and Business Edition databases can grow up to a size of 150 GB.

Here are some benchmarks - which might be out of date:
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/02/windows-azure-benchmarks-part-13-sql-azure-read-throughput.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/08/windows-azure-benchmarks-part-14-sql-azure-write-throughput.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/13/windows-azure-benchmarks-part-15-sql-azure-read-latency.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/16/windows-azure-benchmarks-part-16-sql-azure-write-latency.aspx
http://blogs.microsoft.co.il/blogs/applisec/archive/2012/02/22/windows-azure-benchmarks-part-17-compare-storage-types-performance.aspx

The performance might have increased since.

That's just his playoff beard. Once the Stanley Cup Finals is over, Ruby is toast.

You have never seen Matz and Ilya Kovalchuk in the same room together. Coincidence? I think not.

Everyone knows it's the Amount of Facial hair

Does the designer of the language have facial hair? No point in learning it if he doesn't. (And if it's a woman and she's not the bearded lady, forget it.) http://blogs.microsoft.co.il/blogs/tamir/archive/2008/04/28/computer-languages-and-facial-hair-take-two.aspx

See, I think, having worked with all of those languages, that they all suck, but each sucks in different ways and thus each has their uses. The mistake a lot of folks get into is "This is the language I'm most familiar with, so it's the best language ever".

Of course, the real contest will be the length of the language designers' beard:
http://blogs.microsoft.co.il/blogs/tamir/archive/2008/04/28/computer-languages-and-facial-hair-take-two.aspx

But don't forget to do the thing the students will care most about: shave your beard.

I beg to differ

maybe he's a software engineer who wants to be successful like a few of these gentlemen?

They wear [...] a beard, this can't be a good thing

Actually this is a good thing.

would it kill you to buy a nice shirt and a razor?

I know from a reliable source that RMS owns the Gilette Luxury Pack and a business suit. "Know your enemy" and all that. Besides, he has to defend lisp and scheme (in their emacs and guile dialects): http://blogs.microsoft.co.il/blogs/tamir/archive/2008/04/28/computer-languages-and-facial-hair-take-two.aspx

The picture in the linked article is missing a beard.

I was going to mod you funny, then I thought maybe a lot of people wouldn't get the beard reference, so I decided to post instead. Anyone else want to mod parent funny?

You might want to reconsider that. There is a proven significant link between facial hair and the success of programming languages. I would assume there is a similar correlation in any software project.

I predict the GPP's license is doomed to preside over failures, due to the intrinsic lack of facial hair.

Some of you might remember the article at:

Facial Hair:Coding Success

Has Bjarne grown a beard or something? That's the only way I can explain that he's on the front page of slashdot today.

That article is basically a rip of this one by Tamir Khason. Heck, it's essentially a blatant copy of the 2004 version of Tamir's article with some of the 2008 pictures thrown in!

This page (from a recent Slashdot article) reliably crashes to desktop for me, just as the previous beta did.

http://blogs.microsoft.co.il/blogs/tamir/archive/2008/04/28/computer-languages-and-facial-hair-take-two.aspx
Any further questions?