debaserab2

Congratulations!

I'm going through a similar phase myself spurred on by the pandemic (games are, after all, why I started programming in the first place).

I'm continuously amazed by how complex even simple games can be, especially if you're not using one of the big game engines. It's incredibly easy to get sidetracked or over-engineer a certain aspect. It's made me realize just how tough shipping a game - so congratulations on that. It's a huge feat.

This may not be age appropriate depending on your kid, but the (free) CS50 course for games from Harvard [1] is outstanding and accessible to someone with a beginner level of experience. It's not as intro level as something like Scratch would be, but it's very practical hands on learning with tons of resources for anyone who wants to get "serious" about game programming.

[1] https://cs50.harvard.edu/games/2018/

The only people I see excited for "web3" (which I believe has become a blanket term for the metaverse, NFTs, and other crypto schemes) are those carving out real estate there for themselves in order to become future landlords.

> publicly shame someone who's asking to wash your car window for $1

I don't think this metaphor completely fits. A more apt metaphor might be someone telling you your tire pressure is too low when you know your tire pressure is perfectly appropriate for the given types of tires you have and climate you're at.

It's pretty annoying when my boss (or my boss's boss) ends up reading one of these emails and freaks out because they don't understand the severity of the problem. Usually when I see these emails they often are blasted to every email that can be found on the contact page, including things like sales channels. Explaining the context of security vulnerabilities that are irrelevant given our configuration is not a particularly fun or easy things to do to non-technical executives terrified of data breaches.

Platform loyalty in gaming has always struck me as an odd phenomenon. You don't hear people raving about netflix or hulu being superior, but for some reason there is a huge fanbase for Steam itself.

I mean, I don't mind steam, but I'd really prefer to have software that I purchase not check with a gate keeping entity before launching itself.

Why would that matter?

I don’t think the distinction between framework and library matters that much. People choose between react or angular (or others).

I know you're entirely right, but sometimes when I see things like this in Typescript...

https://github.com/sindresorhus/type-fest/blob/main/source/r...

I can walk through it with enough pause, but it kinda makes my head implode when I glance at it.

Just curious - what's a popular non-RPG MMO?

Entirely. Almost seems like word play to soften the blow of critical headlines.

> MMOs have been very viable from both a business

Really? Everything that's not named World of Warcraft seems to die out, usually in less than a year. It's a genre that's been a notorious recipe for failure for most companies not named Blizzard.

I find dependency arrays to be neither intuitive or easy to debug. When you're missing a parameter or use the wrong one React can emit some pretty weird side effects that are hard to track down back to the dependency array.

I generally like shaping my components as functions first and use hooks because I have to in order to do this but definitely not because I find them easier to understand than component lifecycle methods (even if they may be less verbose).

To me, hooks are the ugly part, writing component as a single function is the part that makes it worth it.

The original intention of the web was to make hypertext documents available to people - PDF is just as valid of a format for this purpose as HTML is. Perhaps more inaccessible but certainly not antithetical to the web.

If you implement it on the frontend you lose all the builtin navigation behavior that the browser gives you natively when loading pages. You instead get to build all that behavior yourself in places where you think it should exist using your best judgment (things like deciding when to push to browser history state, for example, may be perceived as breaking the back button to many users if you haven't thought through your app's navigation hierarchy very carefully).

Didn't say it was trivial. But that's what users expect: a reasonable right to data privacy.

When did "deleted" become a vague term?

Deleted means removing as much PII as you reasonably have authority to do so. It means purging all that data from all databases with a guarantee that you will be removed completely from all snapshots in a reasonable amount of time.

This should be the default, normal understanding of what it means to delete your account.

It doesn't mean set a flag in a database so when your company gets acquired in a few years your new owner has a nice little trove of data to mine of people that explicitly opted out.

The former can become the latter pretty easily though and without any consent through both illegal (hacking) and legal (company acquisition) ways. Corporate surveillance very much is a part of the problem and you can't talk about one without talking about the other.

This is the #1 reason I am all in on Chrome even though I don't really want to be. I'd like to be using some other Chromium based browser, but I can't really leave my passwordless life, and Chrome makes it all too easy to sync my garbage passwords across all devices with Chrome installed (which is available pretty much everywhere).

It was the same wikipedia link that you cited.

Even using your songmeanings.com link it doesn't appear that the common interpretation is satirical in nature.

Especially considering the narrow interpretation the op is using for both songs. It's amazing how easily people will gaslight themselves.

> The lyrics reflect the concern felt by Strummer about world events with the reference to "a nuclear error" – the incident at Three Mile Island, which occurred earlier in 1979. Joe Strummer has said: "We felt that we were struggling about to slip down a slope or something, grasping with our fingernails. And there was no one there to help us." > The line "London is drowning / And I live by the river" comes from concerns that if the River Thames flooded, most of central London would drown, something that led to the construction of the Thames Barrier.[1][5] Strummer's concern for police brutality is evident through the lines "We ain't got no swing / Except for the ring of that truncheon thing" as the Metropolitan Police at the time had a truncheon as standard issued equipment. Social criticism also features through references to the effects of casual drug taking: "We ain't got no high / Except for that one with the yellowy eyes". > The lyrics also reflect desperation of the band's situation in 1979 struggling with high debt, without management and arguing with their record label over whether the London Calling album should be a single or double album. The lines referring to "Now don't look to us / Phoney Beatlemania has bitten the dust" reflects the concerns of the band over its situation after the punk rock boom in England had ended in 1977.

Michael Stipe isn't exactly fond of explaining the meaning behind the lyrics of many of his songs but I somehow doubt the song was made to ease the concern of a real future climate catastrophe.

So, in this fictitious world where IRC is a stable protocol and easy enough for the average layperson to use, who pays for the IRC server bills and how?

Yes it is - and it's worthwhile to read bawolffs well written explanation of how exactly it could be exploited. Downplaying security vulnerabilities of this sort is precisely how database leaks happen.

Thanks!

Thank you!

> If you are building a game from scratch why would you limit yourself to a lowest common denominator interface when there's no need? Just write the exact concrete code that needs to be there to solve the problem.

Coming from the realm of someone who has mostly swam in the OO pool their career, I struggle understanding how a concrete implementation of something like a video game wouldn't spiral out of control quickly without significant organization and some amount of abstraction overhead. That said, I have found ECS type systems be so general purpose that you end up doing a lot of things to please the ECS design itself than you do focusing on the implementation.

Do you have any examples of games and/or code that are written in more of a data oriented way? I'd really love to learn more about this approach.

Doesn't happiness exist in the sense that there is a complex set of chemical combinations happening in your brain emitting the feeling of happiness?

I don't think it's quite that cut and dry - it appears to only be using data already available to the player. If anything it seems like a training queue to notice the information that's already present instead of passing it over.

JSX (React's default markup language) expects all tags to be closed, and self closing tags are valid. If you spend a significant time writing React apps (with JSX) then it becomes pretty second nature to write self closing tags. It's not exactly XHTML (I can't think of any other of XHTML's idioms it uses).

I can't think of a single website that has prompted me to sign up for desktop notifications that I've ever wanted desktop notifications for.

My argument isn't really a "good guy" Apple argument but more of an observation of the current kidnapped state of the web RFC's.

"Coding around it" means handling an additional error state, which can be in varying degrees of complexity depending on what the feature is doing for your app.