From: Ilias Lazaridis Date: 2011-06-13T03:40:30+09:00 Subject: Re: BARRIER - require "rubygems" On 12 Ιούν, 19:39, Luis Lavena wrote: > On Jun 11, 1:29 pm, Ilias Lazaridis wrote: > > > Back to topic: please ask some product manager that you trust about > > the basic installer requirement that I've mentioned (it's not my > > requirement, but a general one). > > http://msdn.microsoft.com/en-us/library/ee915058.aspx > > "Another reason to streamline setup is that inexperienced users [...] This just confirms: leave the boxes checked, or get rid of them (maybe detect if there are already associations or path variables, and confront the user only then). > Anyhow, seem your level of expertise in fields from OO, embedded [...] What you call "criticism" is basically detecting issues like weaknesses, flaws, barriers, inconsistencies, defects. This is my main expertise, or an inborn talent and tendency (or even a "curse"). If spotting the issues leads to change, then this is a constructive criticism, a contribution. If I make additionally implementation / architectural suggestions, then it's design work. If there is much change-resistance (e.g. from the typical "freak- show", the self-declared "community police" or simply by one crazy- gone individual who writes publicly when he's under drugs), then it becomes hard work. Each issue needs an (estimated) average of 2 days mental attention until it is solved in the language repository (where it benefits all). Saying that this is no contribution at all is simply ungrateful and insincere. > Here is RubyInstaller repository: > http://github.com/oneclick/rubyinstaller I don't have to prove my technical skills. The people that I'm interested in, detect my abilities just from my writings - they don't need to see a line of code. But I'll reach code-level "naturally". I'll most possibly try the DevKit when I reach C-level. I'll report as usual issues that I spot and most possibly I'll send some code-level changes via the usual channels. . -- http://lazaridis.com