For production sites, why require Solr 2.x and Views 3.x?

I realize that apachesolr 2.x and views 3.x are the future, but I have a policy of only using non-dev releases of modules for my live sites. I just started using Solr with a site and would love to have my results page driven by views. However, I cannot use this module because I am using apachesolr 1.x and views 2.x. I was bummed about this until I realized how easy it was to display the results using views:

function {module}_preprocess_search_results(&$variables) {
  $variables['search_results'] = '';
  foreach ($variables['results'] as $result) {
		$views_search_nids[] = $result['node']->nid;
  }
	$variables['search_results'] = views_embed_view('{name of view}', 'default', implode(',', $views_search_nids));
}

The only thing special about my view is that it receives multiple NID arguments. That's it! Now, I realize that my solution is probably not as efficient as what solr 2/views 3 can provide, but what stops apachesolr_views from using this code for those who want to use solr 1/views 2? I propose a separate release that provides this functionality. If this cannot be achieved under this project, I am willing to create my own project, but I wanted to come to you first.