Thread by @deobald

building a long-life (10yrs+) graph-backed web service for @pariyatti (a non-profit). we're planning to use #neo4j

i have some questions.

#python + #django support seems... weak, at best? (latest commits to `neomodel` and the django plugin are 2019/2018 with no support for neo4j 4.x)

is this a misconception on my part? i'd love a shout out from people happily building webapps with #neo4j on #python out there

#ruby and #rails support seems okay. #activegraph is a thing and there was a commit this week. the design seems sane.

i have 10-year-old rails apps, though. they... don't work. the ruby & rails ecosystem isn't really geared toward "boring things that will work in 10-20 years"

again, shout outs from people happily building #rails apps on top of #neo4j appreciated, on both counts.

the name of the project is neo for *j* — should we just use #java? nothing is more boring and stable than that.

any #neo4j webapps/apis lang/framework advice that isn't "use node" is welcome here.

again, goals are:
- boring, stable tech
- ...but maintained
- long cycle times (for us)
- long lifespan (for us and our tools)
- contributor-friendly (why we went with python first)

/cc @cv