Well, it says in the abstract (and they have further detailed calculations in the paper) that they achieved an average desalination rate of 1.76 kg/m^2/h. So that’s about 1 gallon of water in one hour with 2 m^2 panel. That said, they did their tests using a 9 cm^2 panel, so yields may change significantly on scale up. Not sure if that translates into meaningful cost savings at scale, but it does seem like a significant advance in solar desalination technology. It seems like the paper was focused mostly on salt harvesting, though, rather than desalination. So I expect the real utility to be the combination of the two rather than desalination by itself, if it scales.

That might be why a feature exists, or maybe even why a particular paid library was chosen instead of another. That doesn't explain why the code is written the way it was, which is the point of documentation. Why the feature exists is the realm of the PRD, not the design doc.

Of course if those aren't securities, then the entire site is illegal as it's operating as a securities exchange. That's their legal argument for why they aren't gambling sites, and shouldn't be regulated by state gaming commissions. So expect the full might of all those prediction market sites to be lining up against that argument and for finding him guilty.

> Disney's gotta nail the sweet, sweet merchandising.

Problem is that kids aren't generally buying Star Wars toys anymore, adults are, and they are increasingly detached from the new parts of the franchise.

Scalping isn't, and shouldn't be, illegal. You own the ticket, you should be able to do what you want with it, including reselling it.

And no, getting rid of scalpers wouldn't make ticket prices higher. Scalpers exist because the concert ticket prices are lower than what the market will actually bear. If a theater full of people are willing to pay 1K for a concert and they sell the ticket for 500, a scalper can make a profit via arbitrage. The only actual way to get rid of scalpers is to raise the prices to the sky (like 2-5x current prices) and slowly bring down prices over time until they're all sold. But my guess is you probably wouldn't like that any better, as the end price would likely be higher than the current scalpers price.

I download all my books DRM-free from bittorrent.

My ebook reader is an ancient Sony PRS-650, it still works fine and it has no trouble reading files that haven't been messed up by Amazon. What a concept eh?

"What about the book's authors who aren't getting paid when you download their stuff for free?" I hear you say:

Yes, I wish I could pay for what I downloaded. But I can't. The best option I could find was to buy the paperback as well, so some of my money would trickle back to them. But that's mighty stupid and totally not environmentally-friendly.

I did try to pay an author directly once (the late Ian M. Banks) but he send me an angry email back saying even if he got money from me, I was robbing his editor and distributor, and I should just buy his book normally - which I would, if that didn't entail leaving an undeserved cut to effing Amazon.

So there we are: there's no mechanism to legally buy books that aren't hamstrung by DRM. So honest people who value their consumer rights can't be honest.

I looked up the figures a few days ago - but having since driven to the other end of the country, I've forgotten the precise details. IIRC it was something like Goofy having a higher aphelion - so most of the time (and length of orbital arc) it is going to be further out than Pluto (by a few %, but it also has higher eccentricity, so it's aphelion is lower than Pluto's (and indeed, Neptune's ; which is also true for Pluto). Since orbiting objects travel faster at aphelion than perihelion, that makes the average orbital period of Pluto and Goofy the same (or their year the same, or their semi-major axis the same ; these all mean the same thing) despite Goofy travelling further per orbit than Pluto, with a faster arc near perihelion.

You see the same sort of thing with, say, Uranus, Neptune, and 1P/Halley ; Halley and Uranus have quite similar orbital periods, but Halley's aphelion is well out beyond Neptune's orbit. the long period it spends out there is counterbalanced by the 3 year long Sun-dive it does form (approximately) Saturn's orbit, to the Sun, and back out to Saturn's orbit.50-odd% of it's orbital path followed in about 5% of it's orbital period.

Just because Newton's laws are quite simple, doesn't mean that their consequences are simple. Just ask (if you can get his bones to talk) one J. Kepler, who had to work out the orbits from raw observational data, unsullied by Newton's theoretical framework.

(It still sometimes astonishes me that there is no simple way to calculate the length of an arc of an ellipse or it's total perimeter - you have to do a really complicated, progressive approximation calculation for each specific shape of ellipse. Which, when you realise that Kepler would have had to make hundreds (thousands?) of such approximations while reducing Brahe's data, explains why Kepler came up with at least one relatively good approximation to the length of an ellipse's perimeter.)

Wood burning is very much alive - both old-stylee polluting open-fires and stoves, and ultra-efficient pellet, wood-chip and wood dust burning in power stations. And it's renewable. Try visiting any nordic country some day...

Also, just because burning wood has downsides doesn't mean it has to be ditcheds it entirely. Solve the downsides instead...

hey combine hydrogen from with carbon dioxide,

Hydrogen from what or where?
If, like almost all *industrial* hydrogen, it comes from cracking natural gas, that's as something pure magenta (whatever the complimentary colour to green is).
(Our "analytical grade" hydrogen was probably sourced from electrolysis - certainly when we made it on site, it was ; but that was substantial cost of equipment and maintenance time. Our systems really cared about contaminants at the part-per-million level.)

It's dead, Jim.

It's not coming back.

No, it's more about how teams work. Teams have a scope. They don't typically go beyond that scope. So if my team owns the Foo and Bar modules, I work on those. But if there's little important work on Foo and Bar, but a lot of important work to be done on Baz, it's generally organizationally difficult for us to work on Baz. Typically we need to be lent out by our manager and seconded to the other team. Which can be a lot of red tape and politics.

Now if you're imagining some alternate world where programmers an be moved at will- then we're already one big team instead of multiple small teams.

And no, a smaller team doesn't win every time. If it did, then then smallest team possible is teams of 1 and we'd all do that. There are sweet spots, which depend on the organization, the work to be done, and the importance of that work. For some that's bigger, for some smaller. I've definitely worked on teams that were both too small for the work, and that were too big.

They can, under some circumstances. If the scope of what they work on is too small to fill the team's feature set. Or if the work they would be doing is significantly less important than other work to be done, having them in one large team makes it easier to move to more important work and can get critical features built faster. In that case it may not be overall more work done, but it may move the important stuff quicker. If larger teams weren't useful on some level, we wouldn't have teams at all- we'd all be individuals.

They're one of the 4 biggest stock brokers in the US. If you aren't trolling, you're showing yourself to be really ignorant.

In the end- good engineers with sufficient experience and support will get stuff working with any methodology. Bad ones or ones insufficiently supported will fail with any methodology.

There are some things that agile works well for, but it's really limited to domains where you can quickly build something tangible for feedback and you have stakeholders willing and able to give frequent feedback. UIs are a good example. It's a horrible fit for anything that requires actual research, or that can't be shown to low technical knowledge customers frequently (in other words anything that actually needs weeks or months of backend work, algorithm writing, or infrastructure to be written).

The problem with that is the skills needed to manage and the skills needed to do real work (let's take programming as an example) are pretty distinct. Someone can have both, but they tend to have one or the other. Forcing those without the skills to do the practical work into doing it doesn't actually help the team, it just slows everyone down. And if they get on the critical path of any project you can be royally fucked.

There are a couple of ways to solve this problem:

1)Larger team sizes. This can work if the team owns enough to keep everyone busy, but it can lead to effectively being independent subteams calling themselves one team while being inconvenienced by each other.

2)Each manager managing multiple independent teams. This can work if it doesn't overload the manager. The biggest problem is when the manager decides one team is more important and doesn't support the other(s) enough. This works better the closer the teams are, as it requires the manager to know fewer sets of collaborators and politics