Mal and Phil are back for more Windows Mobile 6.5, Windows Phone 7, and a bunch of your questions. Listen in!
- Download it directly with this link
- Subscribe on your Zune
- Subscribe via iTunes
- Subscribe directly to the Podcast feed with your favorite Podcatcher here
- Listen to it here with the flash player above.
Top o' the WP7 news
- Microsoft announces Xbox LIVE titles coming to Windows Phone 7!
- Browser wars: iPhone, Windows Phone 7, Android 2.2
- Windows Phone 7: Verizon supposedly has cold feet?
Hardware news
- LG GW910 clears FCC, headed for AT&T; Another LG phone: the E900 with Windows Phone 7;LG's C900 tagged by AT&T?; Samsung Cetus Pictured
- HTC Schubert gets shown with WP7; features unibody design
Software news
- CrossTalk IM client for Windows Phone 7: coming soon
- Rumor: Windows Phone 7 may get native Twitter functionality
- Windows Phone 7 Marketplace: No BitTorrent apps
- Twikini developer wants out. Trinket Software up for auction.
- eBay on Windows Phone 7? Done.
Microsoft news
- Windows Phone 7 Developer Tools (final): Sept 16th
- Bing overtakes Yahoo! in the search market
- 'What I learned about Windows Phone 7 from Android'
Community
- Poll: So far, are your happy with the leaked Windows Phone 7 hardware?
- Should Microsoft re-name Windows Phone 7?
Credits
Thanks to the WMExperts Store for sponsoring the podcast. Thanks also to these great artists for the music and to CCMixter.org for offering a great database of Creative Commons music!
Reader comments
WMExperts Podcast Episode 107
Just wanted to say I am excited about the upcoming Windows Phone 7.
Hi was listening the other day and you guys mentioned that WP7 will not have memory issues since it is managed code.
I have been a .Net developer since the beginning and wanted to clarify something.
It is true that the framework will garbage collect and return the memory for objects that are no longer accessible without the programmer having to free up the memory explicitly (like in C/C++). The key there is "no longer accessible".
It is still the responsibility of the programmer to ensure that his code does not hold references to objects, otherwise the garbage collector will not clean it up because it thinks that is still in use. These resource leaks are rather common for inexperienced (or naive) programmers and there is very little the environment can do to prevent it. This is why even managed applications can leak resources and it helps to restart them every once in a while if they do.
Granted, once the application is persisted out of main memory, all of it's resources (leaked or legitimate) will be available for use, but when it comes back into use, you will have the same problem.
I don't know much about the other environments (iOS, Android) development so I don't know if they would handle this case the same way.
PS. I am a big WP7 fan but just wanted to clarify this issue.