What I like about it is that I don't need to delve into second hand shopping to get some old classic games.

I've always wanted to get into getting retro games, and I would get different consoles, but as a matter of money and space I've found it difficult unless I get into only one system, and I find the evercade as a compromise for getting a variety of collections from different systems.

Of course, emulating ROMs would give almost the same experience, but the physical releases with their little manual got me.

It's me, or there's an Evercade VS on top of the table? Curious if it's on all versions of the game, or just in this physical edition for Evercade.

And managed democracy!

I'm playing a lot of Helldivers 2 and The Talos Principle 2, and I'm having a great time from both games.

I've bought a bunch of Wadjet Eye games; Unavowed, Gemini Rue, Primordia, Strangeland, Shardlight, Technobabylon and The Excavation of Hob's Barrow.

And aside from that, Return of the Obra Dinn.

I've already played Gemini Rue, and I'm finishing Unavowed.

Curiosity. It began while trying to play around with programming, and finding a lot of talk and resources about Linux, and then trying it. 3 broken Debian installations just for messing around, then Ubuntu as a more permanent install, all of this alongside Windows.

Then I began using less and less Windows until I just deleted the Windows partition because I needed more space.

Alien, that's a game that caught my attention.

And also Aquelarre, is a game set in medieval Spain, where legends and gods are real. The game describes itself as a "Demonic medieval rpg", and their rules are based on BRP, so it's quite familiar on the basics.

The behaviour you mention is from npm install, which will put the same exact version from the package-lock.json, if present. If not it will act as an npm update.

npm update will always update, and rewrite the package-lock.json file with the latest version available that complies with the restrictions defined on the package.json.

I may be wrong but, I think the difference may be that python only has the behaviour that package-lock.json offer, but not the package.json, which allows the developer to put constraints on which is the max/min version allowed to install.

Finnished Call of Cthulhu the past week, finally finished Prey this one (I've abandoned it for about a year), and between all of this I'm playing Baldur's Gate 3. Now I want to play again the System Shock remake, I'm far in the game and I think I can finish it without much time.

Dead Cells is a game I always have installed just to pick it up in bursts of 30 minutes or an hour.

It's a roguelike, it's challenging and it's easy to pick up any time.

Even though it has levels, the intended way to play it is in runs. You start the game, start a new run, and try to go as far as you can, you die and repeat.

Multiple paths to choose, so it never becomes boring, and the levels are generated, so you can't memorize everything.

It seems they consider themselves complimentary with OpenStreetMap, as stated on their FAQ https://overturemaps.org/resources/faq/#

Overture is a data-centric map project, not a community of individual map editors. Therefore, Overture is intended to be complementary to OSM. We combine OSM with other sources to produce new open map data sets. Overture data will be available for use by the OpenStreetMap community under compatible open data licenses. Overture members are encouraged to contribute to OSM directly.

I don't know a lot about any of both projects, but it seems fair.

I've always felt that pair programming is more useful on early stages of a task, where there is enough doubt about implementation details and discussing them is worth.

This way it felt more of a meeting between two persons discussing details first, while testing them live to check if we were on track second, instead of programming first and discussing second.

By the time we stand on the screen without talking too much we just stepped aside and separate the task if needed.

Any other kind of forced pair programming feels wrong, either because the task was already planned enough to no create enough discussion, or because it was small enough and the discussion was not worth. I've found myself on situations where "we needed" to make a task in pair programming and was dull as you say.