mioelnir

I have to admit that when I saw the dark bar for the first time, I switched to HN to see if someone died.

Also, speaking with my sysadmin hat here, Zookeeper is an insanely powerful introspection point for running distributed services. The number of services with internal cluster coordination protocols that offer similar capabilities is abysmal.

I use the json field to store precomputed/-assembled write-once-read-many json documents. For that I find it incredibly useful, as the JSON functions allow me to drill into the generated JSON for analysis and diagnostics.

I agree. These problems only exist for pay-per-impression and targeted ad models, and the return of dumb ads is a solution to this. I should have made that clearer.

Yes and no. It won't help in the sense that the query planner can not identify the affected partitions. But it can help if the database supports parallel index scans, since instead of one big index, it has to scan n smaller indexes which can be done concurrently.

The design for ITER was finalized in 2001, amended in 2007. Construction for W7-X started 2003. W7-X is now built, fully functional and operational. At several points during its construction, the construction process for its required parts had to be invented first.

That's 15+ years of research, breakthroughs and inventions in plasma confinement physics and engineering that have had to happen first.

As a noncommercial research reactor, W7-X will continue to be useful for many years to come. For material testing alone I would imagine access to reactor capable of producing a stable, continuous fusion reaction is invaluable.

The ARC is a design proposal from 2015. As such they have access and can utilize all the achievements, results and processes from W7-X, ITER and other material science advances of the last 15 years. If their proposal was not better than already built specimens, it would be a bad proposal. To declare it a race against the research foundation they built upon seems ignorant at best.

In 10-20 years, when the ARC is built, a new design proposal will emerge, based on even newer advances in material science and the lessons learned from building the ARC. And it again will be better than the then current, assembled reactors. That is how it is supposed to be.

To serve the ads under the 1st party domain - without ending up in a situation where the entity reporting the number of ad impressions and the entity receiving money based on that number of ad impressions are the same - is often significant effort.

First, if your query used the partition key in its where clause, the database knows(can calculate) which partitions can have a result and which can not. This means smaller indexes/less data to scan to find the result.

In the MSSQL case - not sure about others, this is were I had to use it - you can also switch data segments between tables indexed over the same partition function and with the same DDL. So you recreate the existing table a second time, create all the required indexes on it (which is fast because the table is empty), and then you switch partitions between them basically via pointer manipulation. The empty partition is now in the normal table, the data partition in the recreated one. Then you drop table on the recreated table. This is much more IO efficient than a delete-from statement.

This switching of course allows for a lot of other fun stuff as well, where you switch out a partition with a couple million rows, then work on it in isolation, switch the partitions back and then only have to "replay" the few rows that hit that partition while they were switched. Which is easy because they are now in the shadow table which is not updated further.

It is of course data and application dependent if you can use these things without affecting your application; but if it is suitable, the gains can be immense.

Happens frequently to me with uMatrix. Then you look at the list. You know the usual suspects like jQuery, google ajax, bootstrap, Akamai etc. fairly fast.

On other sites you look at what they want to include and you just think "yeah, no, let's not do that" and just close the page.

Agreed, for a number of students the promise to explain it later will suffice. Others - when given magic boilerplate that does strange, intended things - will recognize it for the black magic it is and will want to wield it as well.

They will dissect, examine and research it on their own and their learning will be much deeper.

Does pledge(2) still enable its simple programming interface by allowing certain default actions based on a filesystem hierarchy layout, statically defined in the kernel/libc/somewhere? The first presented versions of tame(2) had this iirc.

> ... but "Open Source" is pretty much retconned to be defined by the OSI definition of the term

"Open source" as a term or development methodology is older than both the OSI definition and the Debian manual it is based on.

Most places where you have to pay, you usually have to pay up front. The yelling guy might just have called you names for being cheap, I certainly wouldn't expect toilets at a bar to have a mandatory fee.

Another scheme is usually found at Autobahn rest stops, where you actually have to pay for toilets, but get a voucher over the full amount that you can then use in their shops.

In Germany it is not entirely 1:1. If you receive Hartz4 unemployment (€404) and have a so called €450-minijob (which is the cutoff for social security taxes etc), then €170 are additional income and €280 are offset with you unemployment, giving you €574 overall.

