Likewise, especially since "competitive" is such a huge range. As an example, if I'm currently making $100k, I might entertain a position at a slightly interesting company that's offering a "competitive" salary of $95k. However, I don't think there's anything that would make me go through the hassle of interviewing for a job paying a "competitive" $60k.
Basically, posting the salary range gives me a quick and easy way to weed out those companies which aren't serious without a significant investment of my time.
A range would at least give me a good idea of whether the salary is more or less than what I'm currently getting paid. If the high end of the range is well below my current salary, I know I shouldn't waste my time. "Competitive" can mean just about anything, so it gives me absolutely no information.
(Elixir/Phoenix || Node.js/Meteor || Ruby/Rails) && (Angular.js, React, Homegrown JS frontend stuff), as well as desktop stuff with JS (my "lib": https://github.com/Anonyfox/node-webkit-hipster-seed ) from time to time. Actually I'm fluent in many languages so the concrete choice doesn't matter really as long as it is suitable for the given problem. But today there is no question where the answer would be PHP. Especially when the future is "soft" realtime, distributed and high performant or for tiny devices, problems you can't throw more hardware/caches at.
Basically, posting the salary range gives me a quick and easy way to weed out those companies which aren't serious without a significant investment of my time.