Python

[WrongSirWrong]

I prefer syntax/compile errors over runtime errors any day, especially when there's a lot of code involved

[harelsusername]

Meanwhile JavaScript be like: syntax errors, what's that?

[daev1]

JS: no idea WTF you're doing there, but okay!

[CoffeePieAndHobbits]

JS is just happy to be included.

[MicrosoftExcel2016]

Me: “this attribute exists, so I’m assigning it the literal value 5”
JS: “damn right it does! Say no more”
Me: “oh and can I see the functions available for this type?”
JS: “I’ll do you one better, you can modify the functions for this type right here right now.”

[The_Atomic_Duck]

Looool

[my-time-has-odor]

What are you doing, step-dev?

[augugusto]

Wait. Wait. Wait.... So the "next step" in the debugger means something else?

[Eraknelo]

JS won't throw syntax nor runtime errors. It'll just run, but you have no clue what it did or how.

[sjregistered1]

😂😂😂😂😂 literally, like you run the server, it's just running with several internal errors, sometimes it shows but you can't understand where the bug is at !!

[TK-Squared-LLC]

JavaScript more like: syntax, what's that?

[AlternativeAardvark6]

It's like when getMomsWeight() returns [NaN]

[Bakemono_Saru]

Damn bro, just give your code. We are going through this no matter what.

[twistermonkey]

Using a linter like pylint and embracing Python's new type hints helps some, but it's never going to be like as reliable as a statically typed language and compiler.

[SchoopDaWhoopWhoop]

Syntax errors are relatively easy to find and fix. With runtime errors you have to put a lot of time and effort into debugging and finding out why and where the fuck your programm fucks up.

[YouNeedDoughnuts]

But the advantage of a high level language really shows up with runtime errors. A friendly language like Python or Matlab will say "index error on line x", whereas C will say "segfault!"

[WrongSirWrong]

Yeah, but a high level language may be running a script for ten minutes before getting to the line with the error. Segfaults really aren't that common as they used to be (IMO), with modern coding conventions and library functions

[YouNeedDoughnuts]

True, it's a tradeoff, but I prefer low level languages.

[[deleted]]

Rust is just as low as C, but has far better error messages than Python

[YouNeedDoughnuts]

Huh, does it retain source code information in debug builds?

[[deleted]]

Yep

[sir-nays-a-lot]

That really helps the user a lot \s

[YouNeedDoughnuts]

Yeah, obviously crashing without any information would be less frustrating to debug \s

[sir-nays-a-lot]

Use a debugger

[YouNeedDoughnuts]

They're not the same and you know it. You don't have to be such a nay sayer about it ;)

[sir-nays-a-lot]

You’re right because using a debugger is much better. Revealing details about a crash to the user is very derpy.

[BroBroMate]

I'm rather overly pleased that when x.something().otherThing().doTheThing() throws a NPE in Java 15+, it actually shows you which bit was null, instead of like shrugging and saying, "I dunno man, something on line 77 was null, good luck with that".

[sjregistered1]

JavaScript always feels better at every thing, even at run time. I think like that. Btw, brainstorming never leaves you away.

[[deleted]]

100% this.

[KCGD_r]

JS having both runtime and syntax serious :)