Hacker News new | ask | show | jobs
by richo 4631 days ago
I don't know why he's trying to turn this into some deepseated thought about "knowing your boundaries". It seems to me like his whole point is that naively templating one language with another is a bad idea (is is).

When I read the linkbait title, I implicitly thought "writing code? FIND your boundaries". Think threading is simple? Write something nontrivial with threads. Discover how outrageously hard threads are!

1 comments

Point taken, I can understand the confusion based on the title. I'm referring to risk of boundaries between technologies causing people to choose the wrong tool for the job. In each example there are two ways to solve the problem. I'm simply arguing to stay native.