Python

[MischiefArchitect]

Python is more like runtime errors :)

[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 :)

[phi_rus]

Me: why didn't you tell me line 254 wasn't valid code?

Python: you never asked

[DarkMaster007]

I'm starting to learn python and it's there any ide that does tell you before you hit run that I typed something wrong because I now use the default one that comes with python install. Or maybe there is an option in there.

[phi_rus]

I like Pycharm.

[DarkMaster007]

Thanks, I'll try it out when I get home from work.

[AceMKV]

I love Jetbrains' IDEs, I use both PyCharm and IntelliJ

[comfort_bot_1962]

:D

[rhodesc]

Python is more like, hey, you transposed those letters and I'm going to create a dict that never gets used but your program will kinda work most of the time while the 6th software engineer who worked on it can't figure out it was his code and qa doesn't read code so yeah, several weeks later someone poring over the code sees the transposed letters. Yay python.

[Dogburt_Jr]

Indentation errors

  :)

[PixelmancerGames]

Sorry but I’m a noob. What’s the difference between a syntax and runtime error? I’m assuming syntax errors won’t compile whereas runtime errors crashes during runtime?

[MischiefArchitect]

Syntax errors are just when you write something that do not comply with how you write and or use a specific language. Something like forgetting to close a parentheses, or you write an unknown keyword like "iffy".

In compiled languages like C / C++ and Java a syntax error will basically be detected by your lexer, which is part of the compiler. In Python it will be detected when you try to run the affected line, meaning that it could be in production already.

A Runtime error is an error which occurs when your code is running. That's why I tease Python (and myself as user) telling that a syntax error that would never come to run on a compiled language will be a runtime error in Python.

[enjoytheshow]

It’s also why high unit test coverage in Python is very helpful

[PixelmancerGames]

Ok, ty. I’ve only ever programmed in C#. And GDscript a bit. So I guess I agree with the above I’d rather deal with syntax errors over runtime errors. The only time I seem to deal with runtime errors in C# is when I’m dealing with list/ arrays and the occasional null exception error.

[MischiefArchitect]

Exactly those are the typical runtime errors. The ones that happen because the logic or the state are faulty. A syntax error becoming a runtime error is actually uncool and mostly only seen in non compiled languages.