I have a question regarding "mainline" that I hope someone could help clarify.
What is the difference (in terms of coding, etc.) between mainlining support for a chip into Linux versus pinning it to a specific kernel revision? What makes it easy to bring a chip up on a specific kernel version,but not easy to submit that to the mainline kernel so future versions of the kernel are compatible?
Are there significant changes between kernel versions that require someone to be an active maintainer for the specific chip, making sure changes to the kernel stay compatible with the chip? And thus most manufacturer don't care enough to keep supporting future versions once they get on specific kernel version working?
I have a Class B CDL (with a medical cert restriction since it was for a state job, meaning no commerical jobs unless I get a medical done. I presume driving a school bus would be exempt for this) in New York. I guess I was one of the "500k+" people targeted by NYS, as I received an email asking me to apply to be a school bus driver. I gave it a quick thought before realizing that I work a 9 to 5 job, so there was no way I could even work the job if I wanted to. Besides the other good reasons mentioned in the article and this thread, I'm sure that also restricts the number of applicants because most people can't work during those hours unless they are retired or unemployed.
Have you ever looked into Terrarium? It was created by the .NET team a long time ago to demonstrate the capabilities of .NET. You program a creature and simulate an ecosystem which consist of other peoples "creatures" which if I recall correctly were essentially just DLL's of their code.
Even fellow colleagues can send embarrassing notifications on work related accounts. "I can't believe they don't understand such a simple concept" is not something you want appearing in a message addressed to you from a co-worker.
I've seen my fair share of embarrassing messages show up from Microsoft Teams when someone else in my corporation is screen sharing.
You'll need to get a set of Twitch API credentials from https://dev.twitch.tv/dashboard/apps/create and store the ID/Secret in config.json. Once you start the go program just point your browser to http://localhost:8080/ and you can browse through streams with no gameid set 50 at a time.