1y ago

What are your programming hot takes?

You're viewing a single thread.

896 comments

Dynamic typing is insane. You have to keep track of the type of absolutely everything, in your head. It's like the assembly of type systems, except it makes your program slower instead of faster.
- Nothing like trying to make sense of code you come across and all the function parameters have unhelpful names, are not primitive types, and have no type information whatsoever. Then you get to crawl through the entire thing to make sense of it.
- I'm not sure that's a hot take outside early uni programmers.
- You can do typing through the compiler at build time, or you can do typing with guard statements at run time. You always end up doing typing tho
- I like it in modern PHP, it's balanced. As strict or as loose as you need in each context.
  Typed function parameters, function returns and object properties.
  But otherwise I can make a DateTime object become a string and vice-versa, for example.
  
  What happens when you coerce a string to a date-and-time but it's not valid?
  Where I'm from (Rust), error handling is very strict and very explicit, and that's how it should be. It forces you to properly handle everything that can potentially go wrong, instead of just crashing and looking like a fool.
  
  My point is, you won't ever try. You'd only use "weak" variables inside the function you're working on.
  It's explicit when you absolutely need it to be, when the function is being called and you need to know what arguments to pass and what it'll return
  
  A string being parsed as a date-time is presumably user input, which is potentially invalid.
  
  When you say user, you mean a user of a function? In that case PHP would throw a TypeError, and presumably only happens when developing/testing.
  If you mean in production, like when submitting a form, an Exception may be thrown. In which case you catch it and return some error message to the user saying the date string is invalid.
  
  By “user” I mean the person who is using the application.
  Using exceptions for handling unexceptional errors (like invalid user input) is a footgun. You don't know when one might be raised, nor what type it will have, so you can easily forget to catch it and handle it properly, and then your app crashes.
  
  you can easily forget to catch it and handle it properly
  Even if I coded the form by hand and that happened, it's on me, not on the programming language.
  But I don't, I use a framework which handles all that boilerplate validation for me.

896 comments