chaorace

joined 1 year ago
[–] chaorace@lemmy.sdf.org 6 points 9 months ago* (last edited 9 months ago)

I took his criticisms of the combat as basically saying "this system is not interesting enough to form a satisfying gameplay loop". That's a critical statement which I actually agree with, though from my perspective that's a key part of Persona's core design: neither the combat system nor the social link system are endlessly enjoyable, so the player is intrinsically motivated to avoid lingering for too long and properly close the core gameplay loop by advancing the calendar. It's that sort of pendulum-like cadence which gives the series its unique sense of momentum.

I do think that it's a shame RPS's Matt was unable to find joy in P3R's gameplay loop due to disliking the social-link system... but I also see it as an opportunity to better understand the game as a holistic package in a way that can't be achieved through a more carefully measured, quantitative analysis. The way I see things, the game is the game -- I'm much more interested in understanding what's in the game rather than what's not, if that makes any sense.

[–] chaorace@lemmy.sdf.org 9 points 9 months ago* (last edited 9 months ago) (3 children)

I tend to prefer clicking through the unscored reviews first since I find that it's generally a mark of a quality outlet. Rock Paper Shotgun in particular is an old favorite of mine, so their's is the first review that I clicked on and let me tell you guys: it's a real firecracker!

Matt clearly didn't have a good time and I had to respectfully disagree with a lot of the points he's made, but even so... his points are well-articulated and sensible. I'm rather glad for his uncommon perspective on the topic and I do think that RPS ultimately picked the right writer for the job. He hasn't particularly changed my mind about a day-one purchase, of course -- the main difference is now I'll have a more nuanced and realistic expectation for what's inside.

[–] chaorace@lemmy.sdf.org 17 points 9 months ago* (last edited 9 months ago) (1 children)

It's a pretty different situation under closer examination. The DnD developers are ex-Nexon employees and they (allegedly) pitched the idea internally before deciding to leave and take the idea with them.

Nexon thought that they had a legal leg to stand on because of how IP laws work (i.e.: employee ideas on company time are company IP). Perhaps more importantly; they probably felt a need to retaliate in order to send a message to other employees who might want to try something similar.

Palworld, on the other hand, is made by a team with no ties whatsoever to GameFreak. If Pokemon were a younger franchise they might possibly have a patent case of some kind, but even the 3D games go back almost 24 years now.

[–] chaorace@lemmy.sdf.org 15 points 9 months ago (7 children)

You may be interested in reading this post about the process of packaging Steam.

tl;dr: It's mostly an annoyance reserved for packagers to deal with. Dynamically linked executables can be patched in a fairly universal fashion to work without FHS, so that's the go-to approach. If the executable is statically linked, the package may have to ship a source patch instead. If the executable is statically linked & close-source, the packagers are forced to resort to simulating an FHS environment via chroot.

[–] chaorace@lemmy.sdf.org 8 points 9 months ago* (last edited 9 months ago)

Ah, yes, just over five attempts for every human alive. I assume they took the reply addresses at face value and have forwarded 45 billion cease & desist letters to Microsoft's Redmond office?

[–] chaorace@lemmy.sdf.org 1 points 9 months ago

Could have been MMANAA 😔

[–] chaorace@lemmy.sdf.org 14 points 9 months ago* (last edited 9 months ago)

If you hate job boards then you need to find individual company "Careers" pages and go from there.

How you go about this varies a lot by skillset and industry, but I'll just throw out a random example: lots of Linux jobs exist in the DevOps space (think Kubernetes, Ansible, Chef, NixOps). It just so happens that lots of medium-sized software companies need DevOps people, so you can pretty easily find companies looking for DevOps hires just by browsing Y Combinator's Startup Directory

With that being said, I get the impression from the way your post is worded that you're looking to break into a new career without having yet established a concrete plan. My advice would be to step back and consider specific options first. Almost all jobs like these require industry-specific certifications (e.g.: CompTIA, ITIL, AWS, Azure, Cisco, etc.). You need to look at your options, pick a certification, earn it, then go job hunting. Certifications are great for securing entry level jobs and the standards body issuing these will often provide an online directory of partner companies who are currently hiring.

[–] chaorace@lemmy.sdf.org 0 points 9 months ago (1 children)

You'll understand when you're older, son

[–] chaorace@lemmy.sdf.org 1 points 9 months ago (1 children)

Ugh... they got Plasma everywhere!

[–] chaorace@lemmy.sdf.org 1 points 10 months ago

Try Satty? It's inspired by flameshot, Wayland native, and written in Rust.

[–] chaorace@lemmy.sdf.org 0 points 10 months ago* (last edited 10 months ago) (1 children)

First thing's first: all such adapters should be considered evil by default. The only way to make a compliant adapter is with active circuitry in the adapter essentially providing an entirely standalone USB controller interface.

With that being said, here's an adapter which does exactly that. Back when I researched this topic in October I found that the linked adapter is essentially the only one of its kind on the market right now.

[–] chaorace@lemmy.sdf.org 1 points 10 months ago

I like flakes a lot, speaking as a type of user which I'll call a "casual packager".

This is to say that I like being a good citizen and sharing my packaging efforts... while also simultaneously feeling totally uninterested in becoming an owner-for-life. Flakes let me share a package without those pesky strings -- when the user installs a package using one of my flakes, a personal lockfile gets generated at the latest git commit and that's that. If the user doesn't like the version they get, then the power is in their hands to choose a different git ref via their own generated lockfile.

Obviously this is something of a user footgun, especially for consumers of high-impact or security-critical applications, but most of those things are already important enough to get packaged. When it comes to niche, infrequently updated stuff, this approach works super well and helps to draw many reluctant packagers like myself out into the open.

view more: next ›