This is the way to start learning.
Look at a WPT test and try to focus on it.
Look at the web spec
Ask questions in the Discord about where it would be, and people are gladly willing to help. :)
Look at a WPT test and try to focus on it.
Look at the web spec
Ask questions in the Discord about where it would be, and people are gladly willing to help. :)
Ladybird is an outlier and there are probably a few more project like it, but anyone looking to be employed should pick up the new skill that is rust. Contribute to ladybird and learn c++ if the project interests you, but don't learn it for a career.
The advice about career is very geography and industry dependent. Almost no one hired Node.js developers in my city back when i started.
There's basically 0 rust jobs available that aren't scam startups.
Of course it is! You can still access an object after std::moving it somewhere, return references to local stack variables from functions, double-delete (or zero!), use uninitiated variables and do bunch of other things that rightfully caused notoriety C++ has got. And am saying it as someone who writes C++ every workday, unfortunately.
> return references to local stack variables from functions
> use uninitiated variables
Any properly configured compiler will catch and warn about those errors.
> double-delete (or zero!)
Not a real issue if you're using smart pointers.
Sure, you can program with no compiler warnings and no smart pointers—but nothing is stopping you from wrapping your entire Rust program in "unsafe" and doing all those things there as well. Programming languages can only do so much to save people from their own incompetence.
I'm getting strong Dunning–Kruger vibes from your reply. Yes, moved-from objects are in valid but often unspecified state even in STL, not to mention custom code in most C++ projects I had experience with [0][1].
> Any properly configured compiler will catch and warn about those errors.
No true Scotsman compilers...
> Not a real issue if you're using smart pointers. Sure, you can program with no compiler warnings and no smart pointers...
Yeah, the good-old tried-and-true "just always manage your memory correctly and avoid having bugs" way of writing C++ software that have been working out so well.
[0] https://wiki.sei.cmu.edu/confluence/display/cplusplus/EXP63-...
Don't get me wrong. Number of C++ libraries is far bigger than number of rust libraries. But number of modern c++ libraries is still not that high i feel. So once you have integrated legacy code into your project, there's a lot of scope for newbies to create memory leaks/double free/etc ...
Anyone looking to be extremely employable in this market should really learn both.
Otherwise, you are not going to see a migration to Rust from C++ shops at all.
> Ladybird is an outlier and there are probably a few more project like it. but anyone looking to be employed should pick up the new skill that is rust.
Then I suggest you prepare for Leetcode hards on Rust code, if you want to show that you are highly experienced in solving DSA problems that are found in systems software.
Also, why does Ladybird get a pass and the others don't?
I am plugged into an alumni network (based in the US) so I'd say I have a decent sample size to draw conclusions/trends from. Yes, these trends don't apply to every market or locality so there are loads of counter examples. The demographics of the alum network appear to be mostly mid-to-senior level ICs and management from backgrounds being engineers in the private sector and gov contractors. The start-up scene is grossly under-represented.
The tell-tale sign of a mature technology that has the momentum to last is if businesses that do a lot of gov contracts finally adopt a technology. We've seen this pattern with virtualization, then with containers, then with clouds + micro-services. Gov contractors are very conservative to adopt and rely on technology because ultimately their customer (gov agencies) maintain the service. And their pay are not like big tech so they cannot compete on that front and need a healthy and established pool of talent to pick from.
Every successful project is staffed with leads who know the problem space and the technology that is used in the solution. When planning for a project, you HAVE to account for how easy it will be to find talent to support the project given your budget. For short-term or "high-risk-of-being-on-time" projects the talent pool is obviously larger for established technologies like c++ and so that is what has historically been chosen. Obviously where it is appropriate to use c++. For those of you claiming I am in a bubble... perhaps. But keep in mind that companies with a "first to market" mentality are not the majority :)
The point of inflection for Rust I am continually noticing, and why I am confident it is an excellent for career-growth, it is NO LONGER being labeled as a "high risk" for new medium to long-term projects/efforts. When there is runway to grow/find Rust developers and there is runway to develop a missing library that is a dependency, Rust seems to be favored. Yes, if your industry is dependent stable and battle tested libraries then that is a case when Rust might not displace it. But another trend that backs up my claims is seeing parts of such libraries/projects being refactored out into its own thing written in Rust - and all that lives in parallel. So perhaps the dev that knows both languages is the better career advice. Lean toward one language or another based on your interests.
One final thing I will add is there is a good deal of "internal learning" opportunities for already employed folks to learn rust and start on the new project. These are folks that know memory management, know the problem space, know the company tooling, etc. Compare that with a new hire that will also learn rust, and you can see which an employer will favor. Internal folks moving to Rust opportunities and back-filling them with new c++ devs is a common tactic. But that being said, talent still needs to be found and often times casting a wider net by looking for c++ folks that are willing to transition to Rust is a tactic used on job postings. Rust is in demand for systems programmers and zero trust applications, btw.