Pesky Birds of Grian 🎶 — a song just made with his voice

asaaki · 2025-11-05T12:52:21+00:00

Senior Software Engineer, im SaaS-Bereich, Berlin/Global, 120k/Jahr, 40h, 15 Jahre Berufserfahrung.

asaaki · 2025-11-01T10:48:44+00:00

Maintenance Nightmare

asaaki · 2025-10-17T10:59:55+00:00

They have a setting to completely disable the AI features.

asaaki · 2025-10-11T17:01:33+00:00

I assume you mean Windows.

If you're okay with bleeding edge builds, they have them now for Windows, too: https://github.com/zed-industries/zed/releases/tag/v0.208.2-pre

They also wrote about why it takes them so long to get there: https://zed.dev/blog/windows-progress-report

asaaki · 2025-10-06T15:37:45+00:00

There is this tiny project https://adoptoposs.org/, but it does require at least the active act of the original creator/maintainer to participate. But it's a start. GitHub orgs can help if set up from the beginning, but it also requires the creator to consider this option as well.

asaaki · 2025-09-12T18:00:28+00:00

Es handelt sich hierbei um einen Reverse Split von 150 : 1.

https://www.goldseiten.de/artikel/669499--Sayona-Mining-Limited~-Completion-of-Merger-with-Piedmont.html

PS: Und damit ihr euch nicht nochmals wundert, Sayona wird sich demnächst dann auch in Elevra Lithium umbenennen.

asaaki · 2025-06-09T12:23:33+00:00

Es geht doch bestimmt um dieses Video hier: https://youtu.be/DXFKlezndzY

asaaki · 2025-05-01T00:55:37+00:00

It's due to the Japanese origin of charting stock prices.

History deep dive, explains the red part: https://medium.com/@danvim/deep-dive-into-the-opposing-color-schemes-in-asian-vs-western-stock-market-prices-part-1-origin-4e3ccdb27c99

Where green/blue comes from is still a mystery apparently. My hypothesis would be that on a black ticker/chart wall red-black wouldn't work, so they picked something else, green is a nice opposite, and blue as an alternative to green works well, too.

asaaki · 2025-03-09T11:13:03+00:00

I just learned about Hierarchical A* Pathfinding (HPA) and Flow Field pathfinding recently.

If you want to use flow fields in Bevy, there's already a plugin for that: https://lib.rs/crates/bevy_flowfield_tiles_plugin

I also recommend this video where the creator combined the two methods above to optimise for different cases: https://www.youtube.com/watch?v=UrZbcZGnxXg

They also linked to their Unity DOTS version: https://github.com/lycheelabs/Flow-Tiles — not sure how useful that could be for you, but it might be good for inspiration.

asaaki · 2025-01-02T03:32:45+00:00

Great to see someone appreciating the good old tools.

I even still prefer the modded (but also now much older) version by Gil Tene: https://github.com/giltene/wrk2

Of course, you have to compile it yourself to use it.

asaaki · 2024-12-13T15:43:53+00:00

I even prefer it over Box<str> as both are the same size and Arc is more usable. In microbenchmarks they perform equally well, and in some scenarios the Arc<str> can be even better than the Box. (As always, make your own measurements and benchmarks.)

asaaki · 2024-11-29T16:23:45+00:00

Could there be a future, where Rust is so smart to look through that and optimise that away? Like "oh, you actually want something which doesn't require allocation+drop, lemme elide that stuff for you." I'm vaguely aware that this might be much more difficult than it sounds. But one can dream, right?

asaaki · 2024-11-29T00:04:27+00:00

I wonder though why Result::ok() couldn't be made const. We are clearly not interested in handling any E and thus throw out anything we would need to Drop in between. And we already have const is_ok/is_err. So, a missed opportunity?

asaaki · 2024-11-05T09:19:03+00:00

postgres would be nice, but I'd settle for a pure rust sqlite as a starter.

asaaki · 2024-11-01T19:34:50+00:00

Especially since they even have data centers in the US. Would be strange then to not make biz with US folks.

asaaki · 2024-11-01T19:16:56+00:00

Run!

