There was a lot of internal deliberation on what approach should be used to enable resource sharing between multiple consumers of Editable* content. It took a few rounds design to settle on the Object / Content approach.
Once all that was decided the implementation could move relatively quickly hence all the changes coming down the pipe now that the period of deliberation is past.
Fyi, this started popping up on new servers 
I got that pop-up yesterday. Wonder why it doesn’t load the Player’s name.
I’m really excited for native vectors! I’m also glad they chose vector.create(X, Y, Z) instead of vector(X, Y, Z). Seemed jarring in the RFC.
I was wondering, though, if it would be possible to implement vectors for the Color3 datatype? It has a very unloved API, and it acts basically the same as a vector (it’s not even clamped). It would speed things up and also give us Color3 math.
what makes the vector library different from the vector3 library in terms of performance? is it a similar situation with using the colon operator on strings instead of the string library
Yes, just different plumbing.
Keep in mind, when you’re talking about an operation like min/max, such a large portion of the time is spent in the plumbing rather than the actual math operation that minor differences in the plumbing will have a relatively large impact on the total time.
yes that’s how these have usually always worked i’m confused on why you’re surprised since you’ve been around on the devforums since 2020
some of these rely on other components that either aren’t out yet (same update and pending) or a beta flag and aren’t “live”
Do Vector2s make use of the native Luau vector type yet or is that still pending?
No, and atleast I dont think they ever will because vectors can only have one metatable set to them, and that metatable is the one Vector3s use.
No, and they never will (at least there’s no plans for that).
Though if you’re writing number crunching where the difference matters significantly you can just write it using Vector3s and convert to a Vector2 before you write the results into an instance property.
when will this update release? cant update to this version yet
Yes finally!!
I thank the Roblox Team for consistently making awesome fixes and additions to the Roblox Engine 
They had to roll back to v649 on some devices due to some issues present in v650, so I assume you gotta wait until v651 releases (which is in a few days)
lol that’s funny, I tried the model duplication thing and it didn’t crash for me for whatever reason
also my studio just updated to v651, check yours for any updates
Ye it’s 651, it got worse for me on that version.
What is that button?
like now we have 3 ways to report
(srry for low res picture)
whats bloom? ive never heard of it
Bloom (sometimes referred to as light bloom or glow) is a computer graphics effect used in video games, demos, and high-dynamic-range rendering (HDRR) to reproduce an imaging artifact of real-world cameras. (Stole off wikipedia.) Bloom (shader effect) - Wikipedia
Here’s a image reference for such, It was from a reddit post, but gets the job done.
Is the Vector RFC released? doing print(vector) returns the methods vector has
