http://pad.haroopress.com/ - Not sure if open source https://github.com/bianchimro/markgiu - last updated 7month ago https://github.com/danielking/docular - last updated 9 months ago
These are node-webkit editors, as an easy-to-contribute example.
322 karma · joined April 28, 2013
http://pad.haroopress.com/ - Not sure if open source https://github.com/bianchimro/markgiu - last updated 7month ago https://github.com/danielking/docular - last updated 9 months ago
These are node-webkit editors, as an easy-to-contribute example.
Ideally I'd love for there to be a way to explicitly modify database structure, easily and predictably, and have it all just work in several SQL dialects, so that you could meld the engine and the admin interface etc. to any project whether it's a blog or not. I feel like most of these bloggy engines make database structure either invisible or too difficult to understand and minipulate.
Definitely want to open source it proper, build it to be extendable etc. Don't care about competing with anything else, just want to be another option out there. Nothing all that special but maybe my use-cases will create something that fills a niche.
There are also some really rough tessellation techniques in use to simulate ground snow walking in games out now, like that Assassins Creed with the native americans.
So live underground in air-tight domes, at least in the beginning before industry takes off.
To actually fix the cold, pressure and breath-ability? My bet is on either a heavily optimized artificially created vegetation that exploits Mar's soils enough to generate greenhouse gases, or, more realistically, shit loads of (or massive) machines doing that same thing. Here's to hoping 3D printing-esque evolutions in technology and automation permit this to happen within 150 years instead of 500.
I mean, shit, how is this any different from me jumping in and contributing to a Git repo the language of which I haven't mastered? Should I not lose respect when my PR's have syntax errors or use bad practices? Fuck that noise indeed.
To just open up the admin area and see what's going on, provided they're indeed full-permission admins. Then, to actually send input from said interface, that could make ssh'ing into the server something one need not do often beyond initially setting up the app.
Thanks for the idea. Assuming we're not running as root, and the admin side of things is secure, am I not considering any critical pitfalls of this approach? Also, any frameworky cmsy thingers that already do this? Is this new, am I a unique snowflake?
Works on all pages, just adds the pointer-hover: none to the body element. Using modified code from the article. Quite useful, really. I'm surprised at how often I subconsciously guide my cursor away from content while scrolling pages to prevent hover effects popping off.
I can anecdotally attest to my own strategy. I buy rubbing alcohol. Have a shower, clean the problem areas. Shortly after I get out I apply the alcohol to my arm pits, and if I think I'm going to really be sweating I spray some over my upper back, chest etc. Nothing close to the amount one would use if they were spraying deodorant. The result is that I can go several days without any bad odor, even when I sweat so much that my shirts are saturated, they don't even smell, to me or anyone else.
The side effect of doing this is that I am far more sensitive to perfumes and deodorants people use, and they just aren't at all pleasant in the quantities people feel they need to use to smell "nice".
Western countries have to worry far more about immigration than birth rate control.
It's pretty useless considering the fact that most of all frameworks already will work with the modern browsers, and thus why would anyone begin their selection based off of browser compatibility? I will say that knowing whether it's open source, and whether it's responsive-ready is nice.
At the very least a preview picture for each framework's common elements would make this kind site useful.
You feel the same feeling even when contributing to 4chan, however, you know it wont matter for long thus it's far less mental weight to deal with.
I see this kind of "shock" throughout the techy mainstreamy politcally correct communities. It seems to me that the people that take issue with bigotry are themselves somehow weak through some kind of insecurity manifesting itself as a desire to fix this perceived "injustice". Because, you know, muh feels.
4chan just doesn't care about your feels. It's funny to say this (see how I am distancing myself from 4chan to add validity to my argument?); but I do think more communities could learn something from 4chan in this aspect.
On a related note; I saw that outrage thread linking in the 4chan post about this black chick getting some dude fired and what not about a non-PC joke at a conference. Then, in the HN thread [1], to my pleasure, at least the top comments were mostly absent of the typical reddity/facebook etc. white knighting "This is why women arent in tech!" nonsense.
I think at the very least, have a message saying "This information was shared when you did X" so it's at least explicit.
Possibly just not at all; methinks the github crowd, unlike the facebook crowd, are sufficiently privacy sentient.
No server should take more than 100ms-500ms on a sufficiently cached page to process and to begin transferring, in non-edge cases. The only thing that could take that long is a shitty datacenter/vps, and as such, transfer speed/latency limits will encumber all types of requests.
In the end, you still have to transfer data from databases, so ignoring that, client-side template rendering seems like a non-issue to me. Surely it's never the latency issue unless you're serving at ~100+ requests per second, which translates to many millions of requests a day, and I don't believe 99% of websites are doing this.
I mean, if you're worried about cluster workers file reading being slower than a db connection, the json store could be write-only most of the time and only read on app startup while schedules are synced over cluster messaging.
Additionally you could just not update the addon ever if you're OK with it right now.