Server vs Clientside - and when javascript comes into play

Well, my job interview didn't turn out as I had hoped. Well, too bad, but there's nothing I can do about it. 'Not enough experience', they said. Well, they're probably right. Another point, they said, was that I'd rather solve a problem serverside then clientside. They're a heavy-clientside (javascript) company, so I didn't really fit in. My view on server- and clientside differed from the company's view, I thought.. I first solve something serverside. Nothing fancy, just working. When I feel like it, I create some 'sugar on top': the javascript to help the page load faster (e.g., ajax) and check the user input to generate user-friendlier error handling. The company is working with javascript-only applications. What they want to create is not possible with server callbacks. I think any userinput will be checked by the server (never trust user input; you could be hacked), but they just trust on javascript. If it doesn't work, the application breaks. And that's ok; it is impossible to work with the application anyway if you don't have JS. Then it hit me: we didn't really have different views on the javascript subject, we just have different uses for it. While I'm creating websites with some extra sugar on top, they are building applications that require javascript. So it's perfectly reasonable for me to rather solve a problem serverside. For them, it's easier to the the same thing clientside. Guess I don't have enough experience still. A bit late, but merry X-mas and (a bit early) a happy new year, folks.