Is GetService better than game.Service??

Yes. GetService returns a service by its ClassName, and guarantees that that service will be returned. It should be used for every service. Workspace gets a pass, considering the ways to access it.

• game.Workspace (child of game)

• game.Workspace (property of game which holds an object reference to workspace)

• game:GetService("Workspace") (getting service)

• global workspace (workspace again but this method has been deprecated)

There are some services whose names are not their ClassNames. For example, the UserInputService.

local UIS = game.UserInputService -- Uh oh! We can't get it? :(

UIS = game:GetService"UserInputService" -- We got it! :D

We can rename these services, but we can't access them via game.Service anymore.

-- I manually renamed the Players service "Hamburgers". It is named "Players" by default.

local players = game.Players -- Where did Players go??
players = game.Hamburgers -- Hmph, here it is..??!!

players = game:GetService"Players" -- There you are! This GetService saved us.

GetService will create the service if it does not exist. GetService and FindService are used in case the name has changed making the code more robust.

Both workspace and game.Workspace hold constant references to the Workspace if the name changes both methods will still return the workspace and since it does not need to be created we can use it without and issues. This only applys for this service and no other ones have constant references.

In short to make more robust code use GetService.