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.

Context, I work for Unity, but this is my own understanding of things and doesn’t necessarily reflect the views of my employer nor should it be considered “official” positions of the company. We have folks where communication is their job. Mine is helping build a better engine. There’s been a lot of misinformation since the changes were announced and hopefully I can help straighten some of this out, but again if there are other questions, there are others who are better qualified to address that.

The limit for using Personal was 100k. That has been raised to 200k. For the original terms, and these new terms, it is the same; no per-seat price until you reach the threshold. Once you reach the threshold, then you have to upgrade to Professional or Enterprise, and then there is a per-seat charge for the editor. When you hit the revenue or instance thresholds, then there is an additional charge… But you will be doing very well at that point and the amount is insignificant for most developers at that scale. Compared with Unreal, it is still significantly less, even with the announced terms last week. Unity continues to try and make it possible to create highly portable games for multiple platforms, and devices, and to do so with terms that encourage anyone to become a creator and build your dream game. The last thing Unity wants to do is stifle innovation and creativity.

If you watch the Q&A, the reason for the change, so that it was “retroactive” was to apply these term changes to companies pulling in high revenue, think millions of dollars, and who were releasing what amounted to DLCs and Season types of updates but without doing anything except maybe changing assets. Some of these games are even repackaged and re-released as “new” games. In other cases they may sometimes radically change the game so that it might be more accurately described as a new game, but they continue to release using an unsupported version of the engine. If a developer did this every time they approached the threshold, they could technically have millions of users, all while skirting around the TOS. Do this on Personal, delist at 90k, and release a “new” game to perpetually circumvent the licensing fees. The change wasn’t intended to harm the good developers or studios who are trying to make high quality games, it was intended to go after the businesses releasing “Banana Slots 2022.1 (updated).” If that’s the content you release, I’m sorry, but I think your games are kind of scummy. Please stop. The app stores don’t need more of this sort of cash grab content.

If you are making great content and the terms would severally impact you, then Unity was intending to work with you to reach agreeable terms.

Under the new terms, the same applies. If you or your studio are greatly impacted by the new trerms, Unity doesn’t want to sink your business, they are trying to find a way to keep investing in the development of tools and services which will allow you to reach the greatest number of users and want to work with you to make that happen, as that works best for the creator and for Unity.

For those making games for charity which were told they were going to be impacted, that was bad communication and you inadvertently spoke to the wrong person who didn’t fully understand your request. Content made for charity was always intended to be treated with favorable terms. The specifics of those terms I’m not deeply familiar with, so I don’t know how that applies to per-seat licensing or the details of such a contract, but I know that Unity works hard to support humanitarian efforts and I’m sure if you were making content for charities, nothing has changed.

The bottom line is this. If you feel like the terms are going to make you insolvent, work with Unity to resolve that. Unity is a partner, not an overbearing entity. Unity wants you to be successful.

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.

I tried it on my Nexus 5 as well. It didn’t work well for my needs at that time, so I went back to putting Android on it.

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.

This is why it works so well. It’s also one of the reasons I prefer vi over other text editors. It isn’t always the most logical which commands and keys do what, but I like the consistency.

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.

WinFS wasn’t a replacement of NTFS as much as it was a supplement. Documents could be broken apart into atomic pieces, like an embedded image and that would be indexed on its own. Those pieces were kept in something more like a SQL database, more like using binary blobs in SharePoint Portal, but that database still was written to the disk on an NTFS partition as I recall. WinFS was responsible for bringing those pieces back together to represent a compete document if you were transferring it to a non-WinFS filesystem or transferring to a different system altogether. It wasn’t a new filesystem as much as it was a database with a filesystem driver.

It’ll be an anti-clockwise spinning X, with speed lines extending from the tips.