In an attempt to try and translate lawyerese into nerdish, I wrote up OpenAI's trade mark failure before the CJEU.
Mostly because I'm seeing lots of nerds who can't read or understand the decision.
https://tommorris.org/posts/2026/european-court-lawsplains-trade-marks-to-sam-altman/
I wonder why making something available on the web has to be such a cluster fuck of a mess? Nothing is easy nowadays and the tools you’re supposed to build with are JS based garbage.
I think making a simple web version for my app could be a good idea, but nothing of all the nice UI and backend is reusable for that. Everything has to be custom and ugly.
Do US companies really bother doing this? Why on earth? Seems so daft and somehow childishly petty. Well, I can't add some of their products to my app then.
In general I must say that the conversion to gRPC was really smooth. Not a single case of data corruption or similar and everything was pretty smooth sailing. Will definitely keep expanding this API for the future. Assuming my app doesn’t die, of course.
Recently updated the backend for my silly little app to gRPC from plain REST. Works beautifully and is a bit faster too. Now started the task of updating all the admin endpoints to gRPC too. There are almost as many endpoints as for the client, so this will take a while. Fortunately I can take them one by one and still have a fully working admin setup. Gives me an opportunity to fix up some rough edges in the PyQt admin app I use, so it's a win-win I guess.
Americans saying “I didn’t vote for him, why are you screaming at me” piss me off.
Look at Europe, and France. People bring the country to a halt if they increase retirement age for a few months.
Look at Iran. People risk (and often lose) their lives protesting.
You barely protest. You don’t strike. You don’t refuse their orders. You don’t become violent.
People in countries your government is threatening don’t give a damn who you voted for. And they don’t see you doing jack shit about it.
Seems TexturePacker (https://www.codeandweb.com/texturepacker) does not have support for Bevy or Bevy does not handle the atlas format. That's a shame, as it was a really useful tool aeons ago when I used Cocos2D to just pack random sprites into a single texture and then refer to them by name. Efficient loading of lots of small sprites. Parsing the texture atlas meta data should be quite easy, but setting up the named sprites for Bevy is probably a pretty huge task.
Or rather, the Mac screenshots can be automated, the iOS/iPadOS ones can not be. The reason is bugs in "Sign in with Apple" for the simulators. It hasn't worked at all for 5+ years and Apple just doesn't care. So all mobile screenshots have to be done by hand for 12+ languages. Yeah. Not happening considering how few users care about the app anyway.
The Mac app's screenshots could be automated, but it's a huge task to do and probably not worth it.
Time to wrap up this iteration of my app and do some final testing before release. I'm quite happy with how the app works now and think it's getting better with each version.
The Mac app will need screenshots though, and that's a process I hate with a passion. Updating screenshots is such a clusterfuck as Apple's tools and App Store Connect makes it immensely painful. It can be automated, but that will take weeks of solid work to do and not worth it.
Much better!
I wonder if there's a setting for rustfmt that makes it not break up code into one symbol per line like this. This is atrocious. Who on earth wants { to be on a line of its own? I want to keep things on one line if possible unless I've manually added a line break. I have a wide screen, I don't have a high screen. It's also a bigger mental load to grok code logic and flow vertically than horizontally.
Aha, the issue is that transforms are both read and potentially updated and Bevy can't know that the two queries won't overlap. This seems to fix it as bevy can now know that a Player's transform is never updated.
I guess these parameters will only get more complex as time goes on...
This wasn't exactly a helpful crash. I assume my updated system isn't compatible somehow. It does compile though, so it should be fine. And there is only one Player, so the Single<> should be fine.
At least the way I naively construct my systems they tend to end up with pretty complex arguments as you inevitable need to access different things. It seems like it has to be slow? Or maybe the ECS part makes this really streamlined?
Something is really random here. If I merge setup() and load_assets() into one function it does not always work. Sometimes it does. Both do just one spawn() call.
Also I can sometimes see my enemies flicker for one frame or so before being cleared. As if they are all despawned after the first frame.
Meh. Time to do something fun.
Also in this snippet A behaves differently from B. If I chain the systems like in A I see that they all run in the correct order, but the stuff from create_player() and create_enemies() is not shown.
If I call them all separately then everything works. They are called in the same order (seen via prints) and all entities are spawned.
Clearly there's something I don't understand here.
Spawning text this way seems clumsy, but adding a Transform had no effect. I guess a Text is somehow special as Text2D does use a Transform, if I remember correctly.
The create_ui() function is simply supposed to spawn two label entities that keep track of the score and current enemy wave so that these can be updated later.
Do systems somehow set "state" for systems that come before/after them? Commenting out create_ui() makes everything work, except there are no score and wave labels, of course.
2/2
Does the order of systems in Bevy matter? In this little game all the Startup systems simply spawn() stuff into the scene. But it seems my create_ui() system causes whatever system is right before it to "not work". In this case the enemies in create_enemies() are not visible. If I move create_ui() one step up then the player in create_player() is not visible. I've stumbled upon cases like this before but dismissed them as "I have no idea what I'm doing".
1/2
