It really is. Just because some people have a uncanny propensity to mix concerns that shouldn't be mixed, that doesn't mean that a data structure is something else.
> The browser has no real concept of "page navigation" or "site navigation" with any kind of state, or the "current" navigation item, or of hierarchy, breadcrumbs, menus, or other core navigational concepts involving site and page structure.
Why do you believe the browser should support that with primitives? Advocating for that kind of specialization lies somewhere between forgetting important and basic historical lessons on software engineering or an unsubstantiated belief that now everything will be different.
> A large part of "knowing about usability" is just knowing how to execute these basic navigation features without goofing up on the many pitfalls available to you.
You're leaving out a part where said usability principles lie somewhere between emerging requirements that are still under development or fads that are scheduled to be replaced with the latest and greatest promising idea.
Suffice to say arguing to force them into browser as primitives is demanding that they should be set in stone as is.
I would go even further and state that TIOBE is deprived of any meaningful value. It's basically a index that tracks web noise. I mean with TIOBE, C++'s ranking goes up if someone writes a blog post with a joke that goes "A C++ developer walks into a bar...".
I wouldn't be surprised if this post in HN is contributing to the bump.
TIOBE is what you get from garbage-in.
> I wouldn't put much stock in this and I like C++.
I would bet that C++20 led some bloggers to post random stuff with C++ in it.
Once I bought from Amazon a pack of 4 or 5 USB cables from a seller which had good reviews. Once they arrived, they all broke in a matter of 2 weeks. I mean every single cable in that pack was busted after 2 weeks of use.
Based on my infuriating experience with the product I posted a 1 star review stating that all cables broke. After a week or so of posting that review I started to be spammed by the seller with offers of a 10$ or 20$ refund and a brand new pack of USB cables provided I recanted my review. By spam I mean the seller sent the same canned response about 7 or 8 times repeatedly bribing me to recant my review.
I'm not sure what's your personal definition of REST but REST according to Roy Fielding's definition is an architectural style that helps design APIs that are as loosely coupled as it gets. In fact, I'm not sure what style of APIs you feel improves upon REST on this criteria.
I don't believe this is up for discussion: the circuit breaker is a device that is designed and used to protect a circuit against fault conditions. That's the whole point of their use: if a fault condition is detected, the circuit breaker breaks the circuit to about the fault to propagate or damage the circuit and/or any device connected to it.
> What many fail to understand is that disinterest in Github absolutely does not tell you anything meaningful about that programmer.
Well, it does. It says he doesn't have a portfolio for some reason. Is it because he is incompetent and has nothing to show for? Perhaps not, but if the candidate makes it difficult for recruiters and interviewers to get an objective way to corroborate his claims regarding his level of expertise then just for the sake of avoiding wasting your time with yet another paper tiger... It would be better to cut him out of the shortlist for further interviews.
>> Well, it does. It says he doesn't have a portfolio for some reason.
No, you do not have to have a "reason" for not having a public portfolio. Not having a public portfolio doesn't say anything at all about someone's competence.
>> if the candidate makes it difficult for recruiters and interviewers to get an objective way to corroborate his claims regarding his level of expertise
Public code is not the only way to assess skills, indeed as I mentioned elsewhere in this thread its actually a pretty bad way to assess skills. If the best tools you have for assessing competence is github then your recruiting process is lacking.
>> It would be better to cut him out of the shortlist for further interviews.
I can imagine employers with this attitude lamenting how hard it is to find good people.
> In my case, I have found trying to contribute to open source to be a huge waste of time.
You mentioned the full extent of your attempt at contributing to open source consisted of a grand total of two meager pull requests.
I'm sorry to say but if throughout all those years you only managed to put together two patches then quite obviously you did close to zero contributions, both in absolute and in relative terms.
In fact, it seems you complain more about floss than actually contribute stuff.
I find that I general it's terribly easy to get your pull requests accepted to random FLOSS projects. Whether your PR is janitorial work, fixing bugs or adding features, you don't need much work to get your contribution in. So, quite frankly it sounds like you are grossly exaggerating and overstating not only the extents of your work but also the challenges you supposedly face.
> Then there's the issue of dependencies. My cool tool for analysing satellite photos won't be of much use to anyone who doesn't have API access to a satellite ground station.
In that case your so called cool tool to analyse satellite photos sounds very poorly designed. I mean, the whole FLOSS earth observation stack is designed literally from the ground up with extensive separation of concerns in mind (see GDAL and proj4 and orpheo toolbox for example) and apparently somehow you failed to learn the lesson that everyone doing professional, academic, and even amateur work knows by heart.
I'm happy to report that of course I sent in much more PRs and some even got accepted, but I highlighted one that didn't as an example of why it feels like a waste of time.
Similarly, I've had unpleasant experiences with entitled users more than once, I just picked the Heroku buildpack randomly.
As for the satellite tool, open tools will only take you so far. I do use GDAL, for example. But when you need to take photos on demand, you need very precise real-time trajectory and weather data, for which there is no free equivalent. Plus you actually need to send your photo request somewhere. And that's when you become dependent on an NDA-ed proprietary API.
There's good open source tools if you want to do offline analysis of static archive images. But not everyone has such relaxed requirements for refresh period and processing latency.
Consider using satellite photos to analyze traffic. You schedule photos with a proprietary API, use proprietary modules to download them, followed by proprietary file format converters. And then there's a block of image processing that I could open source, but that won't be helpful without the data acquisition and conversion pipeline. But actually it's a TensorFlow AI trained on proprietary data, so even releasing that is a legal nightmare. The whole project is commercially tainted from start to finish.
It really is. Just because some people have a uncanny propensity to mix concerns that shouldn't be mixed, that doesn't mean that a data structure is something else.