379 karma · joined October 10, 2014
Root-ready by the mfg, running Cyanogen from day 1.
FreeNAS ui makes this super simple from that end, and, despite being pitifully out of date, the ReadyNAS supports rsync to the extent that I need.
From the repo: "FAP stands for FPGA Assisted Processor, inspired by Steve Ciarcia's 1981 book Build Your Own Z80 Computer, in which he called his computer ZAP, short for Z80 Application Processor."
At least in this thread, people seem to be giving FB the benefit of the doubt on that particular anti-pattern.
Can anyone rule out plaintext storage?
http://lhorie.github.io/todomvc-perf-comparison/todomvc-benc...
It's not a fantastic UX but it works and it's fast to develop.
The docs are sparse but for my money the format is relatively intuitive. I'd prefer to be using XML/XSL/XSLT as they are FAR more powerful, but that's just what you get with JSON.
Having unfavorable terms, as you've described, makes the bitter pill of devaluation look a little sweeter.
But in response to your question, I'm not sure how it's not free market. Can you describe specifically what doesn't get covered from the "it's not forced lending" argument?
The post I was responding to was advocating apparently limitless free speech, though. Chilling effects SHOULD apply to certain things, and unapproved pornography of yourself maybe should be one of those?
Limitless speech but limited recourse isn't worth advocating, IMO.
Am I grossly misunderstanding this case?
Oh, and if you are genuinely interested in trying K2 before buying, I'll be they'd set up a VM for you to remote into. They did for me in '10.
I am confident, having scoped many a project, that often the case is the stakeholder not quite knowing what they want. A good UI then is a good step forward to allowing the stakeholder to iterate on refining their interpretation of their own problem.
interface IFooAble { ... }
interface IBarAble : IFooAble { ... }
static class FooProcessor {
static T ProcessFoo<T>(T fooInst)
where T: IFooAble { ... }
}This gives us something that as long as the object implements IFooAble, we can use this extension for free. I.E: IBarAble can use ProcessFoo just fine. This works really well for writing fluent interfaces as demoed above.