skip to main |
skip to sidebar
RSS Feeds
但是作者又問:
身邊一些技術背景的朋友,對 API 遲遲未能開放,看不到各式各樣 APP 的狀況,都是持負面看法的,所以上述疑問是很多人共同的看法吧。
Google的做法究竟是對是錯呢?
A Story of a man pursuing understanding and being understood.
Thursday, November 17, 2011
High Scalability談發表的Google+開發工具介紹時,提到為什麼Google+ API推出速度緩慢的猜測:
So the approach is: make the UI first, make it fast, and then wrap an API around whatever evolved. A controversial methodology, but given the imperative for making a responsive UI, it makes sense.
但是作者又問:
However good this approach is for creating fast UIs, it's death for feature development and fast responsive innovation. With an API you can develop in parallel and release stuff faster and iterate faster.
身邊一些技術背景的朋友,對 API 遲遲未能開放,看不到各式各樣 APP 的狀況,都是持負面看法的,所以上述疑問是很多人共同的看法吧。
Google的做法究竟是對是錯呢?
0 Comments:
Labels - 文章分類
30 minutes
(5)
algorithm
(3)
Blogger Hacks
(4)
cobrasonic
(3)
Coffee
(53)
Data Mining
(47)
database
(3)
database security
(6)
education
(14)
Favorite
(35)
google
(17)
Have Fun - 去玩吧
(25)
Infographic
(1)
InternetWatch
(73)
life is like that
(34)
Mathematics
(8)
murmur
(598)
Music
(12)
Netflix
(9)
Nostalgia
(4)
posterous
(137)
Python
(4)
ramblings
(154)
Recommender
(40)
research
(43)
search
(15)
security
(4)
social network
(1)
Software
(2)
Telecom
(1)
Ubuntu
(4)
Video
(62)
visualization
(1)
writing
(2)
專案管理
(3)
文件
(1)
書齋書摘
(38)
管理
(6)
網海泛舟
(51)
職場憶往
(2)
詩戀
(39)
鏡頭人生
(51)
Copyright 2009
The road less traveled by. Powered by Blogger
Blogger Showcase - Submit Your Blog Blogger Templates created by Deluxe Templates
Wordpress theme by Site5
Blogger Showcase - Submit Your Blog Blogger Templates created by Deluxe Templates
Wordpress theme by Site5