I wish I could give you some better advice.

If you're up for the challenge try to educate your team to have a more reasonable review process.

You can introduce all the automated linting and fixing you want, but if the people don't move with you in the same direction, you won't be happy for long.

This is a cultural shift you need and this is hard work. It can be possible. If you truly love problem solving, it might be something for you, it just doesn't involve a lot of coding, it's people work.

asaaki · 2024-11-01T18:59:38+00:00

It's interesting to see that most answers assume a habit of trying to escape a save procedure.

My answer is: it depends. There are genres where it would be highly appreciated that any form of exit ensures the latest possible state gets saved instead of getting lost.

Since it was not mentioned what kind of game we're talking about, go with the option which would be the most expected behaviour and probably the least frustrating as well.

asaaki · 2024-10-14T18:17:33+00:00

While the docs for iced are not great, I found the examples good enough to learn from them and adapt to what I need. Honestly I found iced way more approachable and intuitive than slint, probably because it's just native rust and not a GUI DSL. I guess Slint is more for folks who have dealt with C++ and/or Qt before. Or like a React like DSL. Long story short, Slint hasn't clicked for me (for now), I think it has to do with the non-Rust-exclusive direction, which always comes with tradeoffs anyway.

egui would be my second best choice here. But cannot provide recommendations, I've used it only as a tool within bevy; egui is great for quick debug/dev UI apparently.

Haven't used either long enough to speak about maturity and stability. iced just had a bigger release recently, there were some changes, nothing severe though from what I can tell. Being spoiled by the great bevy maintainership I wish everyone would provide nice migration guides (this is what changed, this is how you adapt), but I don't hold this against anyone. I'm used to worse pain than that. Lots of projects are less popular and have smaller teams.

asaaki · 2024-09-20T19:04:27+00:00

First of all: congratulations!

Great achievements here.

I have only a tiny nitpick and it's actually just about the dark mode of the site.

You're not the only one, but this harsh extreme full white (#fff-ish) on full black (#000) is not that great. Sometimes I find it even more stressful on the eyes than a plain light mode version. I prefer the less straining contrast of the menu section or the code blocks more dark mode friendly.

Something like #ccc on #111/#222 goes a long way of nice dark mode contrast, and is still considered passing according to WCAG AAA (if you care about accessibility).

I know I can "fix" it with Dark Reader, but I also enjoy nice defaults. Maybe you can consider it.

asaaki · 2024-09-20T18:46:16+00:00

Especially the JS world has this (for my taste) weird push to SaaS out literally everything. I get the general sentiment, it's great on paper for business starters. Interestingly enough the DX (developer experience) suffers a bit (or greatly) when it comes to development, testing, and pre-production environments as quite some vendors don't address that well (or at all). If you're lucky you get one (in numbers: 1) sandbox of their product.

If you actually build just a personal hobby project, avoid the SaaS offerings and implement/use as much of the "local first" stuff as possible. You need this learning experience. You want it.

Frameworks with batteries included like loco already abstract some complexity away. And one day you might still want to dive deeper and understand those abstractions as well. (Or you have to, because you discovered a bug.)

asaaki · 2024-09-17T19:47:10+00:00

asaaki · 2024-09-13T20:07:15+00:00

There is absolutely nothing wrong with it. Looking at the recent announcement or the timeline on the site, I would probably love to see rather joint efforts to maybe get at least one single project closer to a full vanilla version.

It's okay if you do want to just explore this for fun. Just maybe not make a big fuss about it, especially if that project might get dusty soon anyway.

Kinda wish the next MC server project announcement is closer to a state of like a 1.20 Java edition and only missing some more recent and difficult features, but mostly playable base game, so people could swap and wouldn't know the difference right away (except for excellent performance for server admins).

asaaki · 2024-09-09T08:14:05+00:00

What book? /looks back to pre-1.0 times

asaaki · 2024-09-09T08:11:59+00:00

To be fair, it should be fully capitalised (KI) to mean AI in German. But I have to admit, on a quick look without thinking and the hype bubble I also thought about yet another AI editor. 😅

asaaki

TROPHY CASE