My approach to building an open-source data tool: Python vs JavaScript (dev.to)

submitted 8 months ago by gecloslatitude@lemmy.world to c/python@programming.dev

4 comments fedilink hide all child comments

Hi there 👋, I’m Gerard, founder of Latitude.

I have written an article on how I approached building an open-source data tool. I had doubts about Python vs JavaScript, but I’m happy with the path I chose.

Would love it if you guys give me any feedback!

you are viewing a single comment's thread
view the rest of the comments

[-] NostraDavid@programming.dev 10 points 8 months ago

I'm confused why you're asking for feedback. You already chose Svelte and Sveltekit, no?

Here's my feedback anyway: I like Python and dislike Javascript. Yes, Python is slow (though that can be offset via Pandas, among other libs) but it's relatively painless. Unlike JS, which is quite painful to work with. JS libs also come and go every few years, whereas Python's seems a bit more stable in that regard.

But it also depends on whether I'm part of your target audience - who is your target audience?

[-] TGhost@lemmy.blahaj.zone 2 points 8 months ago

Doing scripts for my needs and fun. I would never do JS except in the web browser console for "ez stuff" without external libs...

For me python, the way to go ! :).

The last things confirmed me this ?
"Lemmy-client-JS" vs "plemmy".

[-] balder1993@programming.dev 1 points 8 months ago

Not having a standard library is what hindered JavaScript, mostly because of its origin as a browser language. The dev environment is already bad with many competing options that don’t always play nice together, now imagine that sort of problem even for the basic libraries.

Python quite often have more than one library to do the same thing, but they’re often extra niceties.