207 karma · joined November 12, 2011
"Finnish schools are obliged to introduce a period of “phenomenon-based teaching” at least once a year. These projects can last several weeks. In Helsinki, they are pushing the reforms at a faster pace with schools encouraged to set aside two periods during the year for adopting the new approach. Ms Kyllonen’s blueprint, to be published later this month, envisages the reforms will be in place across all Finnish schools by 2020."
But think of this as a step towards commoditization of services. It's a small step from "Hey Siri, get me an Uber" to "Hey Siri get me a ride", whereupon an Apple bidding algorithm gets you an Uber, a Lyft, a GrabCar, etc. based on e.g. price, wait time, and reviews. As a user, I wouldn't necessarily care which platform got used as long as it meets my need.
That being said, Pedestal's sweet spot definitely doesn't seem to be simple interactivity sugar a là jQuery, but I would by no means say it's not suited for startups. Scalability just happens to be one of the benefits of the architecture they chose.
a) "Don't touch the markup without an explicit agreement between the two of us."
b) "Please make sure you have an element with a data-content-for='user.username' somewhere in the HTML."
<!-- Original -->
<span class="username">joe</span>
<!-- New -->
<span class="username"><strong>joe</strong></span>
Updating the selector in the template is easy enough but seems a bit tedious if the design team decides to go for italics next week. Another option would be adding another CSS class or a data attribute to indicate which element should wrap username.How do you usually handle such scenarios?
Missing Rails I18n, SimpleForm, or validations? Clojure has you covered:
* https://github.com/ptaoussanis/tower
* https://github.com/asmala/clj-simple-form
* http://clojurevalidations.info/
Need more specialized libraries? Take a look at ClojureWerkz:
Having tried hard to understand the rather labyrinthine source of the original SimpleForm library, I was astonished by how easy Clojure made writing a similar library, clj-simple-form. The key contributing factors were Clojure's emphasis on simple data structures and powerful functions as opposed to classes, and the ability to pass around functions just like any other objects. For a lot of projects, I find ease of extensibility to be more important than ready libraries.
As a concrete example, a small hobby project I did resulted in a fairly comprehensive library of Bootstrap helpers with very little effort:
* https://github.com/asmala/giddyup
I don't have much experience with Enlive but I find the approach is intriguing. On paper it seems perfect for clean separation of markup and logic, but you're right that careless use of the library leads to tight coupling due to the selector naming. I wonder if it would be possible to circumvent this issue using custom HTML attributes or even pseudo-CFML custom tags to indicate logical units in HTML?
That said, it's not quite as cut and dry, given that API compatibility goes a long way.
Going for YC is clearly a great starting point for building a scalable business, so I wonder what the business logic will look like. As in genuinely, positively interested to know. :-)
Now don't get me wrong, I'm definitely cheering on Google and find Oracle's case despicable and absurd, but still.