5 ms·
> But don't use This is just cargo-culting static typing: "If I avoid dynamic typing at all cost, the cargo crates will surely rain on down!" You'll find that
by hombre_fatal 6y ago
> But don't use
This is just cargo-culting static typing: "If I avoid dynamic typing at all cost, the cargo crates will surely rain on down!"
You'll find that picking a language is more of a business decision than the sort of technical static-vs-dynamic checkbox test you might use to pick the language of your next weekendware.
This kind of absolutist rule of thumb is more flame bait than morsel of wisdom.
- lmm 6y agoThis is the fallacy of the grey. Yes, there are nuances and special circumstances, but the overwhelming majority of the time, static typing is simply better. That's one of a small handful of clear consensuses from the last 20-30 years of programming language evolution.
- hombre_fatal 6y agoIt's not any better if business trade-offs make another decision better. You don't have "all things equal" trade-offs in the real world. Want an easy concrete example? You and your cofounder have 10 years of Ruby experience and investors/customers who want a product yesterday. Or the deliverable that makes most sense is a PHP script that users can drag into CPanel because that's your customer base. The tinkerer inside you always wants to try new things and convince you that some greener tech on the other side of the fence are going to make the difference. It's usually just procrastination from the actual hard stuff: building things people want, today.
- lmm 6y ago> Want an easy concrete example? You and your cofounder have 10 years of Ruby experience and investors/customers who want a product yesterday. Or the deliverable that makes most sense is a PHP script that users can drag into CPanel because that's your customer base. True but facile. Sure, for every imaginable technology, there is a conceivable scenario in which that technology is the right choice. Doesn't mean there's no such thing as a good or bad technology. > The tinkerer inside you always wants to try new things and convince you that some greener tech on the other side of the fence are going to make the difference. It's usually just procrastination from the actual hard stuff: building things people want, today. That's actually an argument for being more absolutist about the technical side: you're unlikely to be in the obscure circumstances where a dynamic language would actually be helpful, and even more unlikely to have that be more important than your business decision. So rather than carefully considering your circumstances and weighing up the tradeoffs, it's better to follow the consensus for what's a good general-purpose language (which these days means a statically typed language) and get on with building your business.
- anyfoo 6y ago> It's not any better if business trade-offs make another decision better. I'm sorry, but cleaning your windows with Windex instead of tap water is then "not any better if business trade-offs make tap water better". I am just not sure what you are arguing for: Static typing is better, except for when you don't have static typing? Some folks here are in the position to choose their current, or shape a collective future landscape, and for those static typing is a consideration. You mention PHP a few times, but I think this is actually a good example for something that has been pushed away in favor of better things. My impression is that at least the bigger software corporations have moved away from PHP if they ever used it to begin with. Even Facebook, one of PHP's biggest users, replaced it with their own so-named "Hack" eventually, which is apparently a PHP-derivate with "both dynamic typing and static typing" according to Wikipedia.
- pmontra 6y agoMy experience is similar (Milan, Italy.) If a company is small and/or has to rely on freelancers it goes with dynamically typed languages (PHP, Node, Ruby, Python and Elixir) because that's what the bulk of freelancers use. If they have many internal developers or use big consultancy firms they go with Java or C#. Of course there are exceptions (I know a few of them) and my point of view can be biased because I use to see projects and developers of dynamically typed languages. But I know a few small companies with a code base in Java that had a hard time at finding Java freelancers. Almost all of them are employees, unreachable for them.
- anyfoo 6y agoA business decision, what drivel. By that argument, no technical merit of anything ever matters, and yet many things of what’s considered viable in a “business” have changed all the time, some of them because of the push of engineers towards better things. This is a forum for engineers (not only, I know), who collectively will at least have a large part in steering what languages are considered common in future.
- memexy 6y agoI actually don't pay any attention to what HN considers technically valid. Collective opinion among HNers is often very skewed from the actual reality. Here is a comment from 9 years ago. It sounds like parody to me and demonstrates how echo chambers eventually deviate from reality. HN can often be an echo chamber > A good programmer should wake up at 6 am in the morning get a solid 2.5hrs of coding done by 8:30 am, at 8:30 leave for work, work till 6 (it goes without saying that the lunchbreak must be spent trying to learn the Haskell or if you are feeling lazy answering questions on stackoverflow). Commute from 6 to 6:30 (it's a bonus if you listen to a technical podcast during this time and no stuff like TWIT does not count, perhaps audio lectures from the Advanced Algorithms course on MIT OCW). 6:30 to 7:00 time for supper and excellent time to catchup on r/programming and hackernews. 7-8:30pm is the time for relaxation by doing some recreational mathematics, doing problems from project Euler and that proof from The Art of Computer Programming excercises which you have been itching to get a go at! 8:30pm to 1 am code contribute to that open-source project, write patches for the Linux kernal and continue working on your startup. > Anyone who does less programming that what is mentioned above cannot call himself a "good programmer", I would have serious reservations in calling that person even a mediocre programmer. -- https://news.ycombinator.com/item?id=2664409 https://news.ycombinator.com/item?id=2664409