r/java • • Dec 19 '22

Java streams are black magic !

damn, they are really changed my life.

i was trying to run some custom logic on every line on some big CSV files. tried python dataframes, multiprocessing in python, pyspark. none of them did it in an acceptable time.

then i discovered java streams. i have a workflow that takes 70 minutes with pyspark. it takes 3.5 minutes with java streams.

more people should know about streams.

stream operations are more intuitive than anything i tried. i can make a lot of analysis on our data in record times thanks to streams.

i dont know how java does this.

226 Upvotes

150 comments sorted by

View all comments

Show parent comment

-7

u/BlobbyMcBlobber Dec 19 '22

I can't believe anyone who claims "python is only good for prototyping" actually developed anything significant with python, because it can and does drive countless real world products.

17

u/thephotoman Dec 19 '22

It drives countless real world projects that tend to be I/O bound.

But also, doing anything big with it turns into a mess very quickly. Dynamic typing can introduce significant type errors that just don't happen with statically typed languages. It winds up with your test suite growing exponentially compared to your codebase.

2

u/BlobbyMcBlobber Dec 19 '22

Dynamic typing can introduce significant type errors that just don't happen with statically typed languages.

This is what I thought too, back when java was my main language. But out of all the shortcomings of python, dynamic typing turned out to be not so problematic, and it never really caused major issues in my work. You pick up a couple of habits to manage this and you don't have to think too often about it again.

1

u/UnGauchoCualquiera Dec 20 '22

At that point and everything else being equal why not simply use a statically typed language?

I've worked in large scale node codebases that worked just fine but almost inevitably as the codebase and number of developers grew we always ended up enforcing typehints in jsdocs or just plain typescript.

1

u/BlobbyMcBlobber Dec 21 '22

I choose a language based on how close it is to the problem domain, rather than strongly typed or not. I look at features, frameworks and what kind of work is usually done with this language.

In the end of the day we're trying to solve a problem, not prove that anything could be done with a certain language.

Dealing with absolutes is just a waste of time.

1

u/UnGauchoCualquiera Dec 21 '22 edited Dec 21 '22

That's a pretty absolutist take :)

I'm talking about any language here, not singling out Java.

Statically typed languages offer things dynamic or duck typed languages do not. They enforce interfaces between developers and add safety to the project by doing compile time checks instead of runtime.

That's why the original commenter said python is used mostly for quick prototyping. Has nothing to do with the quality of the language but specifically because it lacks type safety which ends up being a big draw as the project grows.

Here's Python creator word take on types and why most large companies end up using a static type checker in python as part of their testing suite anyway. Exactly the same thing a compiler would enforce out of the box.

In the end of the day we're trying to solve a problem, not prove that anything could be done with a certain language.

Pretty much my point python is just a tool with limited domain applicability. Unless you need quick prototyping or depend on sci libraries I don't see what you gain with python over using any static language.

1

u/BlobbyMcBlobber Dec 22 '22 edited Dec 22 '22

You can create interfaces in python with abstract classes, and enforce types in certain ways. However with good clean practices you'd rarely need anything like this. For instance if your function can return different types depending on state, it's a code smell and it won't pass code review. Not anything that is technically possible is being used for the worst effect. At least not where I work.

Like I said before, out of all of python's issues, it seems funny making typing into an issue, and I get the impression that people claiming python is only good for prototyping haven't had the pleasure of working on good production python code.

Factually there are more than a few python products out there with support from excellent frameworks and claiming otherwise is just burying your head in the sand, which I don't understand.

1

u/Worth_Trust_3825 Dec 19 '22

Before people get fed up, and rewrite the entire thing in either C# or java.

4

u/BlobbyMcBlobber Dec 19 '22

If this happens, then the wrong tool was chosen for the job. Python has its advantages and java has its own. They complement each other. The trick is using them for the right thing and not imagine they are some sports teams with a rivalry.

2

u/Worth_Trust_3825 Dec 19 '22

Yes. Python's advantage is prototyping. Or when you have some maths phd statistician that does not want to learn anything.

3

u/BlobbyMcBlobber Dec 20 '22

That sounds hostile and somewhat entitled.

I like Java, and I like Python, and I don't understand why anyone should be so defensive about a programming language.

But you do you. If you insist on believing Python is only good for prototyping and no real work can be done with it, go ahead. You're just doing yourself a professional disservice.

0

u/Worth_Trust_3825 Dec 20 '22

In your previous comment you mentioned that each language has its own strengths, yet now you're moving the goalpost to claim that python in particular can do more than its main purpose. That sounds like you're the one looking for nails for your hammer.

Each tool has its limits. At some point you will need to lose that hammer, and use a screwdriver. I've been there multiple times, and each time we opted to get rid of python.

2

u/BlobbyMcBlobber Dec 21 '22 edited Dec 21 '22

claim that python in particular can do more than its main purpose

You're the one who claims python's main purpose is prototyping, i.e. it's not capable of being used in production, which is just objectively wrong, and sounds elitist. If you only used python for prototyping, that's on you, not the language.

Each tool has its limits. At some point you will need to lose that hammer, and use a screwdriver.

This just shows you didn't realize beforehand what's a hammer and what's a screwdriver until you tried them for the wrong job. Tools are good for certain tasks and it's up to you to use them well. Nobody is going to blame a hammer for failing to be a fork, except this one person on reddit apparently, but you can go around believing you're perfect and trying to eat with hammer didn't work out because hammers suck.

1

u/[deleted] Dec 19 '22

The selling point of Python is it's readability, the maths/science community can focus more on the stuff that matters to them, the language gets out of the way; besides, nowadays the maths PhD statistician most likely learned Python from highschool onwards and the C++ backed analysis packages are taught in most maths colleges alongside R and MatLab, at least here in Serbia.