Hacker News Reader

Comment by aruntdharan | Hacker News Reader

Thanks for the tip. We believe it's still the data engineers who will have to write these reverse connectors as well. We understand that python is probably the preferred choice of language for them. We have also seen that a majority of them understand java as well. But we are willing to support multi-language functionality in future, if the community demands it. Do you think majority of the data engineers do not understand Java?

View on HN

It's probably 10 to 1 preference of Python over Java for data engineers. At least 5 to 1.

Noted. We will definitely consider adding support for python. Thanks for the suggestion.

You might consider checking Jython out as an option. It's JSR-223 compliant and trivial to drop into a Java app and just expose Java objects to the Python scripts to be used as is. I've had a pretty great experience with it.

The only downside is it's stuck on supporting Python2.x so you may end up wanting to properly integrate CPython eventually. Since you're targeting running Python code that doesn't exist yet and the language differences aren't huge though, I doubt most users would mind (I wouldn't). Just an idea to consider, esp for an MVP

(One /upside/ is Jython is a Python2 interpreter fully written in Java, so the concurrency and performance may be better than CPython2 with its GIL)

Just checked it out. Looks interesting. Thanks

I would disagree with this. Most Python developers I know can do Java. Not a big deal.

Since there seems to be differing opinions here, I'll just add my experience that having worked with 3 data teams, everyone knew Python and used Python and no knew or used Java.

Great product and very excited for this, wish I could invest in you and wish this had been around years ago when I was trying to convince Fivetran they should create reverse ETL functionality.

Thanks for letting us know!

"Know" vs "willing to write", esp. OSS for making someone else rich

Nowadays, probably something like python then rust/go, just for community, and especially aligned on apache arrow. OSS async python / HTTP, with arrow dataplane support (fast,typed,standardized), is part of our bar for whether we consider a data proj as a core dep nowadays. A surprising amount of ETL startups are YOLO json for the dataplane, so we've intentionally stayed away due to reliability+perf heart pains. But maybe you can fake it till you make it that way too, and then hire staff to clean it up 2 years later :)

Reply on news.ycombinator.com