Plastic fermenters are MUCH safer (I am one of the many who have gotten minor cuts from shattering glass carboys) but just plain terrible for fermenting in. A little scratch in the wall and your sanitizing process will miss the wild yeast that grows in the scratch making the container essentially useless for fermenting with your chosen yeast only.
Also they make widemouth glass carboys which are very easy to clean. But they shatter all the same.
If your going to avoid glass go 304 stainless (SSBrewtechs BrewBucket etc.) plus it basically lasts forever.
Outside of UI components which MSFT is getting to, they’ve worked very hard to make the transition as easy as possible.
If anything, the backwards compatibility has led to making some things worse, IMO, e.g. switching from the simple JSON based project file format they had to the XML based .csproj style one, which I’m pretty sure was done to be able to support .Net framework projects.
Classical .NET Framework CMS like Sitecore are now API first, and migrating away from .NET into a mixture of .NET, Java and JavaScript offerings.
Back in .NET Core 2.1 days, I had a two months project to port an application from .NET Framework into Java and deployed into Red-Hat Linux, because if a rewrite was required, then better away from Microsoft ecosystem, as this specific company already had enough from rewrites.
This is how well some customers have been taking the .NET Framework => Core migration.
What are you specifically referring to? .NET core has pretty much everything and more than .NET Framework did.
In my personal experience, and that of colleagues, it was a pretty smooth experience. We mostly had issues due to some API changes here and there, and of course ASP.NET
Outside of WCF it's not that different. I agree that the removal of WCF feels like a huge gut punch, but if you were following WCF tenets all along and had nice separation of your Data and Service and Operation Contracts it really shouldn't be that hard to drop all your WCF Binding wizardry and write new implementations of your contracts (interfaces) against HTTP REST or gRPC or GraphQL or Raw UDP Sockets or whatever your heart desires as your next communication tool, then dependency inject those implementations like any other dependency injection.
The point I was making was that WCF done well is a lot fewer billable hours to rewrite to use anything but WCF than people often think it is. I've done those rewrites before, and WCF is one of the few frameworks in existence that went so far out of its way to try to not leak abstractions that unless you were dependent on some truly baroque bindings, it's easier than most people seem to think. I've heard a lot of projects avoiding the .NET Framework to .NET 5+ transition solely because of WCF and how much work they think it would be based almost more on sunk "debts" feelings of existing tech debt from debugging WCF bindings/magic rather than maybe seeing it for what it is as more of a "unit testing DI exercise" where you've got existing test mocks (WCF) and just need a clean new implementation of existing interfaces.
Sure, but someone has to pay for that work, and many places don't have developers in-house, which means someone has to feel motivated enough to do a request to finance.
They fly in helicopters and can shoot that many in a day. Its usually very large areas (thousands of acres) with a surrounding game fence. Since the hogs have no natural predators they have to be removed somehow and this is one common route. Vastly different scenario then a small 50 acre place.
Any brewery can get you dextrose much cheaper than $2/lb. I think we are paying around $0.55/pound or something close to that in my area (Texas) for a 50lb bag.
Note this is a shortage currently on dextrose because of all the hard seltzers appearing in the market so quickly and using it all up, so it will probably go up as these keep growing.
I added a small cafe in Aug last year to my existing brewery's taproom because food was required by the state to reopen. I had no prior experience in running a small cafe (we do mostly paninis and similar). My thoughts roughly a year later is that food is one terrible business. We are close to braking even over that time, minus buildout. We have a wonderful staff and have been blessed with no issues in that department. But other problems are always popping up. Such as pork prices have doubled in the last 3 months. Bread went up about 15% and lots of other things change a lot order to order. We can't change our menu every week, so some weeks a sandwich is perfectly priced, while the next its food cost is 40%. Basically there are just so many moving parts, that change so frequently, so much inventory that expires in just a few days (vegs). So little max potential profit. It's usually a goal of 25-30% food cost, 30% labor cost, 40% to overhead and hopefully of that 10-15% profit (Assuming you didn't piss away 20-30% to a delivery service). I have found that being such a small operation we have yet to really hit the 30/30(60%) its more like a 65-80% in ingredients and labor. Which vary wildly from week to week as customer traffic varies. If sales were to triple overnight we could more easily get it lower and into range of the 30/30 or possibly even 25/25. Just because there would be less wasted food, less wasted staff potential, and more room for improvements. Which brings me to the point of this long paragraph. It seems (from my limited experience) like a restaurant that can't get enough sales for its appropriate overhead size, struggles. I am fortunate enough that we make enough coin to live on the rest of the business and don't need the income from the cafe, but it sure is a lot of work for very little reward that I would never want to mindfully walk into.
There is nothing that can grow during fermentation in beer or wine that will hurt you. It will just taste terrible, or unplanned.
In lower abv fermentation such as kombucha or fermented vegetables. Molds can be a risk if the starting medium is not low enough ph, or high enough salinity.
Something like aspergillus flavus could poison you, although you'd notice that because it would be clearly visible as a green mould with a terrible smell & taste. I homebrew myself and agree that poisoning from ordinary brewing (not distillation) is incredibly unlikely.
This is not at all common in beer brewing. I cannot speak for the wine world but most of them have variable height lids.
No brewery would ever put glass marbles into a primary fermenter. As a professional brewer we routinely try to have the beer touch as few items as possible, post chill, due to sanitation risks. Not only would marbles be a nightmare to sanitize (tiny chips or cracks would not be properly sanitized), its a logistical nightmare to later get them out to clean the tank. Tanks are cleaned in place with a pump and spray ball method without ever opening the tank. Getting excessive hops out is enough work much less marbles.
Breweries purge any air out of a tank with Co2 before filling, for multiple reasons, but since Co2 is heavier than air it will settle on top of the unfermented wort as it is gently transferred into the fermentation tank thus removing the need for any kind of marbles or headspace reduction.
A second major reason this would not be done is that when beer ferments it needs extra headspace as the yeast in an ale ferments on top of the beer. A hefeweizen will routinely create a yeast layer about 10-15% of the height on top of the liquid. So if this space was blocked it would be forced out the top, which for most modern breweries would create a large mess into the floor drains and lead to the yeast count being too low reuse.
On the flip side I would be very interested to know of a brewery doing this and why.
- And maximum age of US public officials (especially presidents) set to a similar limit.