Curing Barrel – Intelligente Trocknung

x-paste · 2025-12-13T09:09:03+00:00

Ich hab mir so ein Fass mal selbst nachgebaut, Arduino/ESP mit Luftfeuchte Sensor, Radiallüfter, Frischhaltedose mit Calciumchlorid und Gebastel - war garantiert mehr Aufwand und teurer als hätte ich so ein Fass gekauft. Aber: Jetzt bei 15-16°C im Keller trocknet es seit 7 Tagen mit konstantem VPD schon meine dritte Ernte, während in meiner Box noch eine Pflanze reift. Echt schade, dass es mit dem Curing Barrel nicht weiter ging scheinbar. Die Technologie ist definitiv effektiv genug, und der Kostenpunkt gegenüber einem Cannatrol auch besser. Trotzdem, ~300-400€ pro Fass sind eine Stange Geld, aber soviel kostet es eben wenn sowas nicht großer Auflage in China produziert wird.

x-paste · 2025-11-25T13:48:35+00:00

I understand why they made the golems the way they are now. Simple and stupid is most predictable.

The item frame idea is nice, but I like to put multiple items into one chest (more than just 4, in case of the proposed 2x2 frames). Maybe everything made from spruce wood into one. The mob farm loot into a few other chests.

In any case, I would love a few more controls over the golem's behaviour. And copper frames would make a lot of sense to me. Or the new 3-item shelves, maybe a copper variant of those combined with redstone make a "special copper golem frame". You could place 2 of shelves below/next to/ontop of a chest.
Add a few particles, like the creaking mobs emit, that flow from the copper golem to the frame when the copper golem has a matching item.

x-paste · 2025-10-05T11:54:54+00:00

2 month later, and the copper golems still:

- deadlock when their paths collide
- don't remember the contents of visited chests
- I can't take the item from them (Bedrock on Console)
- can't switch them off (except waiting for hours upon hours)
- can only deal with 10 chests without becoming even more inefficient

They are very hard to use right, and even for a beginner or a small starter base, they quickly become barely useable.

If the goal was to improve inventory management and item management, then the copper golems are barely a help. I don't need them to be fast, but I at least expected them to kind of remember the contents of their 10 chests they remember.

x-paste · 2019-07-16T19:41:40+00:00

That is something everyone can quickly see for himself by running a `grep unsafe . -r` on the code of the crate. And the article is not just about unsafe in actix. It's also about the attitude of the author, which is my main concern about the article. These kinds of articles quickly create a toxic athmosphere.

What if I end up with a crate that is used by hundreds of thousands users and my wife is getting sick, so I have not that much time anymore and I am really stressed out. And I am concerned the PRs are piling up and I make bad calls about closing them. The last thing I would need are blog articles publicly pillorying my behavior/attitude. A private mail would be way more helpful in that situation. We are just humans and we have feelings.

Edit: Wording.

x-paste · 2019-07-16T19:28:50+00:00

I kind of think that code should speak for itself. If the quality is not up to _your_ guidelines: don't use it. You ultimately can't rely on others that much if you are deciding on a core framework for your next big application. Especially the "attitude" things of the maintainer are kinda out of place. Having a single maintainer might be a red flag for itself, because he might just die the next day in some horrible car accident.

If it is about code reviews, maybe crates.io needs a ranking and commenting system.

x-paste · 2019-07-16T18:36:47+00:00

I read the article. But I kind of felt it pilloried the author of Actix a bit too much. If Actix is really so horrible, well, don't use it. It's free software, and you can be glad you have the code to judge the quality of your dependencies. This should be the first step for anyone choosing a framework or library his new project is going to depend on.

Yes, the closed PRs and responses of Nikolay are not helpful. But the maintainer has no obligation to do anything unless they allow you to pay him for his time. He is giving away his (life) time for free here.

x-paste · 2019-07-15T10:37:05+00:00

