Re:Fish (shell) porting to Rust from C++
by shaklee3 on Tuesday January 31, 2023 @10:35AM
(#34596384)
The claim being made in the original post and subsequent posts is that c++ is losing popularity. this claim is not true, and all evidence points to it gaining in popularity despite the HN echo chamber that it's too hard.
Re:Fish (shell) porting to Rust from C++
by nindalf on Tuesday January 31, 2023 @10:51AM
(#34596653)
I still see you didn't read what I wrote. Please, just take a moment to read before firing off a comment.
I didn't make the claim that C++ is losing popularity, but I did mention some sources that do. These are marginal, not dramatic declines. Certainly not a terminal decline.
- Number of people searching Google - https://trends.google.com/trends/explore?date=2012-07-31%202...
- Number of questions asked on StackOverflow that month - https://insights.stackoverflow.com/trends?tags=java%2Cc%2B%2...
A far cry from the claim that it's "dominating and gaining", as you said.
Re:Fish (shell) porting to Rust from C++
by throwaway894345 on Tuesday January 31, 2023 @10:52AM
(#34596679)
The original claim is "C++ is becoming a legacy language". This is clearly a claim about the trend of C++'s popularity over many years. You're trying to refute that claim with a single data point about one year, which isn't sufficient to refute a trend. For example, a single bad day in the stock market doesn't refute the claim "the stock market is trending up over the year". Moreover, your data point is probably just noise--a 4% swing when the error margins are closer to 50%. TIOBE is basically just guessing, and a guess isn't evidence.
FWIW, I've been a professional C++ programmer, and I like C++.
Re:Fish (shell) porting to Rust from C++
by forgotpwd16 on Wednesday February 01, 2023 @06:43AM
(#34609230)
>You're trying to refute that claim with a single data point about one year, which isn't sufficient to refute a trend.
Below the list a graph showing the ratings over a 20 year period is provided. It shows C++ declining until about ~2017 but recently starting rising again.
I see you didn't actually read the link I pasted, especially not the section "Evaluating languages for projects". There's several possible ways you can compare (StackOverflow survey, JetBrains survey, GitHub PRs, StackOverflow trends, Google trends) but ultimately it comes down to what's a good fit for your project.
- Can developers be hired/trained to use it?
- Will they be happy using it?
- What will our development velocity be on this language? What will be the operational burden of keeping it running in production?
- Do we need to rely on third party code? Does that code already exist and what is its quality?
Only your team can answer these questions for your project in particular. It depends on your business problem, your local jobs market, your engineering budget.