I don't think the same teams are working on video decoding and VR browsing.

No but they're pulling funds from the same pot.

That's a software implementation though. These new cards have actual hardware specifically for that.

When do you get in though?

8:30. My hours aren't all that terrible, but after burning the candle at both ends for the better part of a decade of grad school, I'm a little worried about burning out.

Cycling might help with the burn-out. The exercise is good for you. Getting out of a stressful drive is good for you. Etc. Even if the ride is a bit longer, it's probably a net positive. Especially if you end up at the gym or jogging anyways - you get to double-count the bike commute as part of your workout.

You didn't mention riding after dusk as a problem, but there are plenty of good bike light options available now. LEDs and batteries have come a long way in the last 5-10 years and small, rechargeable lights are now powerful enough to provide adequate lighting for nighttime commutes (some are even bright enough for daytime use - so cars see you better).

Thanks for the lighting tips. I'm actually taking some urban cycling classes next month. I think at this point I need knowledge and confidence to make cycling a part of my commute.

It might introduce temporal artifacts, which would not be seen in stills.

Does this support Objective-C++? If not, do you have any plans to implement support for it?

I have not tested it, but it should be a relatively straightforward to get working. Feel free to file an issue on github.

In deferred rendering the cost of lighting is still dependent on the number of lights. In forward rendering it is dependent on both the number of lights as well as the scene geometry. You can apply various additional techniques to make each light much cheaper though.

You're not really being fair here. You could just as well distribute all needed dll's with the app. In fact, that's pretty much what Electron does.

> And C# is no slower than D.

I very much doubt that. Do you have anything to back up that statement?

Benchmarks are tricky and hard to find for dlang as its not that popular, but I have common sense to back that statement. Dlang garbage collector is really really slow for now [0], and C# has a very fast GC and overall is almost as fast as zero-overhead languages like Rust or C++ [1]. So, its reasonable that for anything that involves GC (we all can agree that web server does) D is not that fast as manual memory management languages yet.

[0] https://olshansky.me//gc/runtime/dlang/2017/06/14/inside-d-g...

[1] http://benchmarksgame.alioth.debian.org/u64q/binarytrees.htm...

How would WebAssembly ever do that?

Easy, it is just a matter of creating a compiler backend for Java, Flash, Silverlight that target WebAssembly instead of their original bytecodes, then bundle it with their own runtime compiled via emscripten.

There are already a few projects doing exactly that.

One could even create a ActiveX compliant library, that via emscripten would be able to target WebAssembly.

Vægtafgift is not a thing anymore, there is only ejerafgift now.