bitfucker @ bitfucker @programming.dev

Posts

1

Comments

425

Joined

1 yr. ago

I hope the rotten coconut is not from accumulated nut

Transferring ownership of the account also transfers the game license owned by the account. Still upset publisher

Gay field... A word I never imagined will encounter in my life

Shame. It would be a good way to know if you are their favorite child lol. All joking aside, I think this is a compromise as others have alluded deep in comments. Valve likely doesn't care or enforce it, but they don't want to be responsible for account transfer due to games licensing and other legal shenanigans.

I didn't specifically comment on GNOME ma dude. Just the other commenter that said most people don't want choice. I think it's not "choice" but it should be "choose". Having to choose can indeed become confusing, so there should be a default or pre chosen choice. Having no choice means you are locked in. Hence my comment. I am having no problem with people not wanting to choose, but people that do not want a choice is when I am starting to have a problem.

What the fuck are you talking about? Do you think the license being used is not legally binding? What constitutes as legally binding to you?

If they don't want to choose, that's fine by me. But why tf they didn't want choice? They could just stick to whatever is the default and let others who wanted different choice have their way.

One small bug in implementation can make it a juicy attack vector. Sure you can configure it to give more privacy, but how many users will do such configuration? Many casual user didn't even bother changing their user/computer name (how many times have you seen the user named "user", "asus", or any other default?)

I think you can start a figma or other collaborative UI/UX as an idea first. If a developer is interested in implementing it, then you move on to the next feature

Gold test

"What if the test fail?"

*Write a test for the test

I doubt you pay a doctor for him to say something you want to hear

Yep, this is more in line with what I expect as a steam deck competitor. We'll just see if they can provide more value to customers than steam while also making good hardware to support it.

I am remembering the horse armor DLC lol

No, MSI or ASUS or really any other hardware company (that primarily sells hardware) makes money from selling hardware. Valve main source of income is their steam service, not the deck. For any deck they sold, they could make a loss but they gain revenue by a first time gamer. Much like how console can be sold at a loss but making the profit from the game they sold. The primary difference between traditional console and steam deck is that any hardware competitor to steam deck is still a win for valve since they also mostly profit from sales on their steam service. Thus my point, any hardware company is not valve primary rival since if a consumer chose steam deck, valve wins, but if they chose the competitor, valve wins too. Epic, Ubisoft, and EA or whoever else that tries to provide the same service like valve should be their primary competitor.

Edit: my point being, the deck doesn't need to be faster, or more power efficient, or more ergonomic. They just need to popularize the form factor. The fact that valve makes the deck so awesome on release, only to be overtaken by another hardware is not a loss for valve.

Wasn't it skyrim?

To be honest, any hardware company can't really compete with valve toe to toe since valves can cut cost and sell at a loss. But I am interested in how the so-called steam competitor would make the same handheld device. I'm waiting for you Tim Epic.

Yes, and hence my comment on flatpak which turns out is false (that the upstream developer is usually the distributor/packager too). And the other still applies, distro usually adds a specific tag anyway for their refresh. Like that one time xz on rolling debian was named something x.y.z-really-a.b.c.

I think flatpak packagers should also append the specific tag too if that is the case. Like, x.y.z-flatpak-w where w can be the build release version