That's interesting, because I found it trivial to win with the largest boat. Tank one hit, lead your target, blast away. I remain undefeated with the largest boat.
By contrast I found winning with the medium boat required the most skill, and lost the first few times I tried.
>Why don't we use AI to generate lofi samples for tracker music?
Because generating lofi samples is already pretty easy with waveform generators and existing tools. Burning millions of tokens worth of compute just to make a bass kick is profoundly wasteful.
I haven't used it in ages, but it used to be that Bootstrap also shipped drop-in CSS that would give you decent-looking styles on all the common elements, so a single minified style sheet would give you that classic "2010s startup" look.
I get that Quebec and Ontario have 65% of the population, but why do they have 100% of the seats on a committee that shoves surveillance and gun bans down everyone else’s throats?
Not a clue, but if there are only 7 seats then all 10 provinces can't be represented anyway. I highly doubt political opinions about surveillance are aligned with provincial borders.
Saskatchewan and Manitoba are also over-represented.
BC, Alberta, and Ontario are under-represented. Ontario, for example, is about 39% of the population of the provinces, but only 36% or so of the seats.
The allocation is an imperfect formula, to be sure. I doubt it makes much of a difference in practice, except as propaganda fuel for foreign influence operations driving Alberta separatism. The degree to which most provinces are under- or over-represented is less than 1%.
>I would suggest data centres near the arctic - it's close to most of the Northern hemisphere's users, presents an easy option for cooling (the place is a heat sink), and, with collapsing glaciers, there will be abundant hydro power to be used.
Advocating for exacerbating the melting of the polar ice cap, which will endanger dozens of millions of people, just to have more convenient data centers for manufacturing AI slop, is peak HN.
>So a $4b data center on Earth delivers the same value as a $40b data center in Space?
It may do so, initially, compared to a new-build DC.
But, critically, you can upgrade the racks in an already-built DC without demolishing the entire building. You can't do that in orbit, so the full lifecycle ROI is lower.
Orbital DCs are constrained by cooling and by bandwidth. Even a space-to-ground laser (which does not currently exist in a sufficiently-mature form) has a fraction of the bandwidth of a proper terrestrial fiber line. So you're paying at least 10x for essentially a disposable datacenter that can't move as much data in or out, and likely will not be as powerful as a terrestrial DC because of the cooling constraint, just to have it in space because reasons.
I don't see the business case, at all.
This is so transparently another hyperloop-esque pipe dream invented for the sole purpose of inflating SpaceX's valuation.
>And telling maintainers how to act will not fix anything.
Indeed. For too long, maintainers were expected to be gracious, courteous, and polite at all costs lest they be labeled "problematic", except for a few who were too influential to be muzzled like Theo de Raadt or Linus.
Perhaps we need to normalize bullying people who submit obvious slop as PRs.
No, you absolutely should be gracious, courteous, and polite. But only at first. The duty of maintaining a functional community doesn't mean you're obligated to suffer unlimited abuse.
You can be if you want to but social skills should not be a requirement to lead an open source project. If you create something and share it that doesn't oblige you to even respond to anyone.
Of course, a hobbyist putting his code out there is under no obligation whatsoever. But we aren't talking about small time hobbyists here. These are professionals who are either paid as part of their job or else contribute their spare time to maintain important projects that are part of a large ecosystem that is relied on. There's a community and it necessarily has behavioral standards as part of the shared goal of maintaining group cohesion.
There is no reason you can't be gracious, courteous and polite while refusing to accept or even to review the PR. These things are not tied together. You can also refuse to be bullied by submitters, stop engaging altogether. But bullying is part of the problem, not the solution, normalizing bullying is the wrong direction and will not result in more secure code.
>There is no reason you can't be gracious, courteous and polite while refusing to accept or even to review the PR.
I agree, and I never suggested we cannot do these things.
I'm saying we should normalize immediately telling people who submit obvious AI slop to fuck right off. Submitting AI slop pull requests is rude. It is disrespectful of the maintainer's time and energy. I see no reason why I or anyone else should be respectful of someone who has already demonstrated a lack of reciprocal respect by submitting a vibe-coded PR that they obviously haven't even read or tested.
Because encouraging a culture of disrespect and bullying is actually bad for security not good for it. Politely decline, please, no need to be rude because of your (not always guaranteed to be correct) perception of where someone (or some thing!) is coming from.
reply