2 ms·
So far I've spent several weeks of my spare time forensically decomposing the documentation, nearly line by line. It's been very slow going. The main thing I'v
by jacques_chester 13y ago
So far I've spent several weeks of my spare time forensically decomposing the documentation, nearly line by line. It's been very slow going.
The main thing I've learnt is that Angular is elaborate. Each time I get my head around something, I realise that my previous understanding was utterly wrong.
The docs are sufficiently vague that I spend a lot of time looking for secondary sources or just reading the code directly. Sometimes the code is self-documenting. And sometimes it's neutron-star dense.
But what I'm seeing, I really like. I think that directives are a big part of the magic -- building the HTML you wish existed and then writing your app in that domain-specific HTML.
- Chris2048 13y agoI tried to get into angular, but it seemed to hard beyond the tutorials. Aren't frameworks supposed to make things easier?
- jacques_chester 13y agoThey're meant to make particular kinds of complex application easier. I think Angular's problems is that docs are frankly dreadful. They tell people to fork it and improve it, but go look at their github pull requests. There are hundreds.
- durzagott 13y agoA fellow HN'er posted a collection of all the best tutorials and docs into one cohesive training programme. It's an excellent resource for those of us trying get our heads around Angular's woeful documentation: Website: http://www.thinkster.io/ http://www.thinkster.io/ HN Submission: https://news.ycombinator.com/item?id=6072383 https://news.ycombinator.com/item?id=6072383