And now that we had a look at those examples
and we'll see them in action soon.
That of course already brings us
to one super important question.
Should you use such third party packages
or should you write your own custom code?
And if we compare these options,
we can of course say that for the third party solution,
we have to write less code.
We can use an existing package
and hence we get the end result in a quicker way.
But of course, as a downside,
we have less control over decode and the exact behavior.
We have to accept the default behavior
and the configuration options the package might
be giving to us.
On the other hand,
if we write our own code, the downside is that we have
to well, write all that code.
That this is more error prone.
It's easier for us to mess something up there
and it's more work for us to do
but of course we have full control over the result
and how it should behave.
So we basically have the opposite advantages
or disadvantages here and therefore
as so often in development it depends what's better,
there is no single right or wrong way here.
Instead in reality,
for most more complex websites you might be working on,
you typically mix the two concepts and approaches.
Typically in bigger projects,
you will use some third party packages
and code for solving certain problems.
And you will write your own code
for our problems where you need full control.
And with that course of course,
you will also see a mixture of both
but in this course section,
we are going to have a look at various third party packages
for CSS and JavaScript and how we can use them.