December 12, 2011
by Randy DeFauw
This series of articles highlights Perforce's integration and technology partners. Expect to see future articles in this series about once a month.
Downsized Games makes P4U, a Perforce plugin for Unity3D.
Tell us a little bit about your company and your products
Downsized Games was founded by four ex- Pandemic Studio employees, who were perfectly happy with their lives until their studio was shut down. Instead of lying down and taking it, they seized the opportunity to create games the way they always wanted: fun and fast.
Perforce Plugin for Unity3D
What benefits do we get from integrating your product with Perforce? Describe any key technical challenges that are solved.
Unity3D is a fantastic game development tool but it lacks an integrated version control interface.Posted In:
December 09, 2011
by Mark Warren
I recently came across an interesting Perforce-related blog posting by Bruce Dawson ("Source Indexing Is Underused Awesomeness"). In his article he describes how indexing source code can be an extremely powerful debugging aid, especially when you're debugging builds made on some remote machine, however it's rarely used. Source indexing is one of the gazillions of features added to Visual Studio over its long history yet rarely understood or used by most programmers. His article details a nice solution to enable source indexing for source code held in the Perforce depot.
I think it would be unfair to call a relatively rarely used feature like this "bloatware" but I'm sure we can all think of software tools where a large proportion (the majority even?) of functions are hardly ever used. Joel Spolsky argues that it follows the common 80/20 rule - 80% of the users use only 20% of the functionality. Critically, though, it's not the same 20% of functions for all 80% of users. His article is somewhat "mature" now (incredibly it's 10 years since it was written!) but the economic arguments are much the same - hardware costs have continued to decline rapidly (good old Moore's Law) so the cost of adding more features gets less and less.
December 07, 2011
by Bryan Pendleton
This year marks the 25th anniversary of an event that was once known to all computing enthusiasts, but nowadays is just a dim memory: the NSFnet "congestion collapse". The collapse was actually not a single incident, but rather a period of time during which the network was so saturated with re-transmission requests that almost no actual content was successfully being transferred across the net.
The NSFnet routers ran my code, which was horribly overrun by supercomputer traffic. I found the best way to deal with the problem was to find the supercomputer elephants and shoot them. [ ... ]
The NSFnet meltdown occured primarily because the fuzzball routers used smart interfaces that retransmitted when either an error occured or the receiver ran dry of buffers. The entire network locked up for a time because all the buffers in all six machines filled up with retransmit traffic and nothing could get in or out.
If you're wondering what a "fuzzball router" is, you can read more about it here; essentially, it was a package of software that turned a DEC PDP-11 into a node on the Internet.Posted In:
December 06, 2011
by Natalie Estrada
Last Thursday, over 200 geeks from around the Bay Area partied and networked at the Perfortress for the 14th Bay Area Girl Geek Dinner - it was an electric night of new connections and girl geeky-ness! We ate Pad Thai out of pink Chinese food boxes, drank the new Perforce signature drink – the P4D-lish! – and ate pink and purple candy off of the candy bar. The photo booth hosted by HR was busy all night and there was major interest in all of the open job positions.Posted In:
December 05, 2011
by Tony SmithPosted In:
December 02, 2011
by Randy DeFauwPosted In: