(December 8, 2018 at 1:48 pm)bennyboy Wrote:(December 8, 2018 at 11:42 am)FlatAssembler Wrote: Do you think it would be a good idea to apply to the Hostinger hosting for 8$/month and 10x as much bandwidth? I can keep the same URLs, and, right now, 8$/month doesn't sound too much (I pay more than that for my mobile phone right now). Though every dollar is good if I somehow end up homeless, and I can't really know what will happen to me (I don't know enough programming to make money with that, and I could have never guessed both my parents would have become unemployed and that my mother would have ended up in jail for an entire year).I pay big money for an Azure VM now, but I played around with shared hosting for several year. They are pretty much all crap. For you, I would imagine that region might be an issue is well-- ideally you'd like something hosted in your part of the world.
If possible, I recommend finding a small company in your country that does shared hosting. I did that in Korea, and it still wasn't great, but it was 1000x better than hostgator or any of those super-big sites. googling "shared hosting in croatia" gave enough results for you to try I think.
Quote: Is the same true for other web-hosting services who claim high uptime?Absolutely. I dealt with hostgator, A2, and a couple others. I even paid for higher tiers of more elite service. They were total crap.
Quote:And what would be the advantages of building it in PHP? I can see an obvious disadvantage right now, I can debug JavaScript using the Safari Developer Tools, but I don't know how to debug PHP.Server-side builds have the following advantages, among others
-can access a private database easily
-save processing power of users
-hide more of the logic behind your site so that people can't reverse-engineer your efforts
So for example with your assembler, all the client can see is the final result; they won't be able to read (or just easily copy) your algorithms.
That being said, I know a lot of systems are going more client-side these days-- lots of async AJAX calls to load parts of pages, and so on. I'm not criticizing, I was just curious why you did it that way.
He can just use a CDN if he wants it faster, but the pages he's creating don't require high resources and the traffic won't be heavy enough to matter.