My tools will catch string matches in docs, but if you're using reflection or etc where it's "too weird" for tools I can see it being useful there, yeah.
Picking on a particular nit here, but I think it is indicative of the broader flaw with this argument:
To rename `PostgreSQLClient`, I press F2 and type the new name, and I'm done.
I don't have to wait for an agent to "perform the refactor, update references, run the tests, fix the missing pieces, and mark the relevant checkboxes in the ticket" (btw, what checkboxes..?)
I press a key, type my change, and I'm done.
Wasting time waiting for tokens is also wasting time.
Whether the performance difference between Go and JS (via node or whatever) matters depends on your use case - it definitely matters for the TS compiler, but it might not matter at all for your CRUD app.
A lot of games are less latency-constrained than you'd expect. FPSes are obviously rough with input lag, but stuff that's turn based and even many platformers feel "good enough" up to like 150ms
The person you're replying to isn't me (the person you're quoting above), but to be clear:
I'm not trying to be insulting, here, it's just kind of a bizarre, eyebrow-raising thing to see. There's a reason you're not seeing any AAA games doing this, y'know?
If you're doing something that's really unusual, you're going to have people going "this is really unusual".
Please don't take this the wrong way - this is sincere, well-intentioned advice: have you ever watched Shark Tank? The best people on there can still give a good pitch when their ideas are challenged.
The games industry - and especially the multiplayer games space - are brutal, and players are going to be way more critical, way more rudely, than anyone on HN.
It would benefit you and your game greatly to practice selling your idea in the face of criticism and doubt.
Taking 2.5 megabytes per second of compressed new state information, uncompressing it, and applying it (across the "thousands and thousands of networked entities", etc, that keep being talked about) to the game state? All the memory thrash that implies, along with the knock-on effects (animation updates, yadda yadda)?
Yeah, that has a performance cost.
Will this impact a big-money gaming rig? Probably not? Will it run good on the Steam Deck? Probably not.
Generally, in a game loop, all this stuff is going to be single-threaded and blocking, right? It's mutating the game state, that's the classic why-games-suck-at-thriving-on-many-small-cores problem. So your performance capacity ends up being tighter than you might think relative to other "ingest data" tasks.
Let's say your game's networking runs at 30 ticks a second, and you've done a great job in uncoupling rendering from the game loop, so you're lucky enough to not have to worry about that. You still only have 30ms, on a single thread, to handle networking (likely no special kernel-skipping stuff on clients!), unpack, apply and propagate your changes, and also do your local game loop stuff. If you miss that interval once, the game starts to fall behind and feel bad to play.
Now, you could say "lower the tick rate", but then you'd need less data, too, and your game gets less responsive (fine for some games, not for others)
Client performance characteristics? Speaking very broadly... I can't imagine a game that'd need that much data unless it involved a lot of streaming assets (audio, video, etc) or really, really naive netcode.
If you're using stream compression, 20mbps would likely be a lot more than 10 times as many objects (and you shouldn't be serializing the whole state every update, and... yadda yadda)
You can fit a lot of game in 2mbit/s with a little bit of work.
Yeah, this strikes me as strange. If you're sending that much data constantly, you're either syncing too much stuff too often, or you're not using compression when you should be (shout-out to Oodle)
Something that this article doesn't mention that's going to be a big constraint: each of your clients parsing 20mbps of updates is going to have a performance impact on those clients.
At the end of the day, you can only "democratize" while you have players, and performance constraints on end users aren't getting any looser
Game data and video data have very different constraints. Depends on the nature of the game, of course, but with jitter and all that, video can just run a buffer and manage network conditions (more) trivially, but a game needs things to be a lot tighter to avoid gameplay-impacting desync
Responsibility is a separate question from correctly reporting on the events that occurred. "A protestor shot someone" is correct, "a protestor shot someone and the group is culpable" could be argued, but "the protestors shot someone" is simply untrue.
Insane charges, insane justifications, and judging by the comments in this thread, I feel insane for having ever believed in the myth of the "decent conservative".
I feel like "the upside of the privacy invasion glasses is that parents can have induced videographer anxiety where they once would have had to suffice with memories, how horrible" is not compelling.
I wouldn't malign you, but if you were a close friend I'd probably approach it in the same way I approach friends who are getting a little too deep into gacha or gambling or funko pop "collecting".