[fpc-devel] Russian locale information not compatible with FPC locale variables

[Marco van de Voort]

> > "compatible" is nonsense, since they are not compatible to any of the
> > roughly three preexisting ones. Descendant could be said, but I don't even
> > see much evidence for that. There is a superficial resemblance in the parser
> > model and that is about it.
> 
> At least, they're trying to answer what the users need in .Net world 
> which CodeGear couldn't do.

Wouldn't do, since it is a totally different market. A new language,
incompatible with everything.  While Codegear caters to the needs in its own
usergroup, not in (a very vaguely defined) .NET world.

> They have guts to be different instead of being follower.

Funny that you say that about the Oxygene language. To me the language
concept and marketing screams ".NET me too wannabe".
 
> > They are about as Pascal as Perl is C because they both have curly braces
> > and some similar operator names. 
> 
> But, users have an option to convert their old Delphi codes 

Where? There is no migration path. It is scratch from new for all
non-trivial code. 

> and get the new technology as the pay-off.

Which "new" technology?
 
> > "less compatible"?!?!? Can Oxygen actually compile and execute any preexisting
> > code in any Pascal dialect ?
> 
> Neither FPC.

Note that I say _any_ not _all_.

> > I do recognize that Rem Objects needs some language to package and promote
> > their frameworks (the thing they are IMHO good in), but the featurelist is a
> > bunch of C# me too's.
> 
> It's acceptable as they provide Oxygene only for .Net platform. Nothing 
> wrong of being "me too" if it offers benefits of new technologies.

There is nothing new there. It is all C# and Java rehash.

> It's wrong, IMO, of being stagnant and not creative in the name of
> "compatibility".

Well, then where are the major new features of Oxygene? Where, what?

> Technologies are always improving and changing. We can't
> force ourselves to stick with old technologies just for compatibility
> sake. 

Programmers are not exempt from normal business practices. And that means
constant revenue, dealing with installed base and long term investment
plans.

> Compatibility is preserved only if it's possible to be done.

And all this from a codepage number in one line of source.