> > > A new non-text based format would have all the> benefits> > of> > > the text format as well as many more benefits.> > > > The question I keep asking but have not gotten an> answer> > to is: what benefits can be provided in a non-text> format> > that cannot be provided in a textual format? One> example> > would be a start.> > It's easier...

> Text is not a universal data format. Text is a format for> ...text. In order to represent something in text, it must> have a textual description.> > Saying that text is a universal data format is saying like> a binary file is a universal data format. Just because> something can be stored in a text file, it does not make> text a universal data...

> A new non-text based format would have all the benefits of> the text format as well as many more benefits.The question I keep asking but have not gotten an answer to is: what benefits can be provided in a non-text format that cannot be provided in a textual format? One example would be a start.

> @James> > It appears you are dissatisfied not so much with the idea,> but with the quality of an imagined implementation of the> idea. So lets assume for a moment we have a sound working> system, however far fetched it may seem to you, and maybe> you'll find the concept a little less toady.These are not imagined issues. I was asked what...

> > What's needed in this grand scheme is a standard parse> > element definition and format so that tools are> > compatible. For instance, Java could specify a parse> > element definition and could directly compile this> > format... and pigs will fly.> > Actually, what is required is a universal data format. Not> for source code only, but for...

> What problems did you have? please describe some...I gave some examples earlier. Here's a high-level list off the top of my head:* difficult to impossible to incorporate into source control with other resources* no useful diff / merge (XML-based source is big offender)* source that is difficult or impossible to read. If the source becomes...

> :-)> Actually, as a prerequisite for being a good programmer!I was just kidding around but I'm not sure that a deep understanding of computer science is a prerequisite. I think that it helps and you probably can't be a really great programmer without learning it one way or another.I definitely gained a lot by getting a degree in computer...

> >Calling something 'quaint' is a pretty weak replacement > >for an actual argument. What would be a superior format > >and why? > > I thought I presented the argument in my original post.I see no argument. I see an assertion. One that I dispute.> Essentially, modern development tools have moved way> beyond text editors and compilers.I'm...

> >My real problem is losing control over the code. Code is> > >valuable and I need to be able access it in a static form> > >that I can understand. It's mine (or my employer's) and > >will not depend on a third-party to be able to read and > >edit it.> > I suppose that's a common fear. I'm sure many people felt> the same way during the...

> > The common trait I see in the worst programmers is that> > they start coding without a plan. I don't mean> > necessarily a formal plan. I mean they don't have any> > idea how they are going to solve the problem at hand.> > They just code and code and meander around to a> solution.> > I think the real problem in this case is that the>...

> How come nobody mentions understanding of computer science> as a prerequisite? :)A prerequisite to being the worst programmer? I hadn't considered that possibility ;)

> > On a side-note, I'm not sure I understand your point> here.> > I don't use IDEA (I've heard it's great) but are you> > u suggesting that it has two persisted forms of the> code?> > Yes, worse it appears to cache the display representation.> If the cache goes wrong you can get major discrepancies> between what IDEA shows as the content of a...

> Take IntelliJ IDEA. Think of all the antics it goes> through to essentially synchronize the textual> representation with the parsed model it maintains. Two> SORs usually indicates a bad design, and since the text is> obviously not nearly as efficient or as dense as the> model, the logical choice is to scrap the text. Sadly, we> can't do that...

> I must admit I do have an appreciation for good old text;> it's simple and accessible. But as I've pointed in the> best of worlds the actual benefit of text in our day to> day work is quite limited.My real problem is losing control over the code. Code is valuable and I need to be able access it in a static form that I can understand. It's...

> >>It was personality traits that were un-teachable,> fundamental aspects of their being. Things like> persistence in the face of frustration, inquisitiveness> about how things work, a detail-oriented approach, and an> appreciation of quality in all things.> > When a person doesn't have the aforementioned things, then> how is it possible that...