Fannon

15 ms·

121.
by Fannon 12y ago
Oh no, someone is thinking the obvious! ;)
122.
by Fannon 12y ago
It may be true that thinking your code through takes a LOT longer than actually writing it. But: Beeing able to put a thought / idea (once it's there) to code very fast is helpful. At least I can't hold an complex idea in my
123.
by Fannon 12y ago
Paperwork doesn't use its own cloud storage. You can host it either locally or at your own server. No problem using encryption, VPN tunneling etc. here. The fact that it's not a true cloud service could be seen as a downside. Your
124.
Ask HN: Any good resources / literature on the full web stack?
3 points by Fannon 12y ago|2 comments
125.
by Fannon 12y ago
Thanks- this is really great! Each time I've learned a new language, I've created a file / collection of files like this - as a personal summary and for use as a cheatsheet. (Can recommend this definitely!) But this is much m
126.
by Fannon 12y ago
I can see the problems of the current situation, too. I guess everyone involved does. But what's a viable alternative? I have seen a few project that were completely build on its own, without dependencies on external libraries. Not onl
127.
by Fannon 12y ago
babun looks really interesting. So far I've worked with PortableGit + ConEmu which works quite fine - just updating is not the nicest experience.
128.
by Fannon 12y ago
What NPM can't do is the async workflow of Grunt watch (or serve) and dynamically trigger specific (sub)processes in real-time. Turns out, this is the main way I'm using Grunt. Also some plugins are complicated (or dynamically) to
129.
by Fannon 12y ago
The more I think about it, I dislike the idea of WYSIWYG editors. Not that I would force normal users into writing markup, thats even worse. But in order to deal with browser inconsistencies and potential new and interesting features, the i
130.
by Fannon 12y ago
I had to try to believe it.
131.
by Fannon 12y ago
Well, there are reasons and it's getting more common. In fact most modern browsers, even on a smartphone, may have more computing power than a server if you consider that the client has only to serve itself and the good performance of
132.
by Fannon 12y ago
My problem with that is: Most modern web-apps run much (up to completely) in the browser. And the Semantic Web Stack is very heavy if you want to use it client-side. Here every kilobyte counts. Well, you could directly query a SPARQL databa
133.
by Fannon 12y ago
I've looked into Semantic Web Technologies for a year now and trying to come to a personal conclusion at the moment. This is my current state, through some of this may be premature: PRO: * I can see that the semantic annotation part of