Microblog
in reply to @ 2015-325.144ZThis is the model companies like withknown.com use
in reply to @ 2015-325.140ZWell, basically the way it works is that you charge people to use the service. Then you offer to anyone who is a user access to the source code under a free license.
in reply to @ 2015-324.698ZI would simply charge people for using the service if they felt it will be useful to them
This model is still perfectly acceptable for freedom-respecting software
in reply to @ 2015-324.576Zi.MX6 systems like the Hummingboard aren't even listed
in reply to @ 2015-324.068Znitrokey
in reply to @ 2015-324.030Zffmpeg will do pretty much anything to anything 🙂
in reply to @ 2015-323.979ZThe author seems completely disconnected from the average museum visitor. If the photos do not harm the content and visitors find they enhance their experience, then what is the problem? That you personally dislike their photos? No one is making you look at their photos.
in reply to @ 2015-323.854ZFrom
https://d.wifo.org/t/places-to-find-commons-news-and-new-works-projects/162:
in reply to @ 2015-321.777Z
The constraints for Monad code using fail become (Monad m, ApplicativeFail m) => instead of the simpler MonadFail m =>. If we expect the common use of fail to be in Monad — not Applicative — do-notation, this leaves us with more verbose constraints.Why is this a problem? Having multiple constraints when using multiple features is a normal and useful feature of Haskell.
in reply to @ 2015-321.773ZIf I have
MonadFailandApplicativedefined and use ApplicativeDo, will it use myfaileven if my context is notMonad?