stevedlawrence commented on issue #39: URL: https://github.com/apache/daffodil-vscode/issues/39#issuecomment-946689467
Understood, but I just don't see that as a common use case. I don't even find myself switching to old Daffodil versions all that often. And when it is needed, I'd claim that requiring a user to install a different version is not overly cumbersome. First and foremost I'd say installing this tool should be super easy, more than one step is too many. And as long as switching Daffodil versions is possible, but not necessarily super convenient, I'm okay with that. My concern with this right now is building and installing from source, which Apache prefers, is not as easy as it could be. One needs to build and install this .vsix file as well as build and unzip a file to some system-specific location. It's not hard, but it's a barrier to entry that seems unnecessary to me. I'm just trying to find a way to minimize that. And remember that many systems where Daffodil/VSCode are used might not even have internet access, so the manual steps of downloading a file and unzipping to a local directory still will need to be done sometimes. In my view, that should never be required. I would prefer if the steps for a non-networked user were only `Install this VSIX file` or alternatively `Install this official Daffodil RPM, and then install this VSIX file`. You haven't mentioned anything about my other suggestions. Is there anything specific you dislike about them? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
