- Video calls
- Screen/webcam recording
- Live streaming
- Real-time transcoding for media servers (don’t know much about this but I’ve heard it’s a thing)
- Game streaming
- Video editing (making exporting less frustrating)
1,732 karma · joined January 22, 2020
- Video calls
- Screen/webcam recording
- Live streaming
- Real-time transcoding for media servers (don’t know much about this but I’ve heard it’s a thing)
- Game streaming
- Video editing (making exporting less frustrating)
It’s no different from mandating that the software can’t be malware that puts a ransom on your data, contain other people’s copyrighted content without permission, or just not work despite you claiming that it does when you sold it
And it’s not mandating that anything is structured in a particular way, just that the game works as the buyer would expect and how they achieve that is up to them
We already obligate them to do other basic necessities for consumer protection such as refunding or replacing faulty products
If you include a library function with a null check that gets inlined you probably don’t want a bunch of warnings there for code you don’t even control
Direct link to part 3 (but read the others first for context if you can): https://blog.llvm.org/2011/05/what-every-c-programmer-should...
You don’t want warnings for every piece of code in a library you’re not using or sanity check you added that isn’t supposed to be hit
And you can’t warn when you’re optimising based on undefined behaviour because you can’t know when it will happen, that is equivalent to the halting problem
If you warned whenever undefined behaviour could be happening then e.g. every single pointer deference would say “warning: compiling assuming pointer is not null or unaligned”
Compilers optimise in multiple passes and removing things earlier can expose optimisation opportunities later that can affect other parts of the code too
Being able to assume certain things don't happen is powerful when you're writing optimisations, not doing that would have a real performance cost
I've used a third party app for this for a UK weekly pass train ticket you could only buy physically, but if you buy it on a train rather than at a station they can't print you a ticket with a magnetic strip and they have to give you one with a barcode (technically an Aztec code), which you can then scan onto your phone and use at the gate. But I kept the original ticket with me too and would use that if a person asked to inspect it
I guess it depends on whether it's likely to confuse people?
For example, without any AI, if I generate a lookup table for the sine function in my code, that table may not be copyrightable because it was machine-generated, but it doesn't somehow make the rest of the code not copyrightable either
"Co-authored by" doesn't imply it was entirely machine-generated
Also, one of my first interactions with this Alexa+ thing was “how long is it until 8:45am”, one of only a few commands I use it for to work out how much sleep I’m getting, and it proceeded to ask me what the current time was… I immediately turned it off after that
Apart from ensuring there’s not anything confidential in the code like API keys (which you shouldn’t have anyway, unless it’s just in comments) it won’t take any extra work unless you want to put effort into that side of things
But in general this kind of thing is very unreliable for any non-trivial code without a lot of manual work, so a better approach could be to compile to WebAssembly which can be translated into C