Managing a node project is like juggling twelve barrels full of monkeys… and those monkeys have rabies. Trying to keep all your dependencies in line is insane.
It is absolutely insane to me that people rag on the Python packing ecosystem when TypeScript exists. Sure, Python’s not perfect (Rust and Go seem better, from the small amount I’ve dabbled with them), but way easier and more stable than any TS project I’ve worked on.
Typescript is a language, Node is a platform and framework. You can use Typescript in your Node project, they’re not mutually exclusive.
The way I see it Typescript is more popular than ever, almost all (popular) libraries come with types and every job offer I get they use Typescript.
And with good reason, our team recently took over a small Javascript app and there are tons of bugs that would never have existed if they were using Typescript. Things like they refactored something but missed to update a reference, or misspelled a variable name, failed to provide a required parameter to a funcrion, referenced a field that existed in another config object etc.
It’s about time JS gave us the ability to be strict on types, and have that as part of the interpreter as opposed to needing to transpile TS with the overhead involved
I’ve had this experience in other languages, but never python. Find the missing semicolon and getting a cryptic error message is a very common programming experience.
The reason I never had this problem in python is that by the time I learned it, I was already a fairly experienced developer, and I used better tooling from the get go. This kind of error is reallllllly hard to make in a modern IDE using a linter and formatter.
That suggests to me that this is more likely a fairly language agnostic experience. It might even bias people against the languages they learn first.
I mean, I guess, it depends on your perspective. Some folks work in garbage/proprietary languages all day and would be very glad to have Python-levels of compiler help. Others work in JS/TS and do have similar nonsense to deal with as in Python.
But lots of languages, e.g. JVM languages, Rust etc., don’t struggle with semicolons and the like.
And they don’t have to compile at runtime, so they can easily outclass Python for more complex error reporting, which is at least my experience.
Personally, I have pretty much only had the experience of “tell me where the error is” in Python and TS.
I’ll always appreciate Lisp for the most powerful REPL in existence of programming languages by a long shot. Name me one programming language that empowers developers to troubleshoot and fix runtime errors with high availability like Lisp does:
Meh, who cares. Let’s continue to run.
Here’s a REPL with the app state at the time of the runtime error. Happy debugging!
Fix the bug in production inside of the REPL while everything continues to chug along.
Save the changes to disk and check it into version control.
The REPL in Lisp is so powerful that there’s an entirely different approach to developing apps in Lisp. You can, and some do, code everything inside of the REPL. When they’re done, they save the file to disk.
As someone who has taught people a variety of languages. No. This happens regardless of what language you choose. It’s just a universal programmer experience to get frustrated at your work
This sounds like they did not or could not explicitly compile it. Pretty much all popular languages are compiled. JS isn’t, but people are less likely to say that they ‘run’ that one. Ruby isn’t, but it’s not as popular as Python.
Well, and my preferred version of “everything looks good” is “everything compiles”, which with a strict enough language does also make failure during the first run much less likely.
I’m also not saying that these aspects are unique to Python.
The language failing to tell you where the issue is also happens in JS/TS, C/C++ and I’m going to presume Ruby, too.
Python is just again rather popular and some of these choices don’t make sense with my first hunch.
Honestly man it just sounds like you have struggled with dynamic languages and by extension prefer static (compiled) ones. Which is totally fine you don’t have to like everything. But I do think you’re missing the real issue with “everything looks good.” It’s a lack of experience with the tool. It doesn’t matter if you’re using something as strict as Rust or dynamic as Lisp. “Everything looks good,” is always bad. You should know “this is how this works,” which is just not something a newbie can handle when they still don’t know the difference between pass-by-reference and pass-by-value (or that those words even exist!)
programmerhumor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.