BudVVeezer

18 ms·

1. 181.▲
   Visual Studio 2010 RC available(blogs.msdn.com)

   2 points by BudVVeezer 17y ago|0 comments
2. 182.▲
   by BudVVeezer 17y ago

   It seems to me that the complaint is "what used to fail with this error code now fails with a more annoying and scary error code." It's still a regression, but hardly one that's a huge cause for concern.
3. 183.▲
   Free book on F#(ctocorner.com)

   35 points by BudVVeezer 17y ago|1 comments
4. 184.▲
   by BudVVeezer 17y ago

   Failing to call "delete" on a pointer you "new"'ed in C++ is also clearer, and just as incorrect. The ECMAScript spec makes no mention of how memory will be managed for the user. Right or wrong in terms of clarity, it's still a poor pract
5. 185.▲
   by BudVVeezer 17y ago

   I think developers should always try to avoid poor programming practices instead of relying on implementation details of the browser.
6. 186.▲
   JavaScript memory leak patterns(ibm.com)

   32 points by BudVVeezer 17y ago|7 comments