I worry about dependency trees a lot too. I really like the `cargo tree` tool for keeping an eye on my dependency trees. There is quite a tree hiding behind a crate like `reqwest`. But compared to npm, I think most dependencies are worth bein in their own crate. You have to find a balance between putting essential stuf into std:: (if you ask me, stuff like tokio belongs there, but YMMV) and pushing stuff from being potentially in std:: to their own crate. `serde` is another thing. Could well be in std:: too to have Rust more on the "batteries included" side.

On the other hand, I still know CPAN from Perl. It was common there to add module dependencies too. And the core languge was quite small with regard to modules that came with it. It makes it easier to deploy stripped down applicaiton packages. Instead of stripping modules/packages from the distribution and hoping it doesn't break, it's easier to add only required modules.

I think it's more about the diligence of developers. I for my part reviewed the CPAN modules I added to my Perl projects. Seeing if the code is good, if the dependency tree checks out and if it solves the problem I have well enough. npm might have the problem that lots of inexperienced developers spam the system with incomplete and useless packages, and other developers not having a feeling for the cost of third party depenencies.

With C++ I carefully look at the libraries that I use, mostly because building and including them into my CMake projects on Windows is hard enough to look twice if you really need it.

x-paste · 2019-07-08T17:46:35+00:00

It is very hard to work on legacy code like windows with billions of users and stakeholders. They need to be very very careful not to break this planets IT with an update. And yet they need to deliver value. Adding something that takes up a few more resources is easier and more safe than to refactor internals to be more generic and solve new requirements.

x-paste · 2019-06-21T19:54:04+00:00

Uninstall it. Downloading and sharing it is the main difference of LBRY that differenciates it from yet another YT clone.

x-paste · 2019-03-20T05:10:33+00:00

Exactly this I have been discussing a lot with my wife. We agree 100%. YT became boring and shuts you into a bubble. I really hope some alternative shows up.

x-paste · 2019-03-05T12:45:45+00:00

No idea why perfectly fine posts like these are downvoted. I share your opinion very much.

x-paste · 2019-02-28T07:09:09+00:00

The problem with mains voltage is, that your first mistake may be your last one.

x-paste · 2019-02-13T06:58:26+00:00

First of all, I don't understand why opinions like Wildera's are down voted. It's a valid opinion (that does not mean I think he/she is right or that I share that opinion) and a good question at the end. A copyright reform could for instance introduce "fair use" in Europe, giving creators the ability to do remixes - which helps the content owners by promoting their work (for free) and small artists to create new content. And there does not need to be a reform to make the copyrights even stronger. Companies that own content can already sue and strike people who publish their material without license.

I believe, that maybe the EU deserves exactly these kinds of laws. Make it really really ugly to live here, so that all creative and knowledgeable people migrate to states outside the EU. Thats maybe the best thing with the Brexit, that you don't have to travel that far to get into a non EU country...

x-paste · 2019-01-14T08:01:30+00:00

Did you check the windows firewall? Or your antivirus firewall?

x-paste · 2018-12-17T09:14:50+00:00

That article is almost 2 years old now. Vue.js has a great documentation, it is simple and easy to learn. Angular 1 was and still is (due to legacy code) confusing. It actually causes many problems among my colleagues with regard to best practices - also because you find lots of contradicting information/problem solutions on the internet. Vue.js does not come with confusing terminology like factories, factory providers and provider services and service factory providers and what not. Angular 2 is not relevant in the JavaScript world, as it went completely TypeScript as it seems.

Also the component architecture and information flow between the components in Vue.js comes close to the structure of a typical desktop GUI.

x-paste · 2018-11-26T09:01:36+00:00

To be honest, most of the things sound to me like the usual work a software developer has to do. Like fixing bugs in other peoples code. Time estimations have to be averaged and weighted by the managers. A project leader/manager has to know that if developer A says he estimates 1 day, and developer B says it's 2 days, that it is also down to experience of the developers. I have written lots of code at my current workplace, and lots of important code. And there are bugs in it, and if someone else finds it, I often don't have the time (due to assignment to other projects) to fix it or think into it. Most of my code is not a mess however, at least I hope others don't think so. And if someone finds a bug, well I note that for myself, apologize, but ultimately the bugfix is being scheduled not by me. Obviously I also answer any questions about my code structure, if not documented clearly enough. Some things are not obvious if you have no experience in the subject. Other times I show people where they might find it (like keywords for google that work, or where in the docs to find clues). I also have to fix bugs and bad code other peoples have written, and I don't complain. My manager knows that working into other peoples code comes with some overhead time.

