I'm used to non-software managers thinking knowing a language is knowing how to make software systems, but other programmers? It's like saying if you know every language now you're a novelist. Knowing the language is just a basic necessary fundamental from which you can start to learn how to design and create software.
Really? I disliked Perl for 3 decades on unix and Linux and I've never felt like I have been held back by not knowing or using it. I don't remember the last time I saw a Perl script, let alone needed to understand one.
Yes - videos. I don't recall latency problems since many years ago with some cheapo external speakers. FWIW I just tried a latency test on Youtube to check (currently on Shokz) and it seemed good. Frankly I have no idea if some low latency tech is being automatically used but I certainly didn't take any steps to ensure it was (Ubuntu, these days using Pipewire).
How common is it that they don't have that? because it's a long time since I had latency issues in years of Bluetooth headphones. Anker, Phillips, Sennheiser, Shokz, all sub $100 headphones and I haven't had latency.
I have a feeling you're mixing up the direction of the force you have to apply with the angle of the wheel. Also, countersteering is about how you change the radius of your turn, not about what angle you hold on a steady-state turn.
The effects of the round tire profile are a factor that alter the steering angle for a given turn - conceivably even against to the direction you turn, but as you can see from the Wikipedia page linked that's not what the term means.
And ultimately, it's the only way you initiate a turn, no matter how much many people disbelieve it. As the page says "While this appears to be a complex sequence of motions, it is performed by every child who rides a bicycle. The entire sequence goes largely unnoticed by most riders, which is why some assert that they do not do it."
What you describe is what some call counter steering.
You're certainly tenacious - an entire Wikipedia page telling you the definition, not including your definition, and telling you it's how bicycle steering works doesn't slow you down!
I think rather than arguing with me you should correct Wikipedia and see how far you get. You should also attend to https://en.wikipedia.org/wiki/Bicycle_and_motorcycle_dynamics, that weirdly doesn't seem to mention your special facts on how bicycle steering works.
Experience is misleading and not only is what you describe not countersteering, it's also not how bicycles steer. The primary input is the angle of turn of the handlebars. The complication is that on a balanced vehicle like a bicycle you can't just point the wheel where you want to go or you'd just fall over to the outside of the turn. So, before you steer where you wan to go, you have to point it in the opposite direction to initiate a lean.
Many people get quite heated, insisting they do not do this on a bicycle, and believe all sorts of other things. But the fact is this is what everyone does and it's the only way to steer a bicycle, it's just that it's quite possible to ride without realizing this is what you're doing.
It’s like trying to get somebody to understand countersteering.
Yep.
Until they understand that you’re literally riding the bike on the side of the tire, it can’t make any sense
Wait, what? Countersteering is about manipulating the contact patch relative to the center of gravity. The side of the tire has relatively no relevance.
However, having had a voice chat for an hour this weekend with someone 200 miles away, I can tell you that 30 years ago it worked so much better it's not even funny; it was just expensive.
My phone provider (Fi) gave me an internet connected call rather than use the cell voice network (proudly telling me it was encrypted). It was full of dropouts and there was a serious latency that really inhibited conversation. I switched to a few other options like WhatsApp and the audio quality improved but the latency did not, and even got worse. Young people may be barely aware that a 200 mile phone call had tiny latency - you would not know there was any - because there was a literal wire connection between each end and communication was at the speed of light. Even transatlantic calls had minimal latency unless it went by satellite.
Sure today we can do it with video, but frankly, for a chat, I don't even see much benefit. I'd certainly choose voice-only if it meant zero latency, and sadly I seem to have chosen a mobile provider that does its best to prevent that.
Ubuntu Mono since it was in beta and I heard the designer from Dalton Maag — the typeface design studio commissioned to design it — give a talk about how excited he was to be able to create a comprehensive, carefully thought out, and truly free/libre font.
I've never seen another one that I prefer the look of, and now it's imprinted in my brain. People love to crap on Shuttleworth / Canonical / Ubuntu, but there are a lot of great things they've contributed over the years.
Yes, that's why we use typing, to get better working code more easily. That's why I use type annotation and enforced checkers in Python. It makes it so much easier and quicker to create good systems of any significance.
We currently have to get up in the dark and we're about to get an hour of relief, but if we stuck on winter time sunset would max out at a depressing 7:25pm in summer while sunrise would be a pointless 4am.
I don't understand what's hard to understand. The timing to avoid starting your day in significant darkness all winter would means a very early sunrise and short evenings in the summer.
The logical solution is to change our schedules to partially follow the sunrise, rather than keeping everything static relative to midday.
We could all coordinate changing every timetable and appointment, or we can instead change one single thing to get the same effect.
IMO a theoretical ideal would be to fix the time of sunrise. But I'm practice that would be a huge PITA only workable through tech.
Places closer to the equator get nothing much out of it.
Seems pretty reasonable that if you want to tell the world you hate something, you might want the world to understand why you hate it, or else perhaps we might assume it's not a reasoned position. That's certainly the conclusion I'm coming to.
I'm used to non-software managers thinking knowing a language is knowing how to make software systems, but other programmers? It's like saying if you know every language now you're a novelist. Knowing the language is just a basic necessary fundamental from which you can start to learn how to design and create software.