I think that highlights the point on the limited resources available on the resource side.
What we have sort of works. Could it be better? Most probably. The JOSM editor is very nice but it runs over JAVA and JAVA has been recognised as a security problem and it not recommended for many corporations. Something in Visual Basic sorry Visual Studio Express might be more acceptable. Most commercial coding these days is done in Visual Studio for good reasons. To change the database architecture and the associated infrastructure is a fairly large change. There is a lot of investment in what we have but on the other hand the most valuable bit of what we have is the data and that can moved across. Will it happen. Probably not. Normally what causes this sort of change is money. Things like support costs, what do we do when the guys who know this stuff disappear? Can we demonstrate the code is clean and reliable? I don't think there is anyone looking at these sort of things. Cheerio John On 17 February 2018 at 09:45, Eugene Alvin Villar <sea...@gmail.com> wrote: > On Sat, Feb 17, 2018 at 9:53 PM, john whelan <jwhelan0...@gmail.com> > wrote: > >> Possibly a technical working group to identify areas that could be >> improved or even if we were to start over again how would we do it from a >> technical point of view? Funding would be a different problem. >> > > I believe the now-defunct Strategic Working Group ( > https://wiki.osmfoundation.org/wiki/Strategic_Working_Group) is what you > are looking for? > > ~Eugene >
_______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