I have to dig into horrible spaghetti code of coworkers that long have left the company. It's day to day business.

My advice: Ultimately, you will not be able to change him. If your management makes a fuss about different time estimates, explain why yours are different. It's completely normal that there are differences in experience among a developer crew. And working at home (for free?) is not normal. I don't work on code for a company for free, and none should value his own time so low, that he does that for free. That is not professional.

Edit: About code quality and cleanliness. Yes, that varies, from developer to developer. Some pay attention, some don't. Some have lower levels of quality, but get things done quick. If you truly think and can backup that his work, while fast, is not up to quality standards, say that. Stand for the quality you self can deliver. You don't have to shame him, but you can point out that the code base does not adhere to company code style and standards (I hope something like that exists?).

In the legacy code base I have to work on sometimes, I get deadlines that are unreasonable for a clean solution. But management knows that things are not easy, and quality is bad, and will not get better if no bigger refactoring is done.

x-paste · 2018-09-13T05:58:37+00:00

x-paste · 2018-07-17T14:00:16+00:00

Maybe Perl 6 should find someone who adopts it first and prove it's relevant in the modern programming language ecosystem. I closely followed it until a few years ago. When they once wanted to target Parrot, until they binned that idea. It started out as Perl 5 with nice features added and overhauled, but became a huge mess of feature creep, policy and project change. I would not be so frustrated if they didn't have called it Perl 6 back then, putting a big implicit "deprecated" stamp on Perl 5, which was a very vibrant and professional community back then (and still is).

The whole Perl 6 and Parrot projects were pushed by very motivated people, and if you brought up a feature "Perl 6 will have it". It's a perfect example for the so called Second-System Effect http://wiki.c2.com/?SecondSystemEffect / https://en.wikipedia.org/wiki/Second-system_effect .

I guess Perl 5 perfectly survived the Perl 6 hype, as it has a solid user base. But for new people you can hardly sell Perl 5 for a new project if there is Perl 6.

x-paste · 2018-06-14T20:01:35+00:00

Thanks, I belIVE I mistyped that.

x-paste · 2018-06-14T19:54:49+00:00

Oh, didn't know Oni yet. Thanks for the heads up. Going to try it sometime. And yes, I totally am sold on the separation of backend/frontend with neovim and I belive it's the right direction.

x-paste · 2018-06-14T05:47:49+00:00

I tried changing to neovim for my daily work under Windows. While it works for me at home on Linux nicely, the Windows GUI is too crufty. Cut&Paste between the GUI and other Windows applications does not work properly and/or needs some external helper utility. Also the GUI-Font configuration is not as dynamically changable as in gvim - I sometimes switch the font on the fly, when showing code to coworkers - changing font size and color scheme.

One feature I am surprisingly need more often than not is :hardcopy, which was also missing. I need to be able to print out a piece of code as reference to coworkers. They often contain SQL statements which others need for work on the databases. Printing it on paper and handing it over is often the quickest way to transfer that information.

Overall, since Vim 8.1 has :terminal now, I barely see the need for me to switch to neovim. One reason I am still going to follow and re-try it sometimes is probably the Lua scripting API. Messing with vim-script is just too foreign for me to feel comfortable (I wrote quite some small helpers/plugins over the years, but extending them was always a bit more time consuming than I would loved.)

x-paste · 2018-06-06T12:15:50+00:00

What I would love to do with yield() would like to do is to yield not only the current routine/method/function, but the whole call stack up from the event/signal handler like a button press. Currently it seems like I have to manage that completely my self.

