I love how people watching me talk and mentioning my age or calling me a millennial straight up assume I wasn’t around when PHP, ASP .NET, or even XSLT were hype. I’m not deeply familiar with them because I mostly did desktop but I started early so I’ve seen a few things. 🙂
Here’s a challenge. When I want to tweet “X is just like Y back in the olden days” I try adding “but...” and figure out what the difference is. If I thought of a past analogy after one minute of thinking, clearly I’m not the first one to think this, and there might be more to it.
It’s easy to see the past references. They stand out, and there’s a limited number of variables to play with in the design. Some things will repeat. It’s harder to notice the new twist. Which can turn a past weakness into strength or solve a limitation.
Like, ASP .NET WebForms wasn’t good, but do you know *why* it wasn’t good? If your takeaway is that XML is bad or that any technology spanning both the server and the client is bad, you might want to jog your memory and dig for nuance.
There’s also an interesting area of “almost good” ideas. Where something is actually pretty good but some other flaw caused it to work poorly. People only remember it in conjunction with the flaw and have a knee-jerk reaction with a different take on the same thing.
Finally, uh, you don’t have to be born in a certain time or have a computer at a certain age, to contribute to the discussion. If you’re working on something new it would be a jerk move from me to assume you haven’t spent some time learning about prior art. Extend that courtesy.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I was thinking about the sentiment you might see when something new is introduced. “Oh no, another thing to learn, why can’t we stop.”
And while I get the frustration I also wonder. Are there people who genuinely expect that they’ll be able to stop learning in this field?
Like, another JS library. Of course there is. Why wouldn’t there be? I would be concerned if there are no new ideas being tried. What did you expect, that there’s a limited number of things to learn and then you’re done for the rest of your career? That’s not how it works.
I think maybe the sentiment here may actually be directed against inexperienced project leads. Who might be overly tempted to jump between solutions and impose new things on their team. That can be frustrating.
Crash 4 time squeeze gameplay is really addictive. Digging it. Like the visual style too. My only gripe is the shadow — I get that it helps placement but it almost feels like a cop-out so that the games can’t blame the collision system. “You saw where you landed!”
I so DON’T miss the “four lives and then you have to restart” mechanic. Glad they cut it.
So many subtle touches. Keeping some mechanics like you can smash a box with tnt above it. But doing away with annoying things like accidentally spinning wumpas.
I wonder if our early messaging about Concurrent Mode should have been focused on mounts rather than updates. Some of the conversation I’m seeing assumes we could just “do less work” which is not an option for rendering *new* subscreens — where granular rerendering doesn’t help.
This depends on the app — some apps, like dataviz, almost exclusively do “updates”. So dataviz example, while effective visually, may have been a misdirection. In consumer apps a lot of the interactions we want to make smoother are mounts — like switching tabs or infinite scroll.
There’s also a question of responsibility. We consider what happens when you have hundreds of components that all run a little bit of code *our* responsibility. Userland code then dwarves library overhead in CPU time. We can’t just wash our hands and say “don’t write slow code”.
Omg. I found the AIDS awareness ad that was broadcasted on the Russian TV in 90’s. It always freaked me out as a kid but it’s even creepier now that I understand what it was saying. It’s not what you expect.
Here’s the translation. “The illness known to you as AIDS has destroyed our civilization 10,000 years ago. At first, hundreds died, then thousands, then hundreds of thousands...”
“... When we knew it was too late to fight the disease, we’ve drowned our continent with the rest of the infected to keep it from spreading across the planet. But we’ve miscalculated. Ten thousand years later, the deadly virus threatens the humanity again... “
Hi @codility, would you mind removing my name from your job ads? I don’t think this is very funny
I don’t find it “offensive”, it’s just alienating. It reeks of hero worship which is already a huge problem in JS community. I get that it’s meant as a joke but it acts as a “culture fit” filter similar to “you need to like partying :-)”. I don’t want to be a part of that.
Ultimately it’s not my problem that they alienate people who are not on Twitter (cause they have better things to do) or who intentionally don’t follow me (because they’re tired of seeing my shitposts). But I don’t want to be associated with that either.
Tutorial: implementing undo/redo is so easy with immutability! You take the previous states and put them in an array and then you can
Reality: color picker putting every intermediate change into history as you drag the cursor is probably not quite what you intended
Tutorial: oh this is easy, you just snapshot only at important times, like when
Reality: good luck deciding when to snapshot your state, before the user has committed their action or after the action has already destroyed the previous state you were supposed to snapshot
This is not to throw shade at immutability. I know it's trying its best and I'm thankful for that