AS they are global yes there are some big disadvantages. If you, for example, use some third party script (library, framework whatever) and this script is also defining a global variable start or end and change the value of it, you might have some behavior which is super hard to debug.
Avoid global variables wherever possible. Also avoid using var at all. Use let or const to clearly define the scope it has.
If you really need global variables, which is in 99% of the cases not the case, you should attach them to your own namespace. In javascript this is done by adding your namespace to the window like
let window.myNameSpace = {};
where myNameSpace is something unique as your applications name. Then you can add your global vars with
window.nyNameSpace.start = ....
and of course retrieve everywhere else.
It doesn’t matter if you use Uppercase, Lowercase, Camelcase or whatever. You need to take care of the case anytime and everywhere. This is super important to become a good programmer.
So if you have to take care anyways, Why not use something easy to read? camelCase is not only common in javascript but in all programming languages I know. In the very long past you have used underscores to avoid upper case characters in your source code. so the functions were named like
delete_the_first_char_in_given_string()
for me that was the best readable but today it is recommended to use camelCase like
deleteTheFirstCharInGivenString()
what is also ok. But using lowercase its completely unreadable
deletethefirstcharingivenstring()
So yes, it makes sense to use camel Case.
Btw. You can use upper case column names in SQL. There is absolute no problem even on linux.