cecilkorik

Vaporware turns out to be vapor. Shocking.

Took literally minutes for her to come back down to Earth. Oh wait, that was her rocket trip.

These magic beans will not only grow twice as fast, they'll also fix the last magic beans that didn't grow.

Of course he will. Soon the Myanmar Junta is going to be the first and only non-US operator of the domestic policing variants of the F-22 and B-21.

I don't really get why people try to block people from using the software when their problem is that they don't want to support it. Fix your support process if it's getting spammed by idiots. Block people there. Add a dropdown that makes you choose which OS you are using and tells the user that you won't support their distro if that's how you feel you need to gatekeep things.

It's not that I don't understand the frustration of dealing with idiotic support requests, or that I deny their right to stop packaging the software for a whole OS... but it always just feels so deeply misguided to me. Providing direct technical support is such a totally different thing from simply providing a best-effort attempt to build your software on a different OS or at least not getting in the way of people who do (by prohibiting anyone from building packages).

The logic behind these decisions escapes me, it's like moving to a different country and leaving everything behind because you went out in your shed and saw a spider in there, and then justifying it by saying you hate spiders and rarely used the shed anyway and it's just like... why? I get that you don't like spiders but lets be realistic it's not going to hurt you and if it really bothers you that much throw a bug bomb in there or something, it's a common and manageable problem whether you feel like it is or not, and you're not managing it in a remotely sensible way.

I mean, if there are in fact many "people who contributed" then they should have no trouble forking the project at this point and continuing open source development of it. Their code and everything they contributed to is still open source. Nothing is being held hostage, no one is obligated to use the new proprietary closed-source version and the license they contributed under the terms of implies that it doesn't bother them that somebody else is using their contributions for their own internal purposes to create a proprietary version of it. That's explicitly allowed by the kinds of licenses they were using.

If there aren't many people who contributed then the problem is not the licenses, it's the fact that we depend way too much on people and companies donating development and maintenance effort to keep these projects afloat. The problem with donations is that they're not mandatory and if you try to make them mandatory then they're not a donation anymore. If it's no longer in the company's interest or economically justifiable to keep donating effort to the project then they won't. If the project can't survive that, then the license isn't the problem.

Those who do not learn from history are doomed to repeat it, that's why everybody needs to start fucking listening to what the historians are telling you all.

We should be so lucky...

The comment I was replying to is basically just asking "why should they care [that they're not native to this land]?"

So - if it cools the place from, say, 29 degrees outside to 22 degrees inside, that’s the same as warming it from 15 degrees outside to 22 inside?

Oh my, not at all. If it runs for 1 hour continuously in cooling mode that's going to be electrically largely equivalent to running for 1 hour continuously in heating mode (again, provided it's not variable speed). Even then the electrical load will vary slightly according to various conditions. The actual temperatures achieved though, depend entirely on the thermodynamics of the system (both inside the pump itself and your whole house and the environment it's in) which are extremely dynamic and complicated. There are almost no simple, linear relationships you can use to approximate what is actually going on. Even the approximate calculations that HVAC installers do called "Manual J" are hugely idealized and oversimplified. You've got things going on like solar heat gain through windows, heat losses through insulation, and heat transfer through gaps in the insulation, air losses through vents and doors and windows and gaps that are specific to your individual home and that you can't even really measure accurately. It's a very difficult thing to even attempt to compute or simulate no matter how much we try to develop models that accurately estimate things. On a larger scale, this is why we still struggle to accurately predict the weather.

Only the next bill will tell

That's a reasonable position. You can make all the estimates you want but at the end of the day the only thing that really matters is what you get billed for and that will tell you the truth about what's actually happening in your house, environment, climate, and situation. I would be confident that given the same temperature conditions you really won't see much practical difference in electrical usage between a heat pump in cooling mode and an air conditioner (if anything they tend to be somewhat more efficient just due to better design and higher build quality). But you won't know the true situation until all the measurements are actually done and posted to your bill, and even then you won't be able to directly compare them because there are so many other variables that are always changing.

The name of the group is "return to the land" they should therefore be hopping on the first flight back to Europe if they're planning on returning to their land. This land isn't theirs to return to.

I've literally never felt like I needed a file server to be easier and support more protocols, and this seems like it's trying to do way too much at once. HTTP is beautiful and convenient but as a bespoke javascript-heavy API it's really not a particularly great way to manage files, FTP sucks and if you still need it for something you need to re-evaluate your life choices, TFTP is useful in extremely niche applications that I wouldn't want to hook my entire file server up to anyway and certainly don't want running along side these other options, WebDav is fine but again really only necessary in niche applications which you don't need or want your entire file system hooked up to (or if you don't know how to VPN) and this doesn't seem to support SFTP/SSHFS which is what I would consider a modern standard for a secure file transfer protocol.

Just use Samba and/or ssh, every Linux distribution comes with packages for them. Both are widely used and battle-hardened, and between the two they are compatible with almost everything. You don't really need all that other stuff.

In some ways it’s the inverse of the UNIX Philosophy: instead of doing one thing perfectly, this program is doing everything [9001] could think of, and doing it “good enough”.

As a believer in the UNIX philosophy (armed with an understanding of why it is fundamentally useful) it horrifies me that either developers or users think this is a good thing.