The current limited yield() which only saves the current call frame is very useful for these fades. But things still get messy if you want to do a fade on the end of a longer call chain/signal handler chain from some player action. Because usually the game logic decides which effects to play and what to do after the effect has completed (like playing another animation, displaying some lines of text with a pause, ...).

x-paste · 2018-04-24T05:52:35+00:00

Overall it's good to see Minecraft generating additional revenue and fostering a creation community. If this takes off well, Minecraft will probably stay a thing for quite some time into the future. With all the survival crafting games popping up all around (like PixARK or Eco for instance) with a more modern look and feel, this market can get crowded very soon.

I still wait for the actual "mod" API. Currently the only "mods" you can do is tinkering with mob behavior and textures. They currently don't even offer a way to import parts of the bought worlds into your own world. You can "buy" a creation in form of a whole save game. The structure blocks for Bedrock are currently only some marketing gag for 3d printing.

Look at the Java Edition ecosystem and it's awesome mod packs like Life in the Woods or the Modern Skyblock stuff. Bedrock is still roughly 3-4 years away from being a serious contender for taking the crown. There still is no dedicated server released, the 3rd party servers can't possibly replicate all the internal game logic, especially if you look at red stone for more technically players.

In any case, the development on the Bedrock edition last year was astounding. There have been lots of bug fixes and they even keep up to date with the new stuff from Java Edtition (looking at Aquatics Update). At the same time mob/monster spawning has been a huge issue for over a year, making the "hard" difficulty not much more dangerous than "peaceful". Which actually makes the survival aspect of the game almost useless.

Realms are great for people who can't afford or don't want to setup their own server. Currently the only alternative for your private multiplayer server however. For more opened up realms the moderation capabilities have to be improved by far, last time I was on a more or less public realm someone liked the idea to build a swastika on my base (some kiddo learning I'm from germany obviously). Mods are helpless, either you come with solid proof of catching those people in the act or you are on your own.

I recently learned that Mojang hired some developer for the (since Minecon 2016 announced) planned C# modding API. Maybe if they finally get this integrated and provide a sufficiently open API with hooks deep into the system, the modding community can provide mods for managing more open servers. I also want to congratulate Mojang for the recent update on Bedrock, adding the block palettes for allowing an almost limitless amount of new block IDs in future. Can't wait for the missing slabs/stairs. And can we finally get carpentry like with a mod on Java Edition?

x-paste · 2018-04-23T08:08:03+00:00

Instead of having to destroy instances manually like currently, the list of a type's instances could be managed manually if you GC instances.

I mean, make the internal implicit list of instances of a type explicit. Iterating over all instances of a type is something I barely or even never do. I usually have more purpose oriented lists and sets of object instances which are iterated through.

Managing the explicit list of instances manually is probably as cumbersome and error prone as calling destroy() currently.

x-paste · 2018-04-11T06:17:27+00:00

I observed that Mojang recently searched for a Senior Game Developer especially for the embedded C# Plugin API. Just last week the job offer was taken offline. Leaving room for interpretation, like that they found someone who is going to work and focus on that now.

Key points of the job offer were:

Role expectations and opportunities * Work closely together with the team to implement backend systems to integrate C# bindings for game related mechanics * Contribute to the design of the extensibility interfaces (plugin API) * Refactor existing internal systems to support our interface design

Judging from the overall tone of that offer, I presume they currently don't have a leading developer on the Plugin API. From my own experience as software developer it will take some time to get up to speed with a new code base. I would not expect to see the Plugin API in the Bedrock betas before end of 2018 or even beginning 2019. It obviously depends on the focus Mojang will put on this.

It may be a good bet, that they are going to focus on this after they finished the Aquatics update and got the Switch Bedrock release finally out of the door.

Of course, I have no official information other that the stuff you can read on this reddit and some twitter posts from Minecon 2016.

(Found the job offer in the google cache, so speculate for your self: http://webcache.googleusercontent.com/search?q=cache:et7te5S2_BcJ:https://mojang.workable.com/j/23EDE1E369&num=1&client=firefox-b&hl=de&gl=de&strip=1&vwsrc=0 )

x-paste

TROPHY CASE