3 ms·
The idea looks pretty good, and it's OK if someone hacks it for themselves, but the implementation is lame, in my opinion. I understand that I can be a bit off-
by tmcb 14y ago
The idea looks pretty good, and it's OK if someone hacks it for themselves, but the implementation is lame, in my opinion. I understand that I can be a bit off-topic or ranting worthlessly on a simple hack that was intended to be just that, a simple hack.
It looks like people forgot how to develop simple protocols for this sort of thing. A simple protocol for remote named pipes, a client and a server, and a wrapper/gateway for dotCloud/HTTP wouldn't take a (very) long time to develop, wouldn't be completely dependent on an external service, and would probably develop into something bigger --- even for anonymous file sharing!
I really would like to know why programmers, in general, seem not to be doing this sort of thing anymore. Sorry if it looks like some sort of misplaced criticism, I'm posing all of it genuinely as a question to the community.
- gbin 14y agoOk first I tend to agree on the general remark : I have been in software development for a long time and a lot of recent solutions look totally overkill / overengineered for me. But here, it makes the thing really easy, it autodeploys, the underpinning technology (0mq) makes the socket rendez-vous easy. For a first proof of concept I just love the usability ! Now yeah you can do it by installing a proxy on one of your servers ... ha but first you need a public server on the internet, tweak the services, expose it a little bit more to hacks etc etc ...
- jeremyjh 14y agoResume Oriented Arcitecture
- gbin 14y agoLol, love it :)