Introduction speech about my up and coming Wade.Go client-side centric web framework for Go. The project is at http://github.com/phaikawl/wade

1. Wade.Go
Web development in a brand new way
https://github.com/phaikawl/wade

2. #whoami

3. Wade.Go =
+

4. Enter Go
● Announced in 2009, reached 1.0 in 2012
● Sponsored by Google, developed by the community
● Rising star in cloud & server side development

5. Enter Wade.Go
● Client side centric web framework (think AngularJs)
● NOT a Javascript framework

6. Javascript

7. Maintenance headache

8. Why Go
● Strictly typed
● Compiled (in no time)
● Simple
● Friendly
http://golang.org

9. Why Go
C++
C#
asm
Javascript
Typed, compiled Dynamic, Interpreted

10. Why Go
Although we expected C++ programmers to see Go as an
alternative, instead most Go programmers come from
languages like Python and Ruby.
Rob Pike

11. Why Go
“Most of the appeal for me is not the features that Go has,
but rather the features that have been intentionally left
out.”
tdxxx on Hacker News

12. TJ Holowaychuck
On TJ Holowaychuck's blog
medium.com/code-adventures
“
“

13. Gopherjs

14. How Wade.Go renders the page
Renderer
DOM interface
Virtual DOM (go.net/html) Js DOM (jquery)
Server renders the page
as HTTP response
Browser renders the page
Application
Search engine
crawler
Web Users
Before JS
After JS

15. As a result
● SEO-friendly
● Write the page once and only once
● Renders content normally even if Javascript is disabled
or too slow

16. How it feels
● Easily reuse code between client and server
● Flexible data binding
● HTML reuse
– Custom elements
– The page engine

17. Conclusion: Why Wade?
● Client side centric AND still SEO friendly
● No more maintenance headache
● Write code in a great language
● One language for both client and server

18. Getting involved
● Github project: https://github.com/phaikawl/wade
● Contact me:
● Email: phaikawl@gmail.com
● Facebook: https://www.facebook.com/perfwill