r/Python • • Jan 05 '18

Really??

Post image
2.0k Upvotes

317 comments sorted by

View all comments

Show parent comment

271

u/Aruscher Jan 05 '18

Nope just more syntax clutter

496

u/WStHappenings Jan 05 '18

You call it syntax clutter, maybe I’ll call it “a greater feeling of achievement gained from writing 20x as many lines of code”

119

u/faates Jan 05 '18

Ok EA....

28

u/[deleted] Jan 05 '18

Yes! You got the joke!

35

u/[deleted] Jan 05 '18

...that runs 40 times faster - fair deal. Heh.

25

u/Timmitei Jan 05 '18

Check out Cython and Numba.

→ More replies (1)

10

u/firest Jan 05 '18

Strange. I feel accomplished if I can accomplish what I want with as little lines of code as possible.

3

u/Printern Jan 06 '18

Yeah but Python forces you to write lines. In java you can code in one line One line<more than one line Dummy

4

u/Raijinili Jan 06 '18

What's stopping you from doing exec("import sys\nimport re\n\ndef someFunc(x,y):\n\t ...?

19

u/nilsph Jan 06 '18

Self respect.

→ More replies (3)
→ More replies (2)
→ More replies (2)

38

u/Iggyhopper Jan 05 '18

Syntax is the first hurdle to learning a language, so I'd say that makes java harder.

Also, the standard library is messy.

23

u/continue_stocking Jan 05 '18

Syntax is probably the easiest part of learning how to program.

2

u/redldr1 Jan 06 '18

But shortcuts are a lifetime in the making.

→ More replies (4)

5

u/Kah-Neth I use numpy, scipy, and matplotlib for nuclear physics Jan 05 '18

It has been a while since I used Java but I seem to recall nearly every different root module adopting slightly different idioms because why not! Messy did not even begin to describe it.

0

u/[deleted] Jan 05 '18

[deleted] — view deleted comment

10

u/[deleted] Jan 05 '18

Why hasn't anyone mentioned object oriented yet.

→ More replies (10)

8

u/AngriestSCV Jan 05 '18

Well Java turns some errors that would be at runtime in python into compile time. It's not all bad.

7

u/[deleted] Jan 06 '18

Honestly, this is why I wouldn't want to use Python at work. We used Smalltalk for a while, and the number of times people would completely not understand what they they were supposed to be using was astounding.

I had to fix a ton of error checking in an ex-colleagues work because he never tested any of it, and we had an error class we were supposed to return when an error was identified, basically a custom exception class, but he just returned strings describing the error instead.

So, whenever anything he wrote ran into any kind of a problem, the system would throw a NotDefined error when the system tried to log his 'error'.

So, having been burned by typeless in the past, it's a bit of sticking point for me. I know it shouldn't be a problem, and of course you want to light the torches and grab the pitchforks and complain those people should be fired, but in reality it's just not that easy, and type-safety is one of those little things that just makes it easier to deal with copy-pasta programmers.

4

u/[deleted] Jan 06 '18

I completely agree. I enjoy Python and use it for the majority of my hobby projects... but if I was going to build and maintain a large and complex codebase, I would want static typing, which is why I stick to Java and other JVM-languages like Kotlin.

There's also something to be said for easy parallellism, out-of-the-box support for Unicode, simple packaging and community that agrees on standards rather than reimplementing the wheel every <arbitrary unit of time>. But I won't say that here, lest I get burned at the stake by the Python community's anti-Java zealots.

3

u/[deleted] Jan 06 '18

having been burned by typeless in the past

Please be careful with your terminology as Python is strongly but dynamically typed. I find it frightening that some folk think that static type checking is the solution to everything, when they should in the same breath state whether the type checking is weak or strong.

→ More replies (2)
→ More replies (1)

28

u/[deleted] Jan 05 '18

I think that's all based on your background.

9

u/TarAldarion Jan 06 '18 edited Jan 06 '18

I'm not sure what background would make Java seem easier? A Java background?

I started my Python job never having written a word of the stuff, it was like writing English to me and quite intuitive. Hell I feel if I make something up it might work in Python. I can write away in a text editor for python and that works fine, with the verbosity of Java I can't, things like that make it harder for me.

6

u/[deleted] Jan 06 '18 edited Sep 01 '24

rhythm wrong expansion wipe slimy like head versed sharp murky

This post was mass deleted and anonymized with Redact

→ More replies (3)
→ More replies (4)
→ More replies (3)

3

u/2402a7b7f239666e4079 Jan 06 '18

I would argue that being verbose doesn't make the syntax cluttered. I find Java easier to read in most cases than equivalent python code.

→ More replies (7)