{"blog_url":"https://t-wada.hatenadiary.jp/","author_url":"https://blog.hatena.ne.jp/t-wada/","url":"https://t-wada.hatenadiary.jp/entry/20050221/1108998847","image_url":null,"published":"2005-02-21 00:14:07","description":"Ruby on Rails\u306e\u4f5c\u8005David Heinemeier Hansson\u306b\u3088\u308bweblog Loud Thinking: Broadcasting Brain\u306e\u6700\u8fd1\u306e\u30a8\u30f3\u30c8\u30ea\u3067\u3059\u3002\u672c\u6587\u3082\u30b3\u30e1\u30f3\u30c8\u3082\u8208\u5473\u6df1\u304f\u8aad\u3081\u307e\u3057\u305f\u3002\u4ee5\u4e0b\u3061\u3087\u3063\u3068\u5f15\u7528\u3057\u307e\u3059 One of the clear goals for Rails from the start was to stay at the infrastructure layer. I didn't want Rails to succumb to the lure of high-level components like login systems,\u2026","type":"rich","provider_url":"https://hatena.blog","categories":["memo","ruby"],"html":"<iframe src=\"https://hatenablog-parts.com/embed?url=https%3A%2F%2Ft-wada.hatenadiary.jp%2Fentry%2F20050221%2F1108998847\" title=\"The case against high-level components - t-wada \u306e\u65e5\u8a18\uff08\u65e7\uff09\" class=\"embed-card embed-blogcard\" scrolling=\"no\" frameborder=\"0\" style=\"display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;\"></iframe>","version":"1.0","title":"The case against high-level components","provider_name":"Hatena Blog","blog_title":"t-wada \u306e\u65e5\u8a18\uff08\u65e7\uff09","width":"100%","author_name":"t-wada","height":"190"}