{"id":872,"date":"2015-01-13T15:43:31","date_gmt":"2015-01-13T20:43:31","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/acts\/?p=872"},"modified":"2019-02-26T16:32:47","modified_gmt":"2019-02-26T21:32:47","slug":"kurogo-open-source-and-foot-in-mouth","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/acts\/2015\/01\/13\/kurogo-open-source-and-foot-in-mouth\/","title":{"rendered":"Kurogo, Open Source, and Foot in Mouth"},"content":{"rendered":"<p>Several years ago I worked on a mobile project using modo labs&#8217; kurogo. What we did was simple enough. It provided a mobile framework, using its own phonegap-like technology as a way to &#8220;compile&#8221; we code into native apps for android and ios. When we were a decade behind in mobility, it provided a means to do things that sounded like they should be done.<\/p>\n<p>Fast forward to present. Modo labs is touting their new v2.0. That&#8217;s interesting, right? I knew their 1.x platform and was not impressed, but this is new. In the wake of the new rages in mobility (spa&#8217;s and APIs) I couldn&#8217;t wait to see what they had come up with.<\/p>\n<p>But wait I did. It took several months to provide me with code to muck with. A project that really enjoys calling itself open source &#8212; but they&#8217;re not making v2.0 open source. That&#8217;s the secret sauce. Okay, fine, maybe they&#8217;re having trouble making money with an open source project. I shouldn&#8217;t judge it too harshly on that.<\/p>\n<p>Well, I finally got into some training on the product. Got my hands on the code literally 20 minutes before the training. The setup docs were poorly written. In a time where vagrant and docker are on my mind a lot, not having a VM, having to set things up manually seemed like taking a step backwards in time.<\/p>\n<p>Finally got into the nitty gritty, and quickly noticed not much had changed. They are still peddling the same design decisions they made a decade ago. A new enhanced administration, but the apps being created will look pretty much the same. The configuration files write the application for you. As a developer, this was disappointing.<\/p>\n<p><strong>But I realized they\u2019re not making a product for developers. They\u2019re creating a product for configuration managers.<\/strong><\/p>\n<p>I was floored when I saw PeopleSoft \u201cdevelopment\u201d for the first time. It\u2019s the future though. It\u2019s a way to create applications without having to pay for developers with specialized education \/ experience.<\/p>\n<p>As the people who are putting together the University\u2019s PeopleSoft campus solution I\u2019m sure will tell you, it\u2019s a double edged sword. A LOT can be done by people with minimal training, but getting outside of the box, creating \u201cexperiences\u201d becomes borderline impossible.<\/p>\n<p>That said, Kurogo I\u2019m sure has its place among a certain breed of application. And I hope it will take off, and people find use for it. But <em>it is an elegant product, for a more civilized age.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Several years ago I worked on a mobile project using modo labs&#8217; kurogo. What we did was simple enough. It provided a mobile framework, using its own phonegap-like technology as a way to &#8220;compile&#8221; we code into native apps for android and ios. When we were a decade behind in mobility, it provided a means [&hellip;]<\/p>\n","protected":false},"author":4571,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[111257,1029],"class_list":["post-872","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-mobility","tag-open-source"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/872","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/users\/4571"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/comments?post=872"}],"version-history":[{"count":1,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/872\/revisions"}],"predecessor-version":[{"id":873,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/872\/revisions\/873"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/media?parent=872"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/categories?post=872"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/tags?post=872"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}