1,035 reputation
2721
bio website
location Switzerland
age
visits member for 2 years, 5 months
seen Dec 17 at 10:56

Flair

Web-Developer and wiseacre


Oct
3
reviewed Reviewed Are Java certifications important for an architect role?
Oct
2
awarded  Custodian
Oct
2
reviewed Reviewed Sites with overlapping code-bases. Developing multiple sites with little changes
Oct
2
reviewed Reviewed What am I missing about PHP?
Oct
2
comment What am I missing about PHP?
@Chris "Most commonly" means in this case always. Or the other way round: It absolutely never runs in a browser. PHP is used to generate static HTML, to run code in a client, you still need to use JavaScript.
Oct
2
answered What is the motivation behind TypeScript?
Oct
2
comment What is the motivation behind TypeScript?
-1 So you don't like JavaScript. That's your statement, basically.
Sep
24
answered Proper Use Of HTML Data Attributes
Sep
16
awarded  Critic
Sep
16
comment Why would one bother marking up properly and semantically?
-1 for that lousy link. (The pragmatic guide to HTML: Principles)
Aug
30
comment My father wants to learn PHP-MySQL to port his application. What I should do to help?
Is C# not an option? I would use it, if I were you. PHP is easy to start with, but also easy to find yourself creating a big mess. Furthermore your father would have to learn HTML and CSS, without it chances are not too god for a web based app. How about a Silverlight solution? It's web based and .NET
Aug
27
comment Rush to client-side in web development
I chose to accept this answer, because it is the most complete one. All the others have good points, but this is the most conclusive. Thanks everyone!
Aug
27
accepted Rush to client-side in web development
Aug
27
comment Rush to client-side in web development
Very good point indeed.
Aug
25
comment Rush to client-side in web development
Great answer! But server-side frameworks promise the same benefits, don't they?
Aug
24
comment Rush to client-side in web development
@tdammers I don't want, really I don't. I don't see any point in using SOAP over HTTP. REST is suitable for nearly everything.
Aug
24
comment Rush to client-side in web development
Of course I know how painful it is and was to make everything work in every browser. But this work has to be done regardless server- or client-side (as you have to use a browser in the end anyway). I certainly agree on your second point. However, I don't see 30% to be rewritten. Some alterations possibly are needed, but I doubt it is as bad as in the old days. On the other hand you have to redo everything based on the service layer, if you want to replace your server-side stack. So you are VERY tightly coupled to your server side implementation. Possibly from the top of the UI to the model.
Aug
24
comment Rush to client-side in web development
One more thing, 'Client-side web development is strongly coupled with web browsers' - Web-technologies are official standards, as long as you stick with it you are implementing a standard, not coupling your application to a browser. While not too long ago this was not really true, it seems to be at the moment.
Aug
24
comment Rush to client-side in web development
Isn't that pure imagination? You will possibly have to change your server-side stuff when clients change, as you wont get round generating HTML/JS/CSS at some point.
Aug
24
comment Rush to client-side in web development
To clarify, my assumptions are limited to front-end. I see a shift towards the client-side, in UI logic, rendering and stuff like that. Of course server-side will never be gone, but reduced to an REST-api (or SOAP for that matter).