Yeah, I expect that it might. Nope, I'm an engineer working on the engine side of things. I joined Unity because I believe in the work we're doing, like my colleagues. The last couple of weeks have been a distraction, but my team is still pushing ahead and building the engine of tomorrow. Believe me, I'm personally just as frustrated with how things were communicated. I have a lot of faith in my team and the positive impact of the work we are doing. All I can say is that we're continuing to build functionality and features which will enable developers to accomplish more and drive success. Decisions about how this technology is licensed isn't something I have direct control over, but I hope that through our efforts we can help restore the trust which has been eroded. I'm still bullish on the future road map.

I like my Smart EV. From the outside, it is as long as most cars are wide, can U-turn as right as a Tesla Cyber truck, if not tighter, and can get me from A-B daily, charging overnight off a regular household outlet.

As a resistor, there isn't a forward or backwards. Diodes and some capacitors perhaps, but resistors have no forward or reverse bias. Upside down might be a problem because all the electrons will fall out. /s

I expect it is natural that there is a tipping point, where there is enough content that it becomes engaging for others. It's like going to a house party. The first few people to arrive at the party awkwardly stand around and might leave early. Once there is the right number of people, the group dynamic shifts and the entire energy of the party is elevated. The Exodus brought a lot of curious visitors, but everyone was standing around. Now there's engaging content and comments are growing. Some of those who stopped by in June will likely come back at some point if they left early -- I did the same thing in the early days of Reddit. I think there's been a large enough influx to kick things off and I expect things to continue to grow, but the active user count was probably inflated significantly over the past couple of months and will be resetting to more reasonable numbers.

You could argue that place was a copy. Before that you had The Million Dollar Homepage (https://en.wikipedia.org/wiki/The_Million_Dollar_Homepage?wprov=sfla1) in 2005, where companies could buy a pixel for a dollar. I have a hard time believing that it didn't have some influence over the creation of place.

They are different as you and I have both described, but when the sink device can support different streams, it has a significant advantage, because it automatically can support sinking frames from the broadcasting device and it removes the overhead of decompressing and then recompressing with practically assured data loss. It is yet another example of how patents, especially software patents, work against the original intent of the patent process.

Or heximal/senary. Arguably imperial is already duodecimal/hexadecimal/sexagesimal for the fractional parts.

I think it's closer to 75% (75.25% precisely). 55% because of the attack and 55% trying to figure out what the picture is. Stacking those stats, of those who weren't confused at first, those 45% remaining were subjected to the effect of the attack. Only 25% remained unaffected.

Miracast is plagued by latency problems, but it is still alive. Android itself still has support, it is the Nexus 6 that Google dropped support, to only support their Chromecast. Microsoft Xbox can be used as a Miracast receiver and there is support for Miracast built into Windows 10+, both as a receiver and transmitter. While Miracast was built upon Wi-Fi Direct, (Wi-Di, I believe), it has been extended to work over a wired network too. The biggest difference is that Miracast is transmitting the frames over the network, so that the device transmitting needs to render the content, whereas DIAL and Chromecast are sending steam URLs, authentication, and transport messages to the Chromecast, which then is the device actually rendering. Chromecast is better for mobile device batteries, but I loath the proprietary nature of it.

The limit was 260. The OS and the filesystem support more. You have to enable a registry key and apps need to have a manifest which says they understand file paths longer than 260 characters. So while it hasn't been a limitation for awhile, as long as apps were coded to support lesser path lengths it will continue to be a problem. There needs to be an conversion mechanism like Windows 95 had so that apps could continue to use short file names. Internally the app could use short path names while the rest of the OS was no longer held back.

You might say extra redundant?

It should put the question to bed, but there are plenty of examples where something in the Constitution needs to be interpreted for intent, by the SCOTUS.