At least that's how I understood the mechanics just now, having never been forced to actually understand them.

First of all, if a pharma company had an annual income of 2bn from HIV treatments, and that companies CEO went forward with a HIV cure that is only predicted to earch 3bn overall; that CEO could essentially be removed from his position, as that would not be in the best interest of the company and shareholders.

Also, there does not need to be an evil twist where someone deliberately holds back a developed cure. It is much easier to cut/steer the research in ways that favor treatment/management options, ensuring that a cure would only be found be accident.

If you disagree with a license then do not accept it, do not use the software, do not use the product.

Talking so high about freedom and rights, and then calling other people's rights trivial when they do not fit in your echo chamber of righteousness.

This does not matter one bit. Bitkeeper offered the use of a product under a condition, in other words, a license. And it offered the product for free, expecting the license to be honoured. Every open source developer should respect and uphold that agreement, once entered by both sides.

Your personal opinion of the license terms is irrelevant. You respect other people's license, because you want them to follow yours. If developers can not grasp that, how do we expect users to?

18 disk zpool with three raidz2 vdevs, with 2 disks from 3 different vendors per vdev, bought in two batches per vendor and evenly spread across the case. That's about as paranoid as I consider practical for the homelab/online part of my storage needs.

Also, not sure there are three pieces of storage software that I trust and are readily available to me.

Where I work the really big lists are all moderated, with only 3-5 people allowed to post to the list. If you need to post something there, you mail one of the moderators the text you want sent on the list, together with an explanation what it is about and why you can't target a smaller number of recipients.

Email got a lot more boring since this was introduced.

Just two paragraphs in the article says that they expect at least every 4th car to be electric by 2025, and that this of course means different supply requirements which they have to start planning for now. That's just regular market forecast planning.

You have very, very obviously never been inside a german car factory.

VW should found a utility company for water and electricity and be awarded the contract for american occupation force bases. Then they do not have to get bailed out, but can charge it right back.

> Women working in tech sales are offered roles with a median salary of 5% less than their male counterparts.

As a non-native speaker, this makes it sounds like they compare different roles.

My favorite XFS workflow:

1. filesystem is corrupted, once again

2. try to repair it

3. oh right, the repair tool can not replay the journal

4. try to mount it

5. admit after 3 hours of nothing that the journal-replay code triggered on mount actually can really not deal with corruption

6. reboot the server to get the filesystem unstuck

7. rerun repair, this time throwing away the journal

8. look at the empty filesystem with everything in lost+found

9. restore from backup

The team I'm in only runs 1'400 servers, yet this happens regularly.

But also be aware, that the traffic Netflix serves out of those containers is way less then 0.01% of the internet traffic in North America. The container cloud is their management engine.

The CDN that is actually pushing the traffic runs FreeBSD and would be using, if anything, jails.

I'm always tempted to classify the internet as a test network in our firewall documentation, because that can't be the production version.

Personally, I think if there was a birth control option for men that was even remotely in the same ballpark as the pill in terms of effectiveness, reversibility and pre-plannability it would easily equal or surpass the pill's usage rate.

> The last thing the world needs is another immature SSL/TLS implementation...

No, they world needs as many of those as it can get (if they are tagged as such). And then all the authors need to discuss with each other what they learned from the implementation. And then they compare their code with existing code bases and discuss differences. They review their patches, as well as patches from other projects.

They discuss the diffs, learn from others and bring in new ways too look at things.

All bugs are shallow given enough eyes, and yet one of our biggest mantra's sole purpose is to limit the number of eyes. We need people that are familiar with crypto codebases and its subtleties, because we need the reviewers for our established projects. And for this reason, we need people to write and publish crypto related code. Not so we can push another new, excitingly half-baked TLS stacks into a product, but to foster the code review process we all rely on.

I think there was at least one type out there that detected dropbox, encrypted those as well and deleted shadow copies.

One option gives an immediate, personally beneficial effect - "you get your files back".

The other option gives you an immediate, personal loss - "your files are gone" - together with an all but unobservable, mid- to longterm benefit for society.

You can of course hope for the majority to take the second option, but hope is the first step on the path to disappointment.