In another words friction slows movement down and does not treat some direction on surface more preferable than others. Assuming regular surface this is pretty much definition of friction.
I am not sure how well I have explained stuff but if you are able to experimentally disprove this it's worth of paper.
For some reason I cannot reply to your comment wizzwizz4.
We are talking about dynamic friction in it's simplest form. You can treat it as simple math problem too. Let's consider two extreme cases:
A: Side slip is 1m/s and wheel spin zero or very small.
B: Side slip is 1m/s and wheel spin extremely big, let's say 1000m/s.
I think we can agree that friction is always opposite to surface speed. If wheel spin is on x axis and side slip on y:
On A case friction is (0, 1).normalized() * friction-coefficiency => (0, friction-coefficiency)
On B case friction is (1000, 1).normalized() * friction-coefficiency => [approximately] (friction-coefficiency, 0)
On classroom teacher says that slip does not matter. What teacher actually means that slip does not effect into -magnitude- of friction but this is left behind because problem is presented in context of 1D. Tho in 1D slip still matters little bit because there is difference is slip 1m/s or -1m/s.
Sometimes I am wondering what if there is theory which have been on right track but it's (false?) falsified and already forgotten. Sure theory could be incomplete or incorrect on some ways but would that right part be noticed? For example I think it's too easy to imagine world where relativity or quantum theory would be socially falsified and/or left without any attention.
Simple example experience I had when I was beginning of my physic studies (which I never finished) was when discussed with elder/smarter student about wheel friction. I was explaining that I had figured out that wheel spin actually matters when there is also side slip. [Total slip direction is dependent from spin speed.] But because he -knew- that wheel spin does not matter and he -knew- that he was better/smarter/etc. he was so focused to correct my mistake I was unable to convince him. How much this happens on higher stakes?
So if situation is that there has not been much progress for a long time I think it could be valuable also understand these failed theories and of course very importantly why they are falsified.
When I am working with hard problem I usually go this order:
1. Describe the problem.
2. Describe bunch of naive solutions.
3. Describe problems in those naive solutions.
4. "Describe problems in those problems": Why some of those problems do not hold water. Those can be workarounded, fixed or they actually are not really problem in this case or maybe some combination of naive solution properties gives working solution.
At the time I was lost joy of coding too but I was able to found it again.
One key point was to ignore learning new tech if it was not absolutely necessary and focus just creating new things. I think it all started from Sebastian Lague's video which reminded how beautiful coding can be.
Excel does not support any delimeter natively since its region dependent.
I ended up saving my mental heath by supporting two different formats: "RFC csv" and "Excel csv". On excel you can for example use sep=# hint on beginning of file to get delimeter work consistently. Sep annotation obviously break parsing for every other csv parser but thats why there is other format.
Also there might be other reasons too to mess up with file to get it open correctly on excel. Like date formats or adding BOM to get it recognized as utf-8 etc. (Not quite sure was BOM case with excel or was it on some other software we used to work with )
One can start from typical UIs and start tinkering from there why it isn't good enough for programming.
Good first step is to notice that we dont have even static data objects. Still UIs are full of them (forms) but you cannot copy paste or store them as a whole, everything is ad-hoc.
Now imagine that every form could be handled like Unity scriptable object. And maybe something what prefab variants do: data inheritance.