>> I don’t consider that a problem, on the contrary: eating your own dog food >> is good. >> >> BTW, in the past (old tools, old frameworks) the problem was the same. > > When Camille last week tried to convince me to kill the old Compiler *now* > I said “but it’s so nice to be able to switch when changing the new”. > He replied: “But there was just one old Compiler, wasn’t there?” > > And he is right.
No :) He will not be the guy that will have to fight with bugs in Opal but you. He would have been right if we would have a script or a way to create a new opal that can compile another one. I'm in favor to remove the old compiler and the old browser but only when we are in a situation where we can continue to work fast. > What we need to do for real is to support multiple versions of code in the > same > image… or multiple images where one can remote-devlope the other. > This would solve the problem for real. Just start to compile in a different environment is a first step in that direction. without a fully environment based system there are solutions but they will take time. Stef
