And since "exit" has come to mean 50%+ chance that customers will be screwed over it also means that in the future having a decentralized product will be KEY to actually get investor money - there's only so many times this get-customers-screw-customers round-about can spin before it gets uninteresting from a capital gain standpoint.
"But for sure, I'll never reach the official 5.7 l/km with my car ..." --> are you driving a Russian tank? I drive a 10 year old not particularly efficient Vauxhall (UK) and it is doing ~17 km/l!
Would be really interesting if one could program a secure way for the individually hosted servers to hook up with each other and verify the correctness of one another while at the same time keeping the messages secure (I guess bitcoins come to mind here..). Up until something like this happens I guess centralized social networks are going to rule the roost since the value of networks is almost always in their reach/size.
Yup, now we all have to download and run extension "Disable Pocket" in order to not have third party commercial services embedded directly into freshly downloaded Firefox. Its soon time for me to give the Palemoon distribution another go, at least its maintainer seem principled.
I wonder what it would take to create/put-together a minimal window manager and stripped down version of Linux wired to run Windows software as its default mode or purpose. Would it rival ReactOS or is Wine simply too unstable to truly serve as a "whole" OS?
What speed stats would people be getting with this..? The idea of Node managing a hypervisor linux VM somehow seems unrealistic in performance terms - but I might be hugely prejudiced on this so who knows.
Interesting, I'm also servicing an ailing CentOS 5 server; un-upgradeable and a pain: currently having to migrate the core application onto a new server, haven't had issues with Ubuntu LTS for server usage in the past so that's what I'm going for but the discussion here makes me want to go with Debian instead next time!
I don't have the C skills necessary but I would love to see ReactOS reach mature (-enough) state for work use soon: the new, privacy invading, direction that MS are taking their OS in with Win10 is unacceptable to me and yet my productivity on Windows in general is so much higher than Linux/OSX (probably just habit to be honest, I'll soon enough find out unless MS comes out with different approach to privacy defaults)
Good effort for sure but I'm still really sketched out by the sheer amount of monitoring crapware on Windows 10: what stops MS from re-enabling all of this stuff?
After all you and I will need to leave auto-updating on default in order for the OS to stay safe in Internet context. Which effectually means that MS can enable/replace all of these services at any given time. I get that trusting closed source code is always iffy but trusting closed source software that -intentionally- sets out to monitor and document your every move seems a less than optimal path to walk. Will stay on Windows 7 for now and if no better offering comes along from MS I will move to a Linux solution (or even OSX if my privacy stands a better chance of being protected than on Windows). Sad in a way cause I'm fundamentally fine with Windows from a work perspective, it gets stuff done for me.
The buzztalk is strong with them: "The V3 Optimized Desktop Allocation (ODA) technology is the first and only technology that allows for hyper-converged appliances to be delivered in a distributed fashion."
Sometimes I wonder about the strength of this sort of sales behaviour but ultimately I guess they make their own ecosystem by requiring specialized techies to translate even the sales pitch - promoting a sort of "it has got to be super-hyper-vigilantly efficient if I can't even understand what its good for, plus I can wash my hands of it professionally if it fails because anyone in their right mind can see the necessity of having someone else evaluate the usefulness of a system this incomprehensible"-response from certain managers.
Yes, that's what my sense is: it would, within its very limited domain, beat nginx and co. fairly easily.. its interesting because this sort of thing could be made to be modular and thus feature extendable without the overhead if done in a smart enough fashion - many webservices today are sufficiently specialized that they only use a fraction of the features that modern webservers include.
That is good stuff but no: what I am after is blog posts that are editorially aimed at drawing the reader into the subject and then making something of practical/genuine value happen. There is many tutorials presented on OpenCV's page and I'm by no means judging all of them but many of them do seem to fall into 2 discreet categories, either a) extremely simple ( http://docs.opencv.org/doc/tutorials/introduction/load_save_... ) or b) extremely complex ( http://docs.opencv.org/doc/tutorials/ml/non_linear_svms/non_... ). Neither is very exciting/accommodating for someone starting out in the field.
"Bring patience, though.", and that's the exact thing; when starting out with a new framework/technology/etc. I really need test examples that are digestible to get me going - the machine learning part of the tutorials: http://docs.opencv.org/doc/tutorials/ml/table_of_content_ml/... is no doubt brilliant but it is utterly inaccessible to me without serious time input.
These complex sort of projects are the ones that could really do with small neat introductionary blog posts where simple features are demoed with code demonstrations..etc. this is so much more needed than more ruminations on JS libraries but also so much harder work for the blog authors I guess!
OK, but what exactly does this achieve? Bad to worse touch sensitivity on my sleeves? Why? I wish they could have come up with at least one genuine show-stopper application to get people excited about this tech. Reading through this thread the only semi-reasonable application is surreptitious counting of cards.. and even that is useless as cleanly pointed out by the most upvoted comment-on-comment by downandout.
I do not like how the article easily dismisses the point that this guys wife became a centenarian with "Good genes, perhaps, but probably not her husband’s exercises, which she was said to have shunned."
> the persistent storage layer into mesos is still being baked
That's pretty important point, would have thought persistent storage would have been first point to get working for a project like Mesos. Also, their homepage ( http://mesos.apache.org/ ) outright states: "Apache Mesos abstracts CPU, memory, storage, and other compute resources away from machines [...]". What storage are they talking about if not persistent storage?
I'm tired of these "javascript is dangerous" for rendering sites articles (sorry if this is not one, I can't load it at the moment!) - instead there should be one big ass article saying: "javascript is fine for incremental rendering of features, the url should always reflect these increments and hence hard-reloads should be able to pull a fully server side rendered version of the site". END OF STORY.
This is why http://redecentralize.org/ and other similar efforts are so important - the centralized model is functionally unfit for long term usage or relying upon. How to capitalize these newer decentralized technologies are key for next leap in the web industry.
Its still 96KB in base CSS format.. hardly "small" by any standard. Never tried it but at least Min ( http://mincss.com ) is proper small: 995 bytes to be exact, or 96 times smaller than SkyBlue if you will (which I'm sure is in another league feature wise, but I digress).
Look up the history of the Greens in Germany they went from insignificant nth contender in the 1980s to ruling party - simply by slowly gathered the votes of discontent from people fed up with the two main parties. Not voting is not a strategy; should be mandatory in my opinion.
It certainly would be possible, take a look at what is done with canvas out there! But it would be a LOT of work to get the rendering right, most guys who implement "fast" text editors these days are not super intelligent hyper programmers but simply people who prefer to embed native OS text rendering views instead of inventing 10x odd gui junk on top of them.
This is such a fundamentally good idea to implement, thanks to Aaron for taking the time with this - a universal copy/paste is like having access to manual pipes for the GUI, priceless!