Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

I replied to joosts mail here https://lists.openstreetmap.org/pipermail/osmf-talk/2018-February/005082.html Am 20.02.2018 um 08:57 schrieb joost schouppe: > This discussion shows once again how great we are at generating smart > ideas. That definitely is not our problem. But all ideas are equal

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

This discussion shows once again how great we are at generating smart ideas. That definitely is not our problem. But all ideas are equal and will only get executed if the one who posited them executes them. As the project becomes more complex, that means you can either play in a corner by

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

On Sat, Feb 17, 2018 at 4:29 AM, Maarten Deen wrote: > On 2018-02-17 10:56, Oleksiy Muzalyev wrote: > >> This article is on the front page of the Slashdot today: >> >> Fri 16 February 2018 "Why OpenStreetMap is in Serious Trouble" >> >>

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

I also read this article and I found it identifies some areas in which (the central infrastructure of) OpenStreetMap could improve. What I do not like about this article is the deeply pessimistic and resigned tone of it, like clickbait. It reads like "OSM needs to change from the core up or else

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

"but where Google starts to go haywire is in the properly mapped areas." As someone who lives remote in the Netherlands, I can agree to that. DHL, UPS, even ambulances; they are still unable to find my house although I am living here 7 years now. But, I think OSM is also going haywire in the

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

On 2018-02-17 22:02, Jakob Mühldorfer wrote: > Thanks for pointing it out to us! > > I too have some thoughts on points in the article. > One I agree with, one not > > Let me start with this one: > "No Support For Observational, or Other Datasets" > This is the point I agree with. > OSM is

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

Thanks for pointing it out to us! I too have some thoughts on points in the article. One I agree with, one not Let me start with this one: "No Support For Observational, or Other Datasets" This is the point I agree with. OSM is missing out on some valuable information due to this strict

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

Java and Javascript have only those four letters in common. They are completely unconnected in all other respects. On 2018-02-17 19:54, john whelan wrote: > JAVA script is used by web sites. It does not require JAVA to be installed. > > JAVA itself may or may not be a security risk the issue

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

JAVA script is used by web sites. It does not require JAVA to be installed. JAVA itself may or may not be a security risk the issue is that it has been declared one by the US government in the past and that means many organisations will not permit it to be installed. Relevant because it is a

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

Curiously enough those same organizations and governments then run Java web apps on their servers. Java isn't a security risk, Java applets running inside a browser are the problem. And that's blocked by browsers nowadays. I don't understand why this is relevant to the original discussion

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

The JAVA issue comes up as many use work machines and since JAVA has been identified by the US government as a security risk some time ago many organisations do not permit it's installation on their equipment. Which means in simple terms you can't use the building_tool plugin when mapping

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

You would need to install mono to run it and not everyone has mono or wants it installed(thats the problem with Virtual Machine languages). We would also have to rename it to Cosm. Doesn't have a nice ring to it ;). On Feb 17, 2018 1:19 PM, "Mike N" wrote: > On 2/17/2018 11:01

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

On 2/17/2018 11:01 AM, James wrote: except it wouldnt be multiplatform and only run on windows 濫冷. Java is a better alternative as it's a popular language and is multiplatform. C/c++ is a bit more complicated and not everyone can contribute. That's no longer true - .Net is open source and

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

El 17 feb. 2018, a la(s) 06:56, Oleksiy Muzalyev escribió: > This article is on the front page of the Slashdot today: > > Fri 16 February 2018 "Why OpenStreetMap is in Serious Trouble" > > https://blog.emacsen.net/blog/2018/02/16/osm-is-in-trouble/ > > > "The

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

except it wouldnt be multiplatform and only run on windows 濫冷. Java is a better alternative as it's a popular language and is multiplatform. C/c++ is a bit more complicated and not everyone can contribute. On Feb 17, 2018 10:56 AM, "john whelan" wrote: > I think that

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

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

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

On Sat, Feb 17, 2018 at 9:53 PM, john whelan 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

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

I think there are some valid points but change is hard and needs a lot more resources than we have available at the moment. HOT has a validation process but if you look at their projects its rarely used and when it is a new mapper has been permitted to validate. OSM has come as far as it has

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

The emacsen's blog post is spot on. I see it as a call for change from a person who genuinely cares about OSM, not a bitter rant. When you say A and the world says B, it maybe well worth considering that B is the way to go. I think many other people share his views, but were afraid to voice it,

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

2018-02-17 11:56 GMT+02:00 Oleksiy Muzalyev wrote: > For instance, reviews. I hope it will not come to what there is at some > commercial maps, when one adds say a building and then has to wait for a > month that an almighty moderator approves it, so that it appears on the map. This is an

Re: [OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

On 2018-02-17 10:56, Oleksiy Muzalyev wrote: This article is on the front page of the Slashdot today: Fri 16 February 2018 "Why OpenStreetMap is in Serious Trouble" https://blog.emacsen.net/blog/2018/02/16/osm-is-in-trouble/ Interesting that he mentions that "the proprietary mapping world

[OSM-talk] "The Future of Free and Open-Source Maps" Slashdot.org , Saturday February 17, 2018

This article is on the front page of the Slashdot today: Fri 16 February 2018 "Why OpenStreetMap is in Serious Trouble" https://blog.emacsen.net/blog/2018/02/16/osm-is-in-trouble/ "The Future of Free and Open-Source Maps"