261 reputation
1310
bio website korcholis.com
location Barcelona, Spain
age 26
visits member for 3 years, 5 months
seen Sep 10 at 14:23

Interface analyst and developer using a wide variety of languages. Experienced PHP, JavaScript/jQuery, Java, Android and Interface developer which can move from server-side to client-side technologies easily to develop high-end user web applications clearly and well documented.


Sep
1
awarded  Teacher
Sep
1
answered Mobile App Development-Architecture/Platform: Main performance concern: device/UI responsiveness
May
9
awarded  Famous Question
Mar
26
accepted Are web application usability issues equal to website usability issues?
Mar
26
accepted What are the pros and cons of Node.js?
Apr
17
comment Should website frontends be rendered in client-side or server-side?
It should work in IE8, as mentioned to @LucFranken, so History is not available yet. Plus the site is amazingly small, and Wordpress is too big, even for this case. But thanks for your comment
Apr
16
comment Should website frontends be rendered in client-side or server-side?
Hehe, I partially disagree with your last statement, but because I know the limitations of the project [it should run on IE8, thus history isn't available yet. We went across this thing too =( ], so I was playing with an advantatge. Apart from that, I agree with every point. And that's right, the specifications dictate the path to follow. Finally, we moved to an intermediate solution, with friendly urls from PHP and presentation+localisation from JavaScript. I'd personally have pushed localisation to PHP and presentation to HTML, leaving the behaviors to JavaScript.
Apr
16
accepted Should website frontends be rendered in client-side or server-side?
Apr
16
comment Should website frontends be rendered in client-side or server-side?
I agree with you in almost each point. And along with you and @RobertHarvey, the solution always depends. In this case, IMHO, PHP would have been better (and faster), because it has few effects (which can still be done in JS) and plenty of pages with contents which need to be translated, urls which need to be "friendlied" and frameworks which were already done (precisely we own a tiny framework that fits any microsite easily)
Apr
16
asked Should website frontends be rendered in client-side or server-side?
Feb
26
awarded  Constituent
Feb
26
awarded  Caucus
Oct
8
awarded  Autobiographer
Aug
13
awarded  Notable Question
Apr
15
awarded  Yearling
Jan
3
awarded  Popular Question
Jun
22
revised Are web application usability issues equal to website usability issues?
added 357 characters in body
Jun
22
comment Are web application usability issues equal to website usability issues?
You took "simple" out of context. I was talking about simple (or could a better adjective be "classic"?) interaction. A web application is somewhat working in your browser (or similar, the desktop version of Grooveshark is a desktop wrapper of the web version) that could perfectly working as a desktop application. Thunderbird/Outlook>Gmail. Openoffice/Office>GDocs. Due to this situation, Gmail and GDocs can use some desktop like interaction such as right click or drag and drop.
Jun
22
comment Are web application usability issues equal to website usability issues?
Indeed I agree with you. But there may be some desktop application usability possibilities that can be applied to web applications such as double-click, usable-right-click, always-visible menus, to see if they truly work and are useful, etc. I actually do not want to know if I need to concern about usability in web applications. I look for some differences between both worlds and if I need to double check some typical problems that specifically appear in web applications and don't do in non-web applications
Jun
22
awarded  Commentator