Why did Laravel change cookies and $_SESSION?

Question

Sessions

$_SESSION - throws an error.
session('name' => 'my_value' ) - sets the session to reload the page, and not as in the standard before leaving the browser.
Same thing with cookies.
We expose $cookie = cookie('name', 'value', time()+3600);
them But they somehow work outside the box, I check the storage, there is no kukaf :(
They need to be somehow transferred to the views, I don’t understand why they changed so much?
And as I understand it, now to save sessions, you need to create a table and do a bunch of movements , why?

Answer 1

Nothing was changed there, you have something with the settings. The session runs until the expiration of the lifetime, and not until the reboot.

And as I understand it, now to save sessions, you need to create a table and do a bunch of movements, why?

Misunderstood:

By default, Laravel is configured to use the file session driver, which will work well for many applications . In production applications, you may consider using the memcached or redis drivers for even faster session performance.