Lytro's basic building part is an array of microlens, a rather expensive piece of hardware that also limits effective resolution dramatically. This is why the title here touts "single lens".

The array of microlens captures the light field, something that's used for computational focus in Lytro. However, capturing the lightfield in a microscopic imagery of translucent sample does allow you to post-fact adjust the viewing angle of the sample (to some degree), therefore do 3D imagery in microscopic scales.

Anyone knows where to access technical information about the actual study, or how did they conducted the IQ test? ConceptNet is just a database + a library with some NLP parsing tools and database (the concept hypergraph) accessors, but I wonder how did they actually conducted the test as that doesn't seem to be a trivial extension of the available tools...

You should clarify what are you after. Do you just need a place where to push + pull, or are you looking at something akin to the GitHub experience?

Aside of GitLab, also consider Gitorious. I'm not sure about how easy it would be to get GNU Savannah up and running, and Git is only a small part of what it does.

You can also find GitHub Enterprise interesting if you are ready to pay; I assume(!) it will call home to verify the licence though so making sure no stuff is sent to NSA may be tricky. ;-) Upside is minimal setup hassles for you.

You may also find the Girocco platform interesting (CGIs for project index + project management web interface, and gitweb; much smaller than the above-mentioned ones so you have a good chance to actually review all the code for yourself, but it's also more raw experience; disclaimer: I'm the main author of Girocco).

If you are fine with a simpler experience, you can simply use git-daemon (or purely SSH and git installed on the server), possibly gitolite to easily manage user access and gitweb/cgit for a web interface - there's no special magic, the Git repositories are just directories on the server.

I agree. For me, the ratio is slightly less than 1:1 for repeat lectures from the last year that I decided not to change much (maybe just reordered stuff). But for new classes, I can easily spend at least the whole evening (let's say 4-6 hours) per class preparing it; to be comfortable in the subject to answer most questions, decide what to focus on, digress based on the students' interest, I need to be sharp on the material so that I get to tell about 1/3 of everything I re-study for the lecture (proofs I won't cover, historical backgrounds, alternative approaches, etc. - folks like me who have atrocious memory lose here as for me it's not enough to be sharp on the details if I've read it just 1 or 2 times when I was just curious/studying the subject in the past); add to that preparing homework or exercises to make sure they actually make sense, build on the new knowledge smoothly and can be solved with just the material we have covered, and so on. As I've gained more experience I often even don't bother with a test lecture anymore so that's not counted in (though my lectures would improve if I could convince myself to reserve enough time for one).

So, you will end up with just about 8 hours per week spent just giving a single weekly class. This semester, I went easier on myself and decided to introduce no new classes (aside of one topic I researched during the xmas break), so I just spend the morning sharpening up for my two classes in the afternoon on the day I teach, and I even get around to do some advising for my students on that day if lucky - happy me.

It's not so simple for two reasons:

(i) Builtins are used only when gcc wants to inline their code. This may not always be the case. Their usage may (I think) also depend on the nature of the arguments (e.g., are they constant? is their length known? etc.). And there are other weird cases (passing memcpy() function pointer or whatever). Even if you don't explicitly disable builtins, your program may call these functions.

(ii) This specific part of the announcement concerns ifunc-related optimizations. This means that the version appropriate (most optimized) for the processor the program is _currently running on_ is chosen at runtime. In x86 world, at runtime (during the first call to the function), a SSE4-enabled function may be chosen over default function if the processor supports SSE4, for example. And you have just a single binary of your program to handle.

Ok, I agree that it is plausible you can get lost with Apple Maps without being stupid at all. But isn't it silly to drive these distances through the wilderness without having a sixpack of 1.5L water bottles and a canister with extra fuel in the trunk? (Or at least one of these.)

One would assume that "world modification" (monad; in this case, visual I/O) does not fit the restriction "only ever accesses read-only data, or modifies local data that is unaccessible from anywhere else" and as soon as you are showing something to the user, that blocks the auto-threading.

Then again, if you are drawing map tiles, the order you draw them in doesn't matter - so this goes to show that in some situations, there's no way around the programmer actually having to stop, think and declare whether the program's contract allows it to do some user-visible operation in parallel.

Yes. I think key in my good experience with RPi is that for all of them, I'm using the same type of uUSB PSU. It is actually a rather cheap OEM part, but it works reliably and I think many of the experienced problems with RPi stem from bad PSUs.

About 30 boards (ordered from European Farnell, IIRC all made in UK) went through my hands in the past few months; I had no problem with any of them.

I would be the first to point out some dubious design choices and other not-so-good things about the Raspberry Pi, but myself I can't complain about defective items at all.

What software companies in Germany have average salary around 100k?

A lot of people complain about this hardware upgrade - some of them fear fragmentation while others are just disappointed and angry from recently receiving 256MB version. So I wonder, what would you do differently to handle this better?

One obvious thing is marking this as rev 2.1 or something so that it's clear what revisions you have or not.

Regarding the 256MB-512MB transition, I it seems to me to be in fact a difficult thing to do to make everyone happy. They already made one such surprise transition with rev 2.0. If you announce the transition in advance, you push sales down and _slow down_ the pace at which you are able to get the better version out to the customers (I wonder how much though - I think they should try it once to see the impact). I guess the $35 price tag does not enable any discount margins for older version. One possibility is selling new model for say, $40, until old model goes out of stock, but (i) this seems difficult to manage with huge demand and different stocks around the world, coordinating across two distributors, and (ii) people would complain about $35 being just a marketing ploy then just as they complain about $25 now (they probably do have some point here, but the foundation mentioned that they have (some) parts stocked for model A now already, so hopefully they meet their goal of producing this before the end of the year).

That seems similar to mourning the downfall of mainframes and high-power UNIX workstations and the rise of the PCs, and that people start using high level languages before taking the time to learn assembler and memory timings or whatever first.

In an ideal world, all competent programmers would be well versed in all the important aspects of programming and hardware. It's similar with MCU and EE projects. In real world, to get shit done, there are other important factors other than technical competency and lowering the playing field enables hacking electronics for people with little or no experience, only spotty technical understanding of what's going on at all levels, but with familiarity with other fields (e.g. gardening), enthusiasm, determination to pull the project through, documentation skills or whatever. The new projects aren't as perfect technically, but there's heck more of them and they are making ways to yet uncharted areas (and budgets).

What place where hackers live together do you have in mind regarding Prague? I'm living here and I'm not aware of any.