On 2020-04-08 13:33, josef Reidinger wrote: > On Wed, 8 Apr 2020 10:46:17 +0200 > Martin Vidner <mvid...@suse.cz> wrote: > >> On Fri, Apr 03, 2020 at 05:21:21PM +0200, josef Reidinger wrote: >>> On Fri, 3 Apr 2020 16:05:04 +0200 >>> Martin Vidner <mvid...@suse.cz> wrote: >>>> >>>> 2) It uses a namespace, xmlns="http://www.suse.com/1.0/yast2ns"; >>> >>> Can we set namespace if it is not defined in XML? What puzzle me the most >>> about that format (not parser) now is not that xml is badly readable, but >>> that it is very hard and error prone to write/modify it. And mandatory >>> namespace is unnecessary from my POV. >>> Can we simple assume this namespace if none is defined? >> >> The quick answer is no. Just like with other programming languages, >> for throwaway scripts working without namespaces is fine but as soon >> as you start building anything bigger or longer lasting, namespaces >> are needed to resolve conflicts and organize things. > > For me it looks like overengineering. Do we plan to have multiple namespaces
Just a warning note from someone who doesn't know the topic so well. The sentence "that is overengineering, we are never going to do X" always triggers my spider-sense.[*] As much as we abuse of the term, it's in fact really hard to overengineer something. Having a piece of software that is not prepared for the future/present (because someone decided that X would never happen) is a WAY more common problem. And we usually cause by trying to avoid the almost-mythological overengineering. Cheers. [*] Spider-sense: see experience. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org To contact the owner, e-mail: yast-devel+ow...@opensuse.org
