Golang Angularjs Tutorial part 3 - REST and ngResource

preview_player
Показать описание
In this episode we create a REST backend in Go and consume it in Angularjs with ngResource.

The code is here:

Subscribe/like/comment if you'd like to see more.
Рекомендации по теме
Комментарии
Автор

would love to see another project like this. nice variety of topics covered!

sedetweiler
Автор

Great tutorial man! Really easy to follow. Enjoyed watching it!

RushOrbit
Автор

Thanks again, I am finding your tutes immensely useful for my current project.

Some new things I have learned lately :
- Zero problems using Go with UI-router.
- tiedot works well as an embedded database layer in Go for storing objects. Worth checking out, fast, and introduces no extra dependencies.
- Integrating websockets with Go + Angular works better than expected too.
- Go + Angular together makes programming fun and powerful all over again.

Best part - with other tools, developing Windows ports of these web friendly client-server style projects has been a nightmare of the worst sort. So bad that it is not worth attempting half the time.  Python, Ruby, Node, etc - all do the job, but are bad news to deploy projects for Win32 based customers who are not tech savvy.

Go actually fixes that that none too small problem, which is pretty darn amazing.

Many thanks for easing that transition (to Go), with the help of these no nonsense tutes. Well done !

steveoc
Автор

Thanks for all the tutorials, this is making angularjs integration and initial Go usage absolutely painless. Thanks!

dktree
Автор

Great 3 video tutorials on AngularJS and Go.  Thanks a bunch.  I am inspired to come up with my own app using AngularJS and Go.

ClaronTwitchell
Автор

This dosent work geting a

"404 page not found" error at the localhost/static/books.html

Yoieh
Автор

nice tutorial. easy to understand. thanks

ajyku
Автор

calicoJake  Thanks alot! This covers a hole in the Angular docs for ngResource. Namely, how to use the resource to add to a list, and to update the list in the client afterwards. One question though: How would you update the list in the client if you didn't want to reload the entire list? Wouldn't that be advisable, instead of having the extra call to fetch the entire list again?

magne
welcome to shbcf.ru