It is this moment when you search for the big red lever with sign: "EJECT!!!"
1,059 karma · joined October 9, 2011
It is this moment when you search for the big red lever with sign: "EJECT!!!"
Update: it still can serve only one request at a time, but looking forward for some progress there...
Now, with this in hand can we have for instance a multithreaded (or in some other parallel way) web server or even REST API for R?
Talking from the practical perspective, the biggest problem with wide adoption of R is the problem of integration. Sometimes you just want to have a single module in R, and the rest of the system in some other technology. I know there are ways to do it, but not without quite high technical debt. On the other hand having native microservice-like integration could probably help.
I know we are close, but not sure how close.
PS. See the comment above about the css styles. Probably it's some browser dependent handling of small caps
I remember playing it on some 486 PCs, now unimaginable, but then it was really great!
There was even a ~700KB (!) version, stripped down to the most necesary: TCP/IP multiplayer with only 1 level, but man, you could bring it to the classroom on a 1,44MB floppy!
But hey, Apple can now impose the change from the position of power. And they have Beats who will follow this change...
1) languages with this high level of abstraction are very nice if your scenario maps perfectly to its usage (e.g. the wikipedia analysis given in the video). Everything is nicely vectorizable, etc. But if there is some quirk in your data, then sometimes you need to go the usual way, and the Q is of no help (no better than any other language), with the difference that now you do some very inefficient things with those "stinky" loops.
2) it's a question of taste, but I find Q syntax a bit unusual. Probably more time you need to think how to fix your simple problems with this clever one-liners than simply, well solving them...
3) legibility: for all of us working in software developement, we know how much time we waste due to illegible code. Finding bugs, etc. Here this is raised to the new level... of difficulty
4) this is a bit exaggerated, but I don't see how I could use Q in something bigger? Is Q only a scripting languages for one-off mini-batch programs? For instance R has this problem of not having any well-defined project structure, and it is hard to do many things, for instance: bigger programs are hard to maintain and debug, stream processing with R is pain in the ass. Server-side stuff is a little bit shoehorned (Shiny server is cool, but then it's just one-thread thing for serving filtered dataframes to ggplots)
It is cool niche language, but for smart simple analyses, nothing too complex, as it will abstract you from details to your loss.
I think that regarding the near infrared light a regular CCD element could be useful as well, as those are sensitive to infrared too. The only problem is to filter the visible light to leave the infrared spectrum only. Also be sure that the ccd doesn't have a IR filter (some does).