ervine

Workers & Resources: Soviet Republic! That's actually the best one available if you're more interested in the simulation than the aesthetics, even with the jank.

Man Forza Motorsports and Cities Skylines 2 came out within two weeks of each other, and I was so pumped for both. Thinking I'd have two genre-defining games to enjoy for years, it was definitely the most disappointing month of gaming for me.

As a comment on the article: yes, of course - the lack of all the things are symptoms of "this must release now". They fumbled it so badly, a new developer got put on it.

Ah! Well, enjoying a MUD is still a great shared experience haha. Nothing like them since. I still gravitate to punishing games with obscure mechanics and steep learning curves, and I imagine I'm still chasing that MUD high.

I think what made them special was that they were populated by others that put in that effort, and so the community felt invested. And you'd see the same names every time you logged on cause there was a single server, and reputation mattered. Ah man, what a time of life haha.

I'm sure you mean wotmud.org, and I always look for someone to mention this one in MUD threads, but rarely see it.

Man I was hooked on that game in high school. Joined the Lion Wardens, multiple high level characters, knew the zones. Nothing has come close since then.

That feeling of leveling in a safe zone when your screen fills with red names of opposing faction characters and you just get deleted and lose all your gear and a level... so good.

Yes! Everything else aside, whatever you think of its output and value, shipping largely AI-coded features now doesn't really give me the satisfaction that putting things together myself used to.

I'll just have to move up a level of abstraction to get that same feeling, I guess.

None of this has been my experience.

Not scientific but I enjoy actually going somewhere. Jogging you can get to places in your neighborhood, but cycling I can get to places in my region.

That’s why I get on the bike, you’re moving through areas slowly enough to enjoy them but quickly enough to really take in a lot.

I think it’s just a Lance joke - cycling has no correlation with TC.

Nah, they’re freaks.

My love of cycling in every form is one of the greatest gifts my dad gave to me. I wish everyone was so lucky to find an activity they were obsessed with that has only upsides.

So much North American rhetoric is focused on hatred of the cyclist - while that bums me out, what bums me out even more is that all the haters are missing out on the wonderful world of cycling. Commuter, road, gravel, mountain, track, indoor, fixed, single speed, folding, electric, uni, cargo, whatever.

I'm gonna go ride now.

What's a libertarians take on how health care should work? Completely privatized, completely socialized, somewhere in between?

> No one understands TanStack. Sorry to break it to you.

Damn, all these years of using TanStack libs successfully, and I had to learn it here that I don't understand them.

No, writing shit in react is gonna be a nightmare regardless of paradigm. HoC, Class Components, render props, whatever - if you don't know what you're doing and react internals are magic to you, it's game over. Anyway, we can agree to disagree on hooks vs. classes. Cheers.

I guess I think it's table stakes to need to deeply understand how the framework you're using works. Lifecycle methods vs. hooks, you still gotta know what's doing what and why.

So your argument is that instead of explicit class component methods, hooks are implicit based on understanding the react rendering model?

I guess so - but react could also change (and I think did at some point) how their class methods work, how often they're triggered, and when.

I don't understand the stateless comment - hooks are as stateful as you make them, using useState or useContext or any of the other ways of maintaining data between renders.

I think we're just gonna agree to disagree. Cheers.

It wasn't OOP hate, it was hatred of splitting functionality across a number of methods rather than putting it in a single (reusable, sharable!) hook and having your component consume it.

You can write spaghetti with class components, too. Doesn't sound like a hooks issue to me.

I just don't understand this take, every time I hear it I wonder if people just haven't spent the time to adjust their mental model.

Hooks are IMO the best thing that happened to react.

I didn't realize it was moom giving me my "move app to other monitor" hotkey, and moom didn't launch on startup after upgrading to tahoe. I've been using that hotkey for years.

That's when I realized there's no default hotkey for moving an app to an external monitor. That is absolutely wild. (Happy to be wrong)

This is why I love cycling so much.

Wonder if it's worth squashing in the branch, merging to main, then immediately reverting.

Now the work is visible in history, branch can be deleted, and anyone in the future can search the ticket number or whatever if your commit messages are useful.

Dunno if it's worth polluting history, just thinking out loud.

https://typescript-eslint.io/rules/switch-exhaustiveness-che... if that is something you're not aware of!

You can restructure your JS to avoid some crazy verbose TS though, sometimes. I think that's the point they were making. Why be so hostile?

On the other hand, would we even be talking about it if it hadn't stuck to its goals?

Honestly it's kind of refreshing to just push files to a server.

This feels like a "is a hotdog a sandwich?" situation.

"Is sftp-ing to prod a merge?"

More than one assumption in that sentence, ha!

I guess if it doesn't update the url, it's a button.

If it changes the url, it should be a link. At least that's how I've always done it.

I mean the use of tailwind in the article is not good. Shows a lack of CSS understanding. Why are they applying `text-base` instead of just setting that on the root element? Why are they setting text color on the <a> tag and then overriding it on the <span> inside?

This person would write bad CSS, let's not put the blame on tailwind.

Also so much repetition instead of pulling each breadcrumb link out into a shared component. I understand it's just demo code for an article, but if all code bases end up like this that you've seen, the issue isn't tailwind.