The legality of who owns that work will depend on your work contract and your local employment law.
You very well might create something, turn around to sell it to them, and find out that your employer legally owns the copyright to the work even if you did it on your own time with your own resources.
Employment law is nuanced.
Tldr; bring your work contract and your idea to a meeting with an employment attorney and ask them who would own this work.
Resurrecting woolly mammoths just in time for their natural habits to become decimated by climate change feels like a cosmic satire on the duality of human technological progress
I'm not so sure about that. They have kind of opposite incentives to OpenAI. OpenAI starting without much money had to hype the AGI next year stuff to get billions given to them. Google on the other hand is in such a dominant position with most of the search market, much of the ad market, ownership of Deepmind, huge amounts of data and money and so on probably don't want to be seen as a potential monopoly to be broken up.
It's an irrelevant implementation detail. This is for a live call. You are streaming video at the same time, so there's no point in worrying about idling.
I'd even say that it's a good example for others, because the equivalent code with the event loop would be slightly more complicated (maybe 5 more lines?). Striving for "doing things right" when the wrong thing is perfectly appropriate would be a bad example.
My guess is that somebody coded that event-loop-less X client not really familiar with the language and how to write Xlib apps. I partially assume this because C, C++ and especially Xlib are becoming less popular over time, so finding skilled practitioners to write it idiomatically is relatively rare now. This basic event loop stuff is something that maybe belongs in a library. So they just wrote library grade functionality themselves, badly. The commentary here is getting defensive about doing things the wrong way, coming up with lots of post hoc justification.
> You are streaming video at the same time, so there's no point in worrying about idling.
I'd argue it's completely opposite of this. You're streaming video, already putting some significant stress on the system. No reason to waste time (even if it's a minuscule amount) to make things worse.
> Striving for "doing things right" when the wrong thing is perfectly appropriate would be a bad example.
And that's how we ended with e.g. modern IoT that kinda sorta works but accumulation of minor bad decisions (and some less minor bad decisions for sure) ends up making the whole thing a hot mess.
Sleeping for 100ms between checking for events will not produce a noticeable CPU load. The only reason this would drain the battery is because it can prevent the CPU from entering deeper powersaving states - but even for that 100ms is an eternity and video streaming will prevent that anyway.
These houses still had to be built, hooked up to plumbing, wired for electricity, have a lot cleared and excavated, concrete poored... Also you still need to decorate and provide appliances.
Add all that in and you'll see theres a few 100k worth of additional work not in the kit
So that $52k price is really just for building materials and plans, but doesn't include land, permits, building costs.
If I was going to build this prototype I'd start with just a semistructured textual play by play recap as the input. Also including roster, injury, amd schedule information with a fairly basic prompt would probably go a long way.
This data exists for most live games at this point via various web services. I'm sure espn has significant resources internally to source that info
I don't think ESPN does anything that takes significant resources. That's all handled by SportsRadar or ... there's another big provider but their name alludes me. They basically firehose you all the game information as structured data and you can use it programmatically however you'd like.
Definitely. I have no experience in live game statistics, but from my sports content experience I bet there's data scientists and applications behind the scenes that specifically pull this data to be read on-air.
Yeah it feels like the ideal way is to feed in a transcript of the announcer audio + some standard stats. That would ensure you catch both the human stories & the factual content.
But I wonder if there are licensing issues with using the audio/transcript to generate your summary. I know that the raw stats are public domain but I wouldn't be surprised if they can't use the transcripts or audio.
This is one of the most absurd comment I've read in a while. I love it, thank you.
Fwiw, cervelat is also very common in France, I grew up eating that stuff. Maybe that's why I liked the article so much. There's something to dig up there
You very well might create something, turn around to sell it to them, and find out that your employer legally owns the copyright to the work even if you did it on your own time with your own resources.
Employment law is nuanced.
Tldr; bring your work contract and your idea to a meeting with an employment attorney and ask them who would own this work.