API in this case refers to it's original meaning, that is, the interface that is available on a specific "class" of objects. Here, the "class" of objects are mimicking haskell like typeclasses.
The chart on the fantasy-land github page demonstrates the interfaces available on each typeclass. For instance, a Maybe is a functor, so it has the map interface. It's also a Monad so it has the chain interface.
Unfortunately, API is a loaded term and I think the author doesn't do a good job differentiating from the common usage of the term.
Even in that meaning, it still doesn't make sense. Say there was an abstracted twitter standard defined in an RFC, and a library was provided for interacting with it. There is no Twitter(tm), just implementations of the twitter RFC.
Even then, I need to know what the names of the properties are that I have to provide to the fantasy-land-compliant-whatever. Being an expert in fantasy land doesn't tell me that "message" is the property that contains the body of the twitter-compliant message. I still need an api.
The ability to deploy the same code to front end and back, for me anyway, works out quite well. With browserify, I can write common utilities and require the code using the commonJS module system. It's pretty seamless. Doesn't change the skill set necessary for front end development in any way though.
1) Though it's not fool proof (because there is no upper limit on file size), a large JavaScript application that consists of many scripts can be minified and concatenated, reducing download times. The situation can be made better with aggressive caching too, not to mention the client side cache, so I don't see how JavaScript can really be a culprit in "slowing down the internet". Seems a strange idea. If a client side application is written poorly, I can see how that might lead to the perception that JavaScript is to blame, but undeservedly so. I blame the mediocre developer for that :P
Granted, Verold does not handle 3D _creation_ on the web. Instead we are building a platform for creating interactive experiences using 3D content. Eventually it will lead to a full fledged game development platform. Check it out!
I guess, I mean, I love software development and even if I were at home I would be doing it. Also, if I were leaving my day job to start my own business and I... wanted time off before doing it, I would be very concerned I was making a bad decision.
Anyhow, I've been fortunate to have jobs with awesome PTO. With 20+ days of PTO I didn't see the necessity of going a few weeks without a paycheck.
Agree with your assessment. I searched high and low for a font that serves as a programming font for quite a while. For the longest time I loved Inconsolata and some of it's variations. After a while I got tired of it though. It seemed... sloppy, even though I loved it at first. I think what it lacked, for me at least, was consistency between glyphs. Some where straight and angular, while others curved and it just didn't fit. Now I have settled on DejaVu Sans Mono and it seems to be working for me. It's very balanced and the glyphs are very evenly spaced and take up pretty much the same visual foot print for each glyph. Highly recommend.'
This font that OP is showcasing isn't terrible, for a first pass, but there are some problems (funny lower case f curve really bugs me. It's overly pronounced) that need to be ironed out.
I prefer when the font is rather thick than thin, which leads to using sizes like 14, and I've found that Lucida Console and DejaVu Sans Mono work best for me.
The former in Notepad++, the latter is perfect for Eclipse, because Eclipse has a very small spacing between the lines (not configurable) and many other fonts look too condensed due to that.
I've actually started using Deja Vu Sans Mono for a programming font. There are definitely still some annoyances but it does seem to do better than most I've come across.
The chart on the fantasy-land github page demonstrates the interfaces available on each typeclass. For instance, a Maybe is a functor, so it has the map interface. It's also a Monad so it has the chain interface.
Unfortunately, API is a loaded term and I think the author doesn't do a good job differentiating from the common usage of the term.