3 ms·
A true coder wanting to implement things near correct with algorithm complexity (big O), will try to find how to implement the right code by taking time to rese
by jjm 11y ago
A true coder wanting to implement things near correct with algorithm complexity (big O), will try to find how to implement the right code by taking time to research understood and time tested patterns they've learned (it is an applied science after all) and implement them.
Saying the average joe doesn't care to understand what his/her Lang is doing under the hood which will doom them to repeat complexity that many here will respond with "duh" is not justification that a Lang is better - because it supports that behavior "better".
I don't know erlang that well but I'll be damned if I don't spend the time to find out how to properly do M:N with efficient tail recursion.
If one doesn't care for efficiency at all then who cares about benchmarks?
- hharnisch 11y agoYou missed the point. People aren't posting better algorithms, they're posting domain specific knowledge to improve efficiency. The kind of stuff that takes you away from building new features that add value. Benchmarking and efficiency is an important datapoint when picking a language. It's important to understand how un-optimized code performs too.
- jjm 11y agoIn my comment I support domain knowledge experts. In my comment I purposely mentioned erlang because to implement algorithmic efficiency you must have domain expertise. "I don't know erlang that well but I'll be damned if I don't spend the time to find out how to properly do M:N with efficient tail recursion." Tail recursion is an efficiency, doing it right in erlang requires domain expertise. Building new features and adding value is business. Someone with domain knowledge in any of the langs will be able to implement those business values in the best possible way. If your business is built with shitty coders doing shitty things you will eventually find yourself in hot shit. Even if it takes 5 years. What comes around goes around. I would take the domain knowledge developer over any monkey anytime. That's your 10x developer. That's who built all that awesome open source stuff you use all day. Not the business feature value guy. He builds businesses that fail 99% of the time. That other guy building that obscure Lang which turns out useful for that niche topic (I.e concurrency) lives on even in concept to build or inspire other langs/ers. You see, that domain expert knows to pick the right algorithm for the right job. He knows the right Lang for the right job. Even if that job is only business value. Long live domain knowledge experts and those who wish to attain it.
- bsaul 11y agoAbsolutely. Benchmark should be done with idiomatic code you'd like too see in a documentation. Not ultra optimized ones. At least not only.