Yeah I agree with this. From a standpoint of access to the minds of more human beings you can’t justify Esperanto when there are things like Spanish and Mandarin you could learn.
Lojban is for thinking unambiguously and more logically. It's good for programmers but also exactly the kind of language that an artist or poet wouldn't want to learn.
The Internet broke the whole idea of charging for a digital copy of something. We’re seeing a struggle of powers as old power tries to cling on to the idea of charging people for digital copies but it will end sooner or later. One needs to think outside the box of capitalism being an appropriate system for all aspects of society.
Talk about this kind of journalism out of context (why you don’t trust a particular study, for instance) and you’ll be called a quack or conspiracy theorist.
Number of things written in a language isn’t really a good measure for its quality. There was a time when most things were written in COBOL or assembly. I think the main reason people write so much BASH is because there by default.
Perhaps we could use a similar law for software that says you have to opt-in for that. If you try to install Adobe Reader on a Windows PC, for instance, you have to untick to install the Ask! toolbar. I don’t like that
Yep same here. org-mode FTW! You can use it as a personal wiki only able to keep all your data in plain text: no web server or database required. I still use filesystem as my primary organization so I only use hyperlinks occasionally. I put the whole load in dropbox so I can access any of it from my phone.
> Since "$" is used by CSS preprocessors for variables that work in a different way
A complete perversion of priorities. CSS generator languages change and go in and out of fashion all the time but CSS itself will be around for a very long time. They should make the best decision for the future of CSS. Generator languages are inevitably going to need to change to take advantage of any new feature anyway.
Firefox has too many bugs and when you file them they don‘t get fixed very quickly at all. That’s why it isn’t my primary browser. Maybe something about that should be in this document.
I don’t see how you have inferred a fat controller and skinny model from my description. In fact I use the terminology of interfacing to describe what others here have interrupted back into MVC terms as a controller. That should be an indication as to the extent of its role i.e. not that large
My action layer is definitely fatter than the usual model because it does all the real work (that which persists) associated with a particular request. You could argue it is equivalent to involving several of the traditional models. I think it might also be fair to state that this represent an absence of architecture in that particular area and I would agree but there is nothing to suggest that you couldn’t create models with the action layer if you felt it was useful. Strictly speaking I’m against that sort of thing until I see a good case in front of me why I should do it. Writing queries is not so bad that I want to put something in front of it to automate it
Oh, I’ve just realized another difference. The model, as I refer to it is different from that in MVC. In MVC the model is usually a representation of database tables or "an interface defining the data to be displayed or otherwise acted upon in the user interface" (WikiP). For me it is the bit that preforms whatever work the user requested. So it’s pretty misleading of me to call it the model really because I’m not really all that concerned with modelling anything, I shall refer to it as the action layer from now on, I think