|
And, little did CP know what would be unleashed this day!
Now, where's that eye dropper to siphon up that rejoiceful tear...
|
|
|
|
|
Congrats!
And for your birthday present I'll refrain from calling you an old fart
It's an OO world.
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
|
|
Happy birthday Marc, here's hoping you're with us for many more.
Have you ever just looked at someone and knew the wheel was turning but the hamster was dead?
Trying to understand the behavior of some people is like trying to smell the color 9.
|
|
|
|
|
Boring - the same thing happened at exactly this time last year!
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
|
|
|
|
|
PhilLenoir wrote: Boring - the same thing happened at exactly this time last year!
I know. I'm surprised nobody dug up that post and exclaimed "Repost!"
Marc
|
|
|
|
|
Happy Birthday, Marc !
“I have diligently numbered the days of pure and genuine happiness which have fallen to my lot: They amount to 14.” Abd-Ar Rahman III, Caliph of Cordoba, circa 950CE.
|
|
|
|
|
|
|
Marc Clifton wrote: Little did the world know what would be unleashed this day, 1962! So we agree that you should be leashed?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
It's been 7 years since I bought my last new machine (Dell 1720 laptop, 1920x1200 LCD, 160G 7200rpm drive, 4G RAM), which works well for developing WinForms apps but doesn't cut it for Xamarin mobile development. So I bought myself Brix Pro[^] last night.
- i7 4th gen quad-core @ 3.9GHz
- Intel Iris Pro 5200 graphics
- 16GB 1600MHz RAM
- 500 GB Samsung EVO (6GB/sec read, 5GB/sec write) SSD
- USB3 x 4, 802.11 a/b/g/n/ac, RJ45, Bluetooth, display port, HDMI, headphone + S/PDIF
- Size = 4.5" x 4.5" x 2.5"
Going to have fun setting it up and moving my development to it!
/ravi
|
|
|
|
|
No, you're gonna have fun once you have it set up and all the software installed and configured.
And the ship-it-with-these-viruses (Symantec, McAffee, Win8) removed.
In the meantime it's going to be progress-bar hell....
And yes, I'm jealous!
You looking for sympathy?
You'll find it in the dictionary, between sympathomimetic and sympatric
(Page 1788, if it helps)
|
|
|
|
|
OriginalGriff wrote: And the ship-it-with-these-viruses (Symantec, McAffee, Win8) removed. No, because it doesn't come with a hard disk or OS.
OriginalGriff wrote: In the meantime it's going to be progress-bar hell.... Shameful admission: I love setting up a brand new dev box from scratch!
/ravi
|
|
|
|
|
How? It takes forever - even a couple of weeks later I'm generally going "where's the installer for that doohickey?" when I try to use something I forgot...
You looking for sympathy?
You'll find it in the dictionary, between sympathomimetic and sympatric
(Page 1788, if it helps)
|
|
|
|
|
I archive all my installers and license numbers on an external disk (doubly backed up!), so finding my OSs and apps is pretty easy. I tend to keep my PCs lean and mean. All my source code (except for throwaway samples) is stored in TFS @ Microsoft, so recreating my dev workspace is pretty easy.
/ravi
|
|
|
|
|
The problem with packratting installers is that, unless you're equally CDO about checking each vendor monthly for new versions, you end up installing a mess of old versions.
The part of new box config I loathe the most is that installing VS in any order than oldest to newest never works out right. If I could just install the current versions of VS, SVN, and Re#er I could probably be ready to start work on a new box in an hour or two. Instead, the last time I did it building the VS03, 08, 2010, 2012 stack took a full day; and the only one of those I could safely jettison today is 08. I'm working on a new version of the last major 03 app I have left; but would need to test one more small one to make sure it builds before I could boot it. Even then I'm not sure I'd want to; for regression investigation having the 03 version debuggable would be useful and it includes a grid library that doesn't place nicely with .net 2.0 or later.
Then there's normal java, android java, and (unless we either give it up, or win and someone else gets stuck with it) blackberry10 java so I can reinstall the demo app every 60 days when it ages off the dingleberry it's installed on. Two ruby apps, one running with a locally installed copy the second in a VM; both using git instead of svn.
And that's not even mentioning the mess of other tools, etc that I've accumulated over the years.
It took a full week of clicking next between doing real work on the old system before I was ready to switch to my new laptop the last time.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Good point.
I think my situation is a bit different. I've been using VS2010 so far for personal dev, and will be adding VS2013 to my arsenal. Other than that, I only have single (and in most cases, latest) versions of other tools (MS Office, PShop, install builder, obfuscater, and a few free utilities that I can't live without), so migration to a new machine isn't too painful.
/ravi
|
|
|
|
|
My solution for that is to have one VM for VS 2008, one more for 2010, 2013, etc. I still have the installers for each one of them (as ISOs), but primarily I rely on copies of each compiler installed in otherwise completely clean VMs. The clean VMs is what I'm mostly interested in backing up on a regular basis.
Whenever I feel like it, I boot up those clean VMs, download all the latest updates, then update my set of archived VHD images.
|
|
|
|
|
I've thought about a VM for legacy stuff at work, although it'd probably be a single VM for all old VS versions so I could keep it locally without overflowing my relatively small HD. I've never been happy enough with VM dev tool performance in the past under MS-VPC (picking my own hypervisor and getting the VM on the domain are mutually exclusive) or it not playing well with multiple monitors to want to do any primary dev in it though; so I'd still probably end up with at least 2 versions of VS and all the java crud installed locally.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
If all you have to compare with is VirtualPC, you really ought to give it another shot--the state of virtualization has changed a lot since VPC was a contender. I'd been using HyperV with Server 2008 R2 for about 2 years (recently moved on to 2012 R2), and while it's probably not as fast as running an OS natively, my VMs perform well enough that it's generally not a worry.
The key is having enough RAM. As soon as memory usage gets above roughly 85-90% of your physical RAM, performance will drop through the floor. I started off with 8GB, then quickly moved on to 16, then 32, but that's just me--as I throw more RAM in my system, I find myself wanting to simply leave more VMs running all the time. Lucky for me, I was doing this when RAM was going for about half of current prices. If that was still the case (and I had a motherboard that could handle it), I'd move on to 64GB. My CPU is an i7 2600K (from the Sandybridge generation). The CPU's never been a bottleneck no matter how many VMs I throw at it. RAM and disk I/O will get there first.
Practically everything I do nowadays is off of VMs, and I'm not looking back. I have nothing running on the host OS (except for the necessary motherboard drivers), so if the worse happens and hardware dies (and it's happened to me), reinstalling the OS is a 20-minute job, and that's from scratch--since I have no additional app to reinstall, I don't bother backing up the host OS. The VMs are running off of a different physical hard disk (right now in fact a RAID setup). Backing those up is a matter of invoking robocopy from a batch file, though it could be automated. In the worse case, all I need is one VHD file to bring back a VM - creating a new VM and pointing it to an existing .VHD file takes 30 seconds, if that, to walk through the wizard.
As for your last point--a multiple monitor setup--my VM host is sitting in the basement and is just using the onboard video (it might as well be headless, considering how rarely I have to be in front of it). I access it from my desk in my home office upstairs with a first-gen Surface Pro that's got 3 1920x1200 monitors hooked up through a USB3 dock. I can RDP into any VM either in a small window, full-screen on one monitor, or using all three monitors (plus the tablet's own display).
Since everything's running remotely, it's nice to be able to access my full environment outdoors, or at the office through VPN, with little more than a cheap laptop that doesn't have anything of value on it.
|
|
|
|
|
*nod*
Working for a contractor is a pain for stuff like this; multiple customers really makes the many platform problem explode.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Awesome, Sata III as well?
|
|
|
|
|
Yes, both mSATA and SATA-3.
/ravi
|
|
|
|
|
Ravi Bhavnani wrote: Size = 4.5" x 4.5" x 2.5"
Oooh, that's the coolest thing about it. I built an 8 core system a year ago that sits in a huge metal box, something like 16" x 16" x 10" Yargh. And, unfortunately, it's noisy as sin too with the fans.
But geez, it is screaming fast. I absolutely love SSD's. Windows boots in a couple seconds, everything opens instantly. I'm sure you will love the experience of the SSD and 16GB of RAM with a fast quad core processor. Enjoy!
Marc
|
|
|
|
|