[OSM-talk] Funding of three infrastructure projects : Nominatim, osm2pgsql, Potlatch 2
pangose at riseup.net
Tue Aug 4 11:02:47 UTC 2020
I disagree. For that sum of money I would be willing to start writing a new editor in Rust compiled to WebAssembly and desktop and reach a state of basic editing useability in 2 months.
See also https://www.youtube.com/watch?v=ohuTy8MmbLc
Joseph Eisenberg <joseph.eisenberg at gmail.com> skrev: (3 augusti 2020 01:00:49 CEST)
>While the benefit of making Potlatch 2 on AIR is small, the cost is
>2500 Euros is an insignificant price to pay for supporting an editor
>is still used by a couple of thousand long-term users.
>I support this expenditure.
>– Joseph Eisenberg
>On Sun, Aug 2, 2020 at 10:05 AM Alexandre Oliveira
><rockytvbr at gmail.com>
>> I'd like to share my two cents on the matter of supporting Potlatch
>> an editor built with (now) dead technology.
>> I don't think it's worth spending money to update P2 to Air. As
>> have stated, Air has been discontinued as well, and it was developed
>> by Adobe, probably with the same amount of security flaws as Flash
>> had, which contributed to its demise. I don't see Air as different
>> even though it's being maintained now by Samsung.
>> Just take a look. The web is different than when P2 released; flash
>> deprecated and a synonym for vulnerable systems, Air tried to take
>> but now it's just another dead technology. What are the benefits of
>> porting P2 to Air? It may be easier because Air may share some code
>> with Flash, which in turn makes it easier to port to.
>> However, I think that the OSMF should find someone familiar with
>> and look forward to porting P2 to modern web technologies (please not
>> CoffeeScript or TypeScript, React, Angular, Vue.js or any other
>> web tech, it doesn't matter. I think it's going to be money well
>> if P2 was ported to a supported web technology and not something that
>> died a few years ago and is on life support, and barely anyone uses
>> IMO porting P2 to Air is just a waste of money and time from the
>> developer, and we will reach the same point in the future, be it
>> either for deprecating P2 or looking to port it to newer web
>> technologies. OSMF should prepare for the future and not continue
>> using deprecated technology.
>> talk mailing list
>> talk at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the talk