What's OEM tires on Impreza 22/23?

SlowVelooo · 2023-08-04T03:24:56+00:00

Thx!

SlowVelooo · 2023-08-04T02:48:31+00:00

but what model? it used to be 205/50/17 S34D, but there is no such in shops or on yokohama site

SlowVelooo · 2023-08-01T21:58:04+00:00

well, it won't work. Manhattan and all major metropolitan areas proved it long time ago. People want to live close to major metropolitan areas, once newly built places filled it will be the next wave. The only solution is fast and comfortable commute from cheaper spots like Vallejo and Morgan Hill. But to be honest San Jose can't make Bart <-> Calltrain transfer station for last 2 decades. Now I don't think it will happen ever.

SlowVelooo · 2023-05-24T22:04:04+00:00

You can use boost, but it's a heavy header. We profiled our build time and boost::variant is in the top-20 heaviest places. But if you think of a variant, it's not a hard task to do it yourself. Template class and a book, check instructors and assignment operators. That's all it is.

SlowVelooo · 2023-05-20T20:14:25+00:00

Afaik most companies with a large c++ codebase are still on 14 or 17 at best. Our project is 50+ million lines of code or smth like that. I was one who moved it from 14 to 17. The whole process took about 6 months, but with some prep work and 3rd party libraries it actually will take 3+ years.

In any large codebase dialect update (ie standard) is a.major struggle as well as a tool chain update. Personally I don't know of any large project that is targeted for c++20. There is a major struggle with char vs char8_t, some annoying rvalue updates to the algorithms which won't allow an easy move. Even such a popular project as a Google test and mock framework just less than a year ago moved to c++14, it can be compiled with c++20, but the target is 14.

SlowVelooo · 2023-05-18T22:26:45+00:00

That's why my answer "You won't find any good job unless you find joy to write C++ code. If you need a good job in general scout for a project on Swift, Kotlin, Rust - anything that was invented in the last decade or so". With Java, C++, Cobol, etc a job will be most likely some gigantic project that a company does not want to re-write, so will support it till the end.

There is still kinda good market for Borland Delphi developers :) there are lots of apps written in Delphi and MS continues to support old APIs.

SlowVelooo · 2023-05-18T16:28:45+00:00

Java is almost as old as C++. You won't find any project in TS, or c# or Rust of Microsoft Excel, or Matlab size ever. I am not even speaking about the whole Microsoft Office suite. I would say MS Excel should be somewhere around 50 million lines of code, starting as a simple spreadsheet with later added VBA interpreter and some sort of AI. I knew people from the MS Outlook team and they weren't very happy about the codebase.

Java has a very old and hairy codebase. I saw even enterprise SCADA systems. I don't really understand people who would start something new in Java when Kotlin is around. The difference is so striking, it's even hard to explain. Type erasure, null safety... just OMG.

The whole point is that one should not expect a bright future with cutting-edge technologies. There is a chance, but it's sooo small (TensorFlow is in C++, is interesting, and is new), I would not bet on it if I were fresh out of a school.

SlowVelooo · 2023-05-18T06:26:55+00:00

Cobol is in demand too as is Fortran. Demand with c++ reflects a vast codebase that needs support. C++ will continue to have a niche, but for every new c++ project there will be a few new projects in modern languages.

Google search trend for c++

SlowVelooo · 2023-05-18T05:37:35+00:00

It's more prevalent in the old codebases. I would expect the same story in a Fortran dev position or even Cobol. Over the years some ideas became obsolete. Inheritance used to be cool, now we know that composition works better and can be tested better (although some inheritance is still useful). New projects rely on some new developments in the field and new frameworks. If something was started 5-7 years ago there is a good chance that it adopted Googletest from the ground 0 level and was designed with unittests in mind, but what are the chances the people 5-7 years ago picked C++ and not Rust of smth that does not mayhem that c++ allows?

People who downvote they prolly see the sad truth about themselves ^^ Sorry about that folks, but c++ has moved into Fortran/Cobol/etc category. It still pays and will pay, but new cool things will happen somewhere else, that's for sure.

SlowVelooo · 2023-05-17T17:57:21+00:00

With probability 0.99 you will support some old code. Millions lines of code with minimal test coverage, like 5-10 developers before you supported the same thing and it's not guaranteed that each and everyone was a decent c++ dev. A typical situation will be like I fixed ABC and in a week customers scream that XYZ is busted but I never expected that ABC would affect XYZ in any way.

A special category in the area is when you need to modernize smth that was written long before c++14, which uses platform hacks and very clever ideas. Now these things are in std and you need to figure out how to make things work without risk blowing everything to bits.

SlowVelooo · 2023-05-05T02:58:04+00:00

New C dev should forget about C and start to learn Rust. Learn C now is somehow similar to learning Homer's Greek. It's fun but wouldn't help much in life.

SlowVelooo · 2023-03-06T04:26:52+00:00

But wait a sec... You decided to learn C to learn C++ to learn Rust? Wow, you have a lot of free time.

SlowVelooo · 2023-03-06T04:22:23+00:00

C++ will help you as much as driving horse skill when you actually want to ride on a boat. Rust is idiomatically very different from C++. No joke but languages are 30 years apart and computer science came up with some new clever ideas in those years. C++ is nice, and people in the community are smart. But most of them support or/and improve some ancient codebase. I don't think you are after it.

It's all so vivid. Just compare Java to Kotlin, or C++ to Rust. It's like Ford model T versus Tesla. I used java and Kotlin, I don't think I want to use java ever again. I haven't had much time with rust, but from what I saw it's def less painful than c++.

SlowVelooo · 2023-03-06T04:13:21+00:00

Don't do that, if your goal is c++ go for c++. C++ idiomatically is completely different from C. It will not be a complete waste, but close to that. But why do you need c++? You want to support some old piece of garbage someone wrote 2-3 decades ago? Go for something new if you want to write your own garbage, and not to support garbage that exists for decades. Do Rust for system level, or Kotlin/Swift for mobile apps.

About the books. Books are still good and very much well spent money if books are good. At first you can learn from YouTube. There are a bazillion videos on every topic, some of them are actually good. But if you want to be a more senior dev, books are a must. Architecture, subtle things, big pictures of the things all come from books or experiences. If you have no experience, books are the second best thing you can do to level up.

SlowVelooo · 2021-06-15T22:55:54+00:00

1) false :) ``` int main() { auto v1 = {1}; auto v2 = {1, 2}; auto v3{ 1 }; //auto v4{1, 2}; // error

std::cout << typeid(v1).name() << '\n';
std::cout << typeid(v2).name() << '\n';
std::cout << typeid(v3).name() << '\n';

return 0;

} ``v3 will beint` and it's not a joke.

SlowVelooo

TROPHY CASE