There's a lot of blame to go around. The prisons share a whole lot of it.
152 karma · joined October 28, 2012
There's a lot of blame to go around. The prisons share a whole lot of it.
What're your "killer features" that are lacking for ACL in Node in your experience?
I'm becoming severely intrigued by the idea of using specialized proxy servers for applications like this…
What interests me a lot at the moment are HTTP proxies that provide features like these. I like the encapsulation and scalability that true REST makes easy.
I would say writing the "expose DB as REST-API" can be easy for small projects, but a lot of work can go into making something that is RESTful, scalable, and a joy to build with.
Putting that conversation aside, I'd be very interested to know what advantages there are for you in having ACL built-in vs. using one of the ACL middleware modules that are available through npm.
William Riley-Land (Author of baucis)
Applesoft BASIC (Apple ][e) -> Level I BASIC on TRS-80 -> FutureBASIC (Mac 68k)
Those are the BASICs I learned before moving on to Java, C#, then JavaScript.
FutureBASIC was really ahead of its time. You could drop into assembly, make direct system calls, didn't need line numbers, it supported proper functions, and it was event-based and somewhat asynchronous. For ~$300 it was a pretty big deal for Mac users at the time. I think MPW was still several thousand dollars and open source compilers were largely unavailable.
"You don't need a weatherman to know which way the wind blows."
Who would blame anyone for choosing food over starvation? But GMO is not a solution for the world, and it is not a sustainable solution for fixing poverty.
I aim this generally: it's a bit rich for the so-called developed world to destroy sustainable indigenous populations and then "solve" the problem with intensive agriculture. All under the banner of "isn't science great," "what could possibly go wrong," and "cheaper feed for livestock."
I doubt it's a popular opinion, but there I said it!
The JavaScript world should be learning from the mistakes of monolithic and semi-monolithic frameworks such as ASP.NET and SEAM not trying to recreate them.
For my part I'd like to see separate libraries for events, views, models, syncing models to persistent storage, and binding models to forms. Small micro-libraries allow maximum flexibility and efficiency, and facilitate more maintainable code.
The way that Angular violates separation of concerns between presentation and view is another symptom of a monolithic approach, and a step backwards in HTML client software design.
People who are more conscious of the hyperbole often prefer the term "minimally processed."
† There are legal requirements for what percent of a meat needs to be present to be a considered meat, thus we get things like "beefy tacos" which contain a meat-like product with so much filler they do not meet the already low standards of what the USDA considers to be meat.
I am the author of an open source module called Baucis https://github.com/wprl/baucis
I personally perform software development and coding using Node.js, MongoDB, and Backbone.
I bring 10+ years of professional software development experience to the table, as well as about 3 years of experience with Mongo and Node.
I'm also looking to work with an assistant developer for various project management and systems admin tasks.
Please visit http://kunio.acuityscheduling.com or email me at william@kun.io if you would like to talk about a project or collaboration.