brian

there are more aggressive css "resets" that set the default display type to flex. there's no problem making anything a flexbox if it displays the way you want it to

objectively the one with the cult is a good recommendation for a beginner since there's a strong community making content, arguably the most important factor in choosing something

godot also has a lot of stuff baked in, so the community tends to use the built in solution for everything. you won't end up with one tutorial recommending a collision engine that makes assumptions that don't work with the other tutorial for different pathfinding or whatever. they all start with basically the same assumptions.

pygame is a little intimidating since you start with an empty file and a pygame import. there's no real enforced or even commonly followed structure beyond that. beginners can figure it out but it leaves a lot of architecture questions open for you so your tutorials probably won't line up well.

and I say all of that as someone who doesn't particularly enjoy godot, especially gdscript.

since you haven't said anything about type of game, if you want to start at the dead simple side and visual novels sound interesting maybe look at Ren'py?

visual novels have less going on than a big 3d game, so if you want an easy start from 0 it should be as close as you can get. python is straightforward if you don't have programming experience, but otherwise is really commonly used so gives a nice basis for whatever else you want to do.

ren'py also has gotten plenty of commercial use if you wanted to go further in that direction. most big name vn games use it.

yeah but you still basically end up duplicating the internal structure of the react component but in a css file then.

there's nothing definitive that makes one of those 3 options better, it's all preference. any of them fit better than global css though

sure, but both of those are significantly better than a css file. tailwind tends to match the internal structure better, css in js tends to match the component structure better.

tailwind doesn't have a runtime though, where css in js libs generally do. not that that's a big point. the difference is mostly preference

it matches the component model of react etc

did you read their statement? they do.

ai detectors are not good. may as well ask your magic 8 ball

if it's not clear if it's ai, it's not the code this policy was targeting. this is so they don't have to waste time justifying removing the true ai slop.

if the code looks bad enough to be indistinguishable from ai slop, I don't think it matters that it was handwritten or not.

you shouldn't be able to tell if someone used ai to write something. if you can then it is bad code. they're not talking about getting completion on a fn, they're talking about letting an agent go and write chunks of the project.

when futo dissolves as an organization, or someone forks their software and maintains it better than they do, that fork still has to have the button to pay futo and not the new maintainer.

there are restrictions on what you can do with the source. that is not open. the source is available and they'll accept your donation of code, but you are donating to a company's product, not a community project.

you can also buy a nice USB/Bluetooth dac instead of the inline ones that tend to be more fragile. better quality than an internal one and the flexibility of Bluetooth if you want it. generally a little bulky but if you already have wired headphones I don't think it's significant