tag:blogger.com,1999:blog-15324911.post114499120160382932..comments2017-02-02T16:32:11.792-05:00Comments on Let's Push Things Forward: BugginessMatt McKnighthttp://www.blogger.com/profile/16098483018096096360noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-15324911.post-1145063828622342232006-04-14T21:17:00.000-04:002006-04-14T21:17:00.000-04:00Glad you at least agreed with my perspective on sp...Glad you at least agreed with my perspective on spending money within the enterprise. Does this still make me too enterprisey for speaking about it?<BR/><BR/>Can I at least get a little respect for acknowledging when we are too enterprisey and when we are not?<BR/><BR/>Do you think you can get the Ruby community to acknowledge that at times they are too anti-enterprisey?<BR/><BR/>FYI. I am not anti-Ruby. I just want folks in the community to acknowledge alternative perspectives. Ruby has its place.<BR/><BR/>Hype is the plaque in the house of software...James McGovernhttps://www.blogger.com/profile/10192703428650911093noreply@blogger.comtag:blogger.com,1999:blog-15324911.post-1145037376703808282006-04-14T13:56:00.000-04:002006-04-14T13:56:00.000-04:00Some really good points there. I think part of the...Some really good points there. I think part of the problem is that people are looking for *THE* GIS solution when the optimal solution usually involves integrating multiple programs into a workflow that suits your needs. In my work, we use ESRI software but about half the time it just isn't cut out for the task, either due to bugs or lack of certain functionality. So we turn to GRASS, GDAL, OGR, PostGIS or Mapserver, etc. And often these aren't cut out for the task either so we have to search for another solution or roll our own. <BR/><BR/>It takes alot of time and experimentation to find out which software is optimal for certain tasks but it's a crazy to think that any one software package will cover all your needs. That's not what the budget manager needs to hear but its the truth.Anonymousnoreply@blogger.com