�ݺ�ߣshows by User: LeaVerou

�ݺ�ߣshows by User: LeaVerou / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: LeaVerou / Thu, 31 May 2012 17:02:41 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: LeaVerou Turning to the client side /slideshow/turning-to-the-client-side/13153980 turningtotheclient-side-120531170244-phpapp02
My notes for the first section (I was too lazy to make notes for the entire deck :P): Hello everyone. I’d like to thank O’Reilly for making it possible for me to be here today. If my name sounds vaguely familiar, it's probably due to one of these open source web apps and libraries I wrote. Most of these projects have something in common: They try to be as light on the server as possible. They operate on what’s often called "thin server architecture". Everything that can be done on the client, is done on the client. The server is used for three things: Hosting the files, the data and keeping both of these safe. For many projects, this is a no-brainer. In other cases that philosophy becomes more of a challenge. The biggest reason I support this philosophy is its practically infinite scalability. When dealing with the client-side, you are always dealing with one machine. You don't control its capabilities, so it may fall behind your expectations. But it's always one, even if your app gets slashdotted or becomes the next Facebook overnight. Every line of code you write for the server might end up being executed hundreds or even thousands of times per second. Many such lines will bring scalability challenges you couldn’t even imagine when writing said code. This approach also reduces server costs quite a lot. A server that just serves static files and does little processing can be quite cheap to run, even when a web app becomes quite successful. On the other hand, big backends can be quite greedy with server resources. If you manage to have absolutely no server-side code, you can even use services like Github Pages and reduce the costs to zero. Every time I explain this to somebody, there will be some know-it-all who will be eager to dismiss the idea by saying "But servers these days are cheap!". What he means is that storage is cheap. Bandwidth is cheap. CPU cycles are rarely cheap. Professionals like database administrators and performance engineers and the like, are never cheap. Say all you want about reduced server costs, the reality is that I've witnessed many ambitious projects with fat servers becoming sluggish because they grew too fast. Some survived, some didn't. As an added advantage, less roundtrips to the server mean less reloads or less dreaded spinning loaders. When something is performed on the client, the result is instant. Users tend to really like that. I’m sure that, as a user, you do too.]]>
My notes for the first section (I was too lazy to make notes for the entire deck :P): Hello everyone. I’d like to thank O’Reilly for making it possible for me to be here today. If my name sounds vaguely familiar, it's probably due to one of these open source web apps and libraries I wrote. Most of these projects have something in common: They try to be as light on the server as possible. They operate on what’s often called "thin server architecture". Everything that can be done on the client, is done on the client. The server is used for three things: Hosting the files, the data and keeping both of these safe. For many projects, this is a no-brainer. In other cases that philosophy becomes more of a challenge. The biggest reason I support this philosophy is its practically infinite scalability. When dealing with the client-side, you are always dealing with one machine. You don't control its capabilities, so it may fall behind your expectations. But it's always one, even if your app gets slashdotted or becomes the next Facebook overnight. Every line of code you write for the server might end up being executed hundreds or even thousands of times per second. Many such lines will bring scalability challenges you couldn’t even imagine when writing said code. This approach also reduces server costs quite a lot. A server that just serves static files and does little processing can be quite cheap to run, even when a web app becomes quite successful. On the other hand, big backends can be quite greedy with server resources. If you manage to have absolutely no server-side code, you can even use services like Github Pages and reduce the costs to zero. Every time I explain this to somebody, there will be some know-it-all who will be eager to dismiss the idea by saying "But servers these days are cheap!". What he means is that storage is cheap. Bandwidth is cheap. CPU cycles are rarely cheap. Professionals like database administrators and performance engineers and the like, are never cheap. Say all you want about reduced server costs, the reality is that I've witnessed many ambitious projects with fat servers becoming sluggish because they grew too fast. Some survived, some didn't. As an added advantage, less roundtrips to the server mean less reloads or less dreaded spinning loaders. When something is performed on the client, the result is instant. Users tend to really like that. I’m sure that, as a user, you do too.]]> Thu, 31 May 2012 17:02:41 GMT /slideshow/turning-to-the-client-side/13153980 LeaVerou@slideshare.net(LeaVerou) Turning to the client side LeaVerou My notes for the first section (I was too lazy to make notes for the entire deck :P): Hello everyone. I’d like to thank O’Reilly for making it possible for me to be here today. If my name sounds vaguely familiar, it's probably due to one of these open source web apps and libraries I wrote. Most of these projects have something in common: They try to be as light on the server as possible. They operate on what’s often called "thin server architecture". Everything that can be done on the client, is done on the client. The server is used for three things: Hosting the files, the data and keeping both of these safe. For many projects, this is a no-brainer. In other cases that philosophy becomes more of a challenge. The biggest reason I support this philosophy is its practically infinite scalability. When dealing with the client-side, you are always dealing with one machine. You don't control its capabilities, so it may fall behind your expectations. But it's always one, even if your app gets slashdotted or becomes the next Facebook overnight. Every line of code you write for the server might end up being executed hundreds or even thousands of times per second. Many such lines will bring scalability challenges you couldn’t even imagine when writing said code. This approach also reduces server costs quite a lot. A server that just serves static files and does little processing can be quite cheap to run, even when a web app becomes quite successful. On the other hand, big backends can be quite greedy with server resources. If you manage to have absolutely no server-side code, you can even use services like Github Pages and reduce the costs to zero. Every time I explain this to somebody, there will be some know-it-all who will be eager to dismiss the idea by saying "But servers these days are cheap!". What he means is that storage is cheap. Bandwidth is cheap. CPU cycles are rarely cheap. Professionals like database administrators and performance engineers and the like, are never cheap. Say all you want about reduced server costs, the reality is that I've witnessed many ambitious projects with fat servers becoming sluggish because they grew too fast. Some survived, some didn't. As an added advantage, less roundtrips to the server mean less reloads or less dreaded spinning loaders. When something is performed on the client, the result is instant. Users tend to really like that. I’m sure that, as a user, you do too. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/turningtotheclient-side-120531170244-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> My notes for the first section (I was too lazy to make notes for the entire deck :P): Hello everyone. I’d like to thank O’Reilly for making it possible for me to be here today. If my name sounds vaguely familiar, it's probably due to one of these open source web apps and libraries I wrote. Most of these projects have something in common: They try to be as light on the server as possible. They operate on what’s often called "thin server architecture". Everything that can be done on the client, is done on the client. The server is used for three things: Hosting the files, the data and keeping both of these safe. For many projects, this is a no-brainer. In other cases that philosophy becomes more of a challenge. The biggest reason I support this philosophy is its practically infinite scalability. When dealing with the client-side, you are always dealing with one machine. You don't control its capabilities, so it may fall behind your expectations. But it's always one, even if your app gets slashdotted or becomes the next Facebook overnight. Every line of code you write for the server might end up being executed hundreds or even thousands of times per second. Many such lines will bring scalability challenges you couldn’t even imagine when writing said code. This approach also reduces server costs quite a lot. A server that just serves static files and does little processing can be quite cheap to run, even when a web app becomes quite successful. On the other hand, big backends can be quite greedy with server resources. If you manage to have absolutely no server-side code, you can even use services like Github Pages and reduce the costs to zero. Every time I explain this to somebody, there will be some know-it-all who will be eager to dismiss the idea by saying "But servers these days are cheap!". What he means is that storage is cheap. Bandwidth is cheap. CPU cycles are rarely cheap. Professionals like database administrators and performance engineers and the like, are never cheap. Say all you want about reduced server costs, the reality is that I've witnessed many ambitious projects with fat servers becoming sluggish because they grew too fast. Some survived, some didn't. As an added advantage, less roundtrips to the server mean less reloads or less dreaded spinning loaders. When something is performed on the client, the result is instant. Users tend to really like that. I’m sure that, as a user, you do too.

Turning to the client side from Lea Verou

]]> 5333 5 https://cdn.slidesharecdn.com/ss_thumbnails/turningtotheclient-side-120531170244-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 CSS3 secrets: 10 things you might not know about CSS3 /LeaVerou/css3-secrets-10-things-you-might-not-know-about-css3 css3-secrets-111007050520-phpapp02
My CSS3 secrets presentation. These are just screenshots, the interactive version can be found at http://leaverou.me/css3-secrets (works best on Firefox)]]>
My CSS3 secrets presentation. These are just screenshots, the interactive version can be found at http://leaverou.me/css3-secrets (works best on Firefox)]]> Fri, 07 Oct 2011 05:05:20 GMT /LeaVerou/css3-secrets-10-things-you-might-not-know-about-css3 LeaVerou@slideshare.net(LeaVerou) CSS3 secrets: 10 things you might not know about CSS3 LeaVerou My CSS3 secrets presentation. These are just screenshots, the interactive version can be found at http://leaverou.me/css3-secrets (works best on Firefox) <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/css3-secrets-111007050520-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> My CSS3 secrets presentation. These are just screenshots, the interactive version can be found at http://leaverou.me/css3-secrets (works best on Firefox)

CSS3 secrets: 10 things you might not know about CSS3 from Lea Verou

]]> 17057 26 https://cdn.slidesharecdn.com/ss_thumbnails/css3-secrets-111007050520-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Polyfilling the gaps /LeaVerou/polyfilling-the-gaps polyfillingthegaps-111002094920-phpapp02
My slides from JSConf EU 2011. These are just screenshots, an accessible version can be found at http://leaverou.me/polyfilling-the-gaps/]]>
My slides from JSConf EU 2011. These are just screenshots, an accessible version can be found at http://leaverou.me/polyfilling-the-gaps/]]> Sun, 02 Oct 2011 09:49:18 GMT /LeaVerou/polyfilling-the-gaps LeaVerou@slideshare.net(LeaVerou) Polyfilling the gaps LeaVerou My slides from JSConf EU 2011. These are just screenshots, an accessible version can be found at http://leaverou.me/polyfilling-the-gaps/ <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/polyfillingthegaps-111002094920-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> My slides from JSConf EU 2011. These are just screenshots, an accessible version can be found at http://leaverou.me/polyfilling-the-gaps/

Polyfilling the gaps from Lea Verou

]]> 1935 4 https://cdn.slidesharecdn.com/ss_thumbnails/polyfillingthegaps-111002094920-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Mastering CSS3 gradients /slideshow/mastering-css3-gradients/8123661 css-gradients-110527063221-phpapp02
Screenshots from my talk "Mastering CSS3 Gradients". The HTML version of the slides with editable live demos is available at http://leaverou.me/css3-gradients/]]>
Screenshots from my talk "Mastering CSS3 Gradients". The HTML version of the slides with editable live demos is available at http://leaverou.me/css3-gradients/]]> Fri, 27 May 2011 06:32:15 GMT /slideshow/mastering-css3-gradients/8123661 LeaVerou@slideshare.net(LeaVerou) Mastering CSS3 gradients LeaVerou Screenshots from my talk "Mastering CSS3 Gradients". The HTML version of the slides with editable live demos is available at http://leaverou.me/css3-gradients/ <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/css-gradients-110527063221-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> Screenshots from my talk "Mastering CSS3 Gradients". The HTML version of the slides with editable live demos is available at http://leaverou.me/css3-gradients/

Mastering CSS3 gradients from Lea Verou

]]> 44956 16 https://cdn.slidesharecdn.com/ss_thumbnails/css-gradients-110527063221-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 CSS3: A practical introduction (FT2010 talk) /slideshow/css3-a-practical-introduction-ft2010-talk/5637358 talk-101101162127-phpapp01
Screenshots from the HTML slides that I used to complement my talk at Front Trends 2010. Quality is quite bad due to how Acrobat merges images into a single pdf. Find the HTML version of the slides, more information about the talk and my presentation framework here: http://leaverou.me/2010/10/my-ft2010-slides-and-csss-my-presentation-framework/]]>
Screenshots from the HTML slides that I used to complement my talk at Front Trends 2010. Quality is quite bad due to how Acrobat merges images into a single pdf. Find the HTML version of the slides, more information about the talk and my presentation framework here: http://leaverou.me/2010/10/my-ft2010-slides-and-csss-my-presentation-framework/]]> Mon, 01 Nov 2010 16:21:24 GMT /slideshow/css3-a-practical-introduction-ft2010-talk/5637358 LeaVerou@slideshare.net(LeaVerou) CSS3: A practical introduction (FT2010 talk) LeaVerou Screenshots from the HTML slides that I used to complement my talk at Front Trends 2010. Quality is quite bad due to how Acrobat merges images into a single pdf. Find the HTML version of the slides, more information about the talk and my presentation framework here: http://leaverou.me/2010/10/my-ft2010-slides-and-csss-my-presentation-framework/ <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/talk-101101162127-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> Screenshots from the HTML slides that I used to complement my talk at Front Trends 2010. Quality is quite bad due to how Acrobat merges images into a single pdf. Find the HTML version of the slides, more information about the talk and my presentation framework here: http://leaverou.me/2010/10/my-ft2010-slides-and-csss-my-presentation-framework/

CSS3: A practical introduction (FT2010 talk) from Lea Verou

]]> 15162 14 https://cdn.slidesharecdn.com/ss_thumbnails/talk-101101162127-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Colors In CSS3 /slideshow/colors-in-css3/1147797 colorsincss3-090315111323-phpapp01
The presentation for my yesterday's session at MediaCampAthens.]]>
The presentation for my yesterday's session at MediaCampAthens.]]> Sun, 15 Mar 2009 11:13:15 GMT /slideshow/colors-in-css3/1147797 LeaVerou@slideshare.net(LeaVerou) Colors In CSS3 LeaVerou The presentation for my yesterday's session at MediaCampAthens. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/colorsincss3-090315111323-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> The presentation for my yesterday's session at MediaCampAthens.

Colors In CSS3 from Lea Verou

]]> 9987 21 https://cdn.slidesharecdn.com/ss_thumbnails/colorsincss3-090315111323-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://cdn.slidesharecdn.com/profile-photo-LeaVerou-48x48.jpg?cb=1588954937 Front-end web developer. Passionate about open web standards, especially CSS3, HTML5 or ECMAScript. Co-founder of Fresset Ltd. Loves good design. Proficient in nerding. lea.verou.me https://cdn.slidesharecdn.com/ss_thumbnails/turningtotheclient-side-120531170244-phpapp02-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/turning-to-the-client-side/13153980 Turning to the client ... https://cdn.slidesharecdn.com/ss_thumbnails/css3-secrets-111007050520-phpapp02-thumbnail.jpg?width=320&height=320&fit=bounds LeaVerou/css3-secrets-10-things-you-might-not-know-about-css3 CSS3 secrets: 10 thing... https://cdn.slidesharecdn.com/ss_thumbnails/polyfillingthegaps-111002094920-phpapp02-thumbnail.jpg?width=320&height=320&fit=bounds LeaVerou/polyfilling-the-gaps Polyfilling the gaps