dkharrat

It would also be useful to provide a way to convert the other way around (from a date to epoch).

I actually built a similar tool a while ago: http://timeconv.io/ that's similar to yours :) The goal is to provide a set of useful time/date utilities.

Is there an advantage to overriding the man command over the approach of just directly exporting the env variables in bashrc? I currently do the latter and I don't override the man function. I suppose overriding the man function would allow for man-specific customizations, but perhaps there are other good reasons too?

Type erasure introduces limitations on what you can do at runtime that forces a developer to write code to workaround it. For example, in Java you can't write a generic method that instantiates an object based on the type of the generic. The workaround is typically to pass in the Class type as an additional parameter to the method, which in theory should not be necessary. A lot of JVM-based languages are required to introduce additional complexity in the language to simulate reified generics (e.g. Scala's Manifest/TypeTag classes).

Doesn't Airbnb fall in the same category? Renting out your property for a few days to complete strangers requires a lot of trust, and yet from what I can tell, Airbnb seems to have overcome this hurdle.

I do agree there was a trust issue with Homejoy (I've personally tried them once and had similar concerns). But, I don't believe the issue was that they were in an unviable business where trust can't be gained, but rather they didn't have the right mechanics in place that help develop the necessary trust between the consumer and the cleaners.

Not entirely sure, but according to its github page[1], you can have it use the OpenJDK classes for a "conventional JVM".

[1] https://github.com/ReadyTalk/avian#building-with-the-openjdk...

An example where kill -9 can screw things up is killing a database process (e.g. MySQL, mongo, etc). Killing it with -9 will most likely lead to data corruption/loss, as the process might be in the middle of flushing to disk for example.

> If I understand WebRTC correctly, once the link is established, all communication is peer to peer.

In general, it's peer-to-peer, but for clients that can't communicate peer-to-peer for whatever reason (usually due to certain NATs), a relay server is used as an intermediary. To the user it's transparent, so they can't easily tell if it's peer-to-peer or not.

It's based on the WebRTC standard, so in general, yes it's peer-to-peer. However, in cases where the peer-to-peer connection cannot be established (e.g. a user behind symmetric NAT), then a third-party relay server is used (called a TURN server) which acts as the intermediary between the peers (sort of like a proxy).

This is pretty cool.

On a similar note, anyone know of equivalent options for iOS? I see a few open source implementations, but none that are actively developed. There's SocketRocket, but that's just vanilla WebSockets.

I disagree. Yes, MVC provides a pattern that allows views to be input to the user, but if it doesn't make sense for your app, it's perfectly fine to make the view "read-only" and still abide by the spirit of MVC.

If you're claiming that regular HTML views are compliant with MVC because they have HTML links, one can argue that some RSS readers convert the reference links from the RSS feed to actual HTML links that you can use to navigate to the individual RSS item. How is that different than a regular HTML view with links?

Can't wait for the Light Table IDE to support this language :P Debugging will be so much easier.

Same here, though I also miss WinSCP.

I believe SEO is one of the main things that hinder client-thick architecture adoption for many apps that depend on their content showing up on search engines, especially among content-driven websites (e.g. Stackoverflow, Quora, etc.). But I agree, all signs are pointing at the direction of thick-client implementations and eventually search engines will solve the indexing problem.

This is awesome! Major improvements since 1.4.

Even though the main use case for Bootstrap seems to be for rapid prototyping, any thoughts on using it for a production app (but perhaps custom-themed), instead of rolling a custom design altogether? It seems Bootstrap has matured to the level that it can be used as for most projects with little customizations if any. A lot of what I read in the comments imply that Bootstrap is great at prototyping an app and once that phase is over, you throw it all out and start developing a custom design based on what has been prototyped. Why can't one just stick with Bootstrap and customize it as needed?