Rooftop actually has a few advantages that counter act its increased cost vs farms:
- Because the panels are geographically distributed it has less variance. A cloud can pass over a solar farm and you get one huge megawatt swing but when distributed it is much more predictable. If it is 50% cloudy you will get 50% generation continuously. This means grid operators can reliably bring cheaper larger sources with slower ramp rates online that day like nuclear instead of gas turbines. These also reduces the need for energy storage.
- Because the panels are closer to consumers there are less transmission losses and decreased capital cost in terms of energy transmission. Although distribution lines may need to be upgrade to compensate.
Also, the Dart lang team seems to consider Flutter a first class citizen and has been modifing the language for it specifically. From syntactical sugar for Flutter's constructors to carefully selecting language features considering muilti-target platform performance.
It really is the project to beat. I am not sure how you are gonna drop a framework over C# and compete with a framework/lang combo long term.
"Play-distributed apps must use Google Play's billing system as the method of payment if they require or accept payment for access to features or services, including any app functionality, digital content or goods"
I think this is an algorithm mistake on Google's part. Their policy is clear that this scenario is okay. I wonder how they will respond?
On a tangent, if I were to release a paid app to third-party stores. I would have a base price then add the third-party fees on top.
A gripe would be that I don't see these stores allowing for a clear break down of fees. So I can't educate my users. And if a user is unaware of the added fees they can't take it into account on their next phone purchase.
Beyond that, given that there are only two choices seems to imply high barriers of entry into the phone OS game. And that does imply free market issues. But nothing a bit of waiting might not fix?
Well given the state of desktop market which has been around for decades there may be room for intervention, haha. Like grants/tax incentives for consumer apps selling on open source operating systems... idk
Be aware that you are legally bound by any public statements you make about your products, especially through advertisements or on labels.
If you are a retailer, your customers can ask for redress under the legal guarantee provided by EU law - if an item:
- doesn't match the product description
- has different qualities from the model advertised or shown to the client
- is not fit for purpose - either its standard purpose or a specific purpose ordered by the customer which you accepted
- doesn't show the quality and performance normal in products of the same type
- wasn't installed correctly - either by you, or by the customer, due to shortcomings in the instructions
IF YOU INFORM your customer that the product you are going to sell has quality problems, they cannot then claim redress from you about this particular defect."<<<<<<<<<<<<<<<<<<<<<
You are right and you are wrong. They must provide a 2 year warranty on the functionality of a "Beta Edition Linux SmartPhone" with the following disclaimer "Beta Limited Edition PinePhones are aimed solely at early adopters. More specifically, only intend for these units to find their way into the hands of users with extensive Linux experience". A beta is not expected to function correctly. Hence, there is no justification for return under eu law. People writing these laws aren't idiots.
Additionally, that warranty state works well in other jurisdictions and is fine.
I like the vector. Looking forward to the progress. I think your solution space will give you other opportunities down the road even if sellff struggles.
Interesting! There are some farmhouse brewers in Norway, Lithuania, and a few other places that use mashing processes that aren’t temp controlled two step processes. However, mixing cold and hot mashed wort is a pretty neat technique.
Looking at the photo, there is a lot of protein haze and sediment, which I would expect given the lack of boil, and consumption from the fermentation vessel.
Now I wonder how they were processing the grains prior to brewing.
They don't. I believe using this setting it is a good way to prevent tracking by pixel.
In addition, I think enforcing plain text emails would disable any client side tracking events.
EDIT: Well it looks like that setting in Thundebird prevents any remote connections. Not just pixels, so that be good enough. However emails often have a text back up that is going to be better formatted then a hampered html email.
EDIT: To prefer plain text in Thunderbird it is View -> Message Body As -> Plain Text
You can use standalone rootless buildkit building locally/natively and in cluster/container. You can use buildkit through docker too but docker is packing a runtime so standalone buildkit in cluster/container.
- Because the panels are geographically distributed it has less variance. A cloud can pass over a solar farm and you get one huge megawatt swing but when distributed it is much more predictable. If it is 50% cloudy you will get 50% generation continuously. This means grid operators can reliably bring cheaper larger sources with slower ramp rates online that day like nuclear instead of gas turbines. These also reduces the need for energy storage.
- Because the panels are closer to consumers there are less transmission losses and decreased capital cost in terms of energy transmission. Although distribution lines may need to be upgrade to compensate.