boyned//Kampfkarren

@boyned

Joined on Feb 5, 2019

  • The new API changes for data stores have made me reflect a little on what the path for DataStore2 going forward is. As I say many times, my projects move with me. They are open source, yes, and open to contribution, but I don't support projects I don't use, and I don't add features I don't use. This is why, for example, there is no getting data stores by user ID in DataStore2. There are some safety cautions (mostly with users being in a separate server as you use it), but the primary reason is that I have never had a reason to want it, and nobody has sent a pull request. That being said, I've moved a long way since DataStore2. DataStore2 is a module written 3 years ago for Battle Hats that I released just on a whim, and it blew up far past what I could have ever expected. I'm of course very happy that my work is being used in lots of huge games, and whenever the topic of data store libraries come out, they always have to compare to me. It's also nice to see Roblox seeing DataStore2 as a point of reference for future APIs. That being said, it is very challenging for me to maintain. The Good DataStore2 is absurdly easy to use, and nothing else I've seen even comes close. The ease of use of :Get(), write, then :Set() is unmatched. I know this because of some of the kinds of questions I get, which suggest to me that my module is good even for beginners. DataStore2 is battle tested. The bugs that are known in it are very minor, as everything has been ironed out in games with combined billions of visits. The Bad
     Like 5 Bookmark
  • All code samples assume --!strict. Typed Lua uses HM-typing according to an engineer at Roblox. Typed Lua does not attempt to infer multiple return types. It infers that the return type is the first return used. function foo(x) if x == 1 then return "foo" else
     Like  Bookmark