Would be really cool if they set some time aside for workshops, demos, or other interactive use of the space aside from just selling stuff. Without some serious guidance and help, many Pis just turn into an unusual way to play Minecraft.
If you are running multiple copies of postgres on a single node, then you have not significantly improved the resiliency of your database to failure, and it still does not solve the state transition problem. What happens when the primary database fails (or the node dies)? Whether it is on this node or another node, you need to have a replica (sync or async) that you can fail over to, preferably in an automated way. Docker swarm is not equipped to handle these transitions for you, at which point you are just running your database in Docker, with no real benefit over running it on actual hardware or a VM, and with significant added complexity.
Extensive and rather interesting discussion on variations of the theme "No plan survives contact with the enemy" can be found in military writings going back centuries. An overview is linked below.
While I have completely embraced running stateless services in Docker, I have been hesitant to migrate the database layer to containers. While I have not tested it personally, I have seen numerous reports of performance issues when using volumes. Is this no longer an issue, or was it limited to bind mounts? Do volumes not use the storage driver? Also, I have run into permission issues when using volumes with Docker, which I'm sure was just my own ignorance but it does seem like a cause for confusion and potential error. I have read through the documentation on the linked page, and the quickstart guides for KubeDB seems great for getting up and running, but I do worry about situations like if an automated PG database failover can't reconcile a timeline, there isn't much documentation on failover at all and this could add significant complexity to something that is already a potential nightmare. Anyone care to share their experiences running production databases in k8s?
It's sometimes hard for me to articulate to others why I read so much science-fiction, especially to those who see it as just another form of juvenile fantasy. Articles like this serve to illustrate that the writers who are carefully plotting out the future today may end up influencing the future of technology and culture more than they imagined. Clarke, Asimov, PKD, Gibson, they are all accepted as good writers, but I think some day a selection of such writers may be seen as visionaries who not only predicted much of what was to come but significantly influenced the course of that history. Personal computers were widely dismissed in the early days as impractical and unnecessary, yet I suspect it was those engineers who had been exposed to some of the possibilities science fiction writers were imagining for such devices that saw where they might end up. Once the idea of a globally connected network of computers became entrenched in enough people's minds, it was only a matter of time before the problems would be solved. TCP, DNS and HTTP were all important milestones in that path, but we could have converged on another set of protocols if things had been different. Good writers can lay out a vision of the potential in such a system in a way that private business and government usually can't, because they operate on a very different time horizon where they can look past the limitations of what's possible today and imagine what it might become.
Cleaning up the significant amount of plastic that is on the surface still seems like a step in the right direction, even if there is other micropastic further down. The impact on ocean life is not well understood, but we do know that plastic is already having a devastating impact on such life, and I have a hard time imagining this would be worse. The engineering challenges are significant, as they are clearly discovering, but they are at least trying. Are there other more promising projects to clean up existing plastic from the ocean you are aware of?
I hope they can figure it out, but it seems like they may have missed something significant in their simulations. If the water basically pools and becomes stagnant within the boundary of the catcher, then it makes sense that currents will route around the boundary and therefore carry plastic around it also. The long skirt seems like part of the problem, as it's trapping all the water in that area, but my knowledge of fluid ocean dynamics is nonexistant so perhaps I'm wrong. The idea of a passive system is nice, but it seems like the problem would be easier if they had some form of propulsion with a renewable energy source to drive it forward.
Oath is desperate to put more ads on Tumblr, because they massively overpaid for it ($1 billion) and have been throwing money at it ever since (100s of millions). I guess because of the way the content is displayed they can't just segregate nsfw stuff into a demonetized stream, but if they think they can turn Tumblr into a mainstream site that shows family-centric ads, they clearly don't understand what they bought.
There is an element of chance in getting into any top school, but only among the applicants who meet all the other qualifications. That is, between two students with 4.0 GPA, great SAT scores, and a wide selection of extracurricular activities and community service, it's a toss up. But a student with poor grades has no chance. It doesn't matter how many times the student with bad grades sends his application, he isn't getting in just by random chance. When it comes to Harvard, I would guess that 80-90% of applicants can be dropped immediately due to grades, SAT scores or lack of activities. Out of the remaining pool, for those without extenuating circumstances such as athleticism or family connections, is where such as race and "personality" might become a factor, and who ends up getting picked has an element of randomness.
The complaints have nothing to do with staying up to date or support. OracleJDK is no longer free for commercial use. OpenJDK has always been been free for whatever use (it's GPL, with exceptions). The danger is that a developer is already using OracleJDK, and upgrades or inadvertently uses OracleJDK (because it was installed by their package manager perhaps), and then Oracle shows up and claims they owe a bunch of money.
I like Nim, although I don't think it's great for everything and I do think it fills a particular niche. For me, that is a systems-programming language akin to Go or Rust with a familiar syntax. Coming primarily from Python, sometimes I need a language that is a) safe b) fast c) easily capable of producing a cross-platform executable. Nim provides all of these with a Pythonic syntax and style, and that is really the main reason I like it. It lacks the sponsorship and audience of the other two, but is still a well maintained language with an active community and all the core functionality you would likely expect. That being said, a few years ago I was a strong proponent of Nim, while today it is clear that Rust and Go have captured the mindshare and continue to grow momentum. In fact it becomes hard to recommend Nim when I think of where these 3 languages will likely be in 5 years.
They say the proposed version could store 20 megawatt-hours, but I wonder what the maximum output is? That is, how long does it take to produce that energy? If the maximum output is ~1-2 MW, it can support 1k or 2k homes, but it's also important to put in context that peak load of an average sized US city peak load is ~1000 MW. A med-sized wind turbine can produce ~2 MW, for comparison.
His "projects" page also lists "Log Structured File Systems" (which inspired LSM used by many databases) and Raft (the consensus protocol) as things he made significant contributions to.
This may be related to Bethesda transitioning to distributing its PC games directly via Bethesda.net and cutting out middlemen such as Steam. They want to capture the full price of a retail copy, and to do that they are cutting out resellers on all platforms to drive people towards their own new platform.
You might want to look into something like syncthing. It uses a distributed protocol like torrents but also supports updating files to new versions while only resyncing the diff and sharing folders. Open source, donation-funded.
I would imagine there is set of criteria which would absolutely trigger the fighters to bring down the plane, but those were not met, and those in charge erred on the side of caution. Bringing it down aggressively would not be without its own risks, as the aircraft and debris are still going to crash down somewhere. Additionally it means taking the life of a citizen, and causing a lot of damage that the National Guard is then somewhat responsible for, and potential PR backlash. I believe it was clear early on in this case that the guy was not a terrorist, and he didn't intend to hurt anyone, so adopting a "wait and see" approach seems quite smart.
Loss aversion specifically refers to "people's tendency to prefer avoiding losses to acquiring equivalent gains". It's not just the general idea that people are averse to losses, it's about how people value gains and losses differently.
A turning point was a fateful shuttle ride where I found myself sitting next to Eric Brewer, VP of Cloud, [...] Soon after, we got the green light from Urs.
This seems like a red flag for management at Google, if the best way to pitch ideas up the chain is hoping you can ambush someone important on the company shuttle.
This article was trying to make the claim that at many birthday parties in the US, all the childrens' parents will stay at the party. I don't know how common that is, but some cursory searching does indicate that it's a thing.
> Dep does not support using multiple major versions of a program in a single build. This alone is a complete showstopper. Go is meant for large-scale work, and in a large-scale program different parts will inevitably need different versions of some isolated dependency.
This seems to be a major sticking point but I'm having trouble understanding why. I'm not familiar with any other package management system which supports simultaneous major versions in a single project. If two things require different versions of a package, those seem like separate projects to me. Is this to support dependencies which rely on the same package at different versions? If so, why not just call it a version conflict and fail until it's resolved?
> These cloud hosting companies don't make this a natural evolution though, because there's no human to talk to
This is not true at all. Once you start spending real money on GCP or AWS, they will reach out to you. You will probably sign a support contract and have an account manager at that point. Or you might go with enterprise support where you have dedicated technical assets within the company that can help with case escalation, architecture review, billing optimization, etc.