Quoting: qptain Nemo[...]

Quoting: CybolicI'm curious about you mentioning that you prefer the prefix management in POL; I always found it incredibly confusing. In Vineyard, the prefix is meant to be the top-level interface and everything you do happens under that. How does POL differ and what are the benefits?

Let's see.
Creation:

• creating a new prefix is pretty much the same, if you don't count the fact that POL lets you download different wine versions in advance and easily create fresh prefixes with any wine version it provides; whether it's a "fair" comparison or not in practical usage it's a huge advantage for when you need to test a lot of things under different configurations

Management:

• POL has a button for opening winecfg for a given prefix (technically, vineyard does include pretty much every setting from there though...)


• POL offers more installers of various system components


• you can switch the wine version after creating a prefix as much a you want as well as easily get additional wine versions as they're needed

I absolutely agree though that the whole UI presentation paradigm of Vineyard is much more straightforward, you actually need to go to the settings window of POL to get to all those tools, but in terms of practicality some of those advantages are significant especially in scenarios where rapid creation and testing of prefixes and experimentation are needed. I guess the biggest one here is the ability to download and switch between wine versions. This feature is incredibly helpful in both Lutris and POL.

Oh yes, I absolutely agree! I've often wanted to add the Wine version handling that POL has, but the choice is either to create my own repo of Wine versions and duplicate the work they've already done (which seems a waste of resources and yet another split effort) or download directly from their repo (and steal their bandwidth, essentially). It's the same thing with Lutris' handling of DXVK and a bit of a rock-and-a-hard-place situation all in all.
This would probably be the perfect example of somewhere we should really be working together though; maybe something will happen eventually, but currently, the only solution I can offer is that Vineyard does let you use Wine versions that you've already downloaded in POL.
As for the other points (for Vineyard at least), that's the result of me just not having enough free time these days to add installers and new options :(

Thanks for the dialogue, I think you're on to something here ;)

View this comment - View article - View full comments

Quoting: qptain Nemo

Quoting: CybolicWhile it's always nice to see more development on user-focused Wine tools, I wish that PlayOnLinux would focus more on uniting the field instead of doing their own thing again. Using Java is one thing, but coming up with yet another install script framework - in a different scripting language from what's generally considered the standard for these thing - isn't really helping build a solid, widely usable pool of install scripts. We already have Winetricks and Lutris (both of which use Bash shell scripts), I really don't see how adding JavaScript to the mix will help.

Disclaimer: I wrote Vineyard so I'm fairly biased ;)

I can't express how much I wish Lutris, POL and Vineyard somehow joined forces.
POL has great prefix management tools.
Vineyard has a great set of useful options for running stuff.
Lutris has another great set of useful options for running stuff.

It's amazing but also so, so frustrating. A tool that contains all options from both Lutris and Vineyard and has prefix management capabilities of POL would absolutely rock. I'd sorta prefer that unification happened under the Lutris umbrella but I don't want it to be a matter of contention.

There have been talks about joining forces previously, which mostly amounted to settling on how prefixes are handled (generally, and at least in Winetricks, Vineyard and Lutris; POL is doing its own thing there as well), but apart from that, I think a lot of the separation of work comes from having different end goals.
Lutris aims to be a generic frontend for game emulation/handling.
POL aims to be a Wine-focused frontend game handling.
Vineyard aims to be a generic frontend for anything related to Wine.

I'm curious about you mentioning that you prefer the prefix management in POL; I always found it incredibly confusing. In Vineyard, the prefix is meant to be the top-level interface and everything you do happens under that. How does POL differ and what are the benefits?

View this comment - View article - View full comments

While it's always nice to see more development on user-focused Wine tools, I wish that PlayOnLinux would focus more on uniting the field instead of doing their own thing again. Using Java is one thing, but coming up with yet another install script framework - in a different scripting language from what's generally considered the standard for these thing - isn't really helping build a solid, widely usable pool of install scripts. We already have Winetricks and Lutris (both of which use Bash shell scripts), I really don't see how adding JavaScript to the mix will help.

Disclaimer: I wrote Vineyard so I'm fairly biased ;)

View this comment - View article - View full comments

Quick note: You've get the Steam link filter on the SoundCloud link ;) Fixed

Also, Distance is a fantastic game.

View this comment - View article - View full comments

Steam link to We Were Here Too: https://store.steampowered.com/app/677160/We_Were_Here_Too/ [External Link]

View this comment - View article - View full comments

For anyone curious about what languages they might learn from it:

The official languages are Arabic Mandarin Chinese, French, Japanese, German, Russian and Spanish. You'll be able to learn these languages in English, or learn English in any one of the official languages. There are also many languages that have been partially translated by the community.

At the moment, these are:

Basque (32%), Croatian (72%), Czech (33%), Danish (40%), Dutch (100%), Esperanto (99%), Estonian (41%), Greek (33%), Hungarian (35%), Icelandic (100%), Indonesian (48%), Italian (64%), Lithuanian (33%), Norwegian (98%), Polish (90%), Portuguese (PT -44% and BR -90%), Romanian (37%, Slovak (33%), Sranan Tongo (36%), Swedish (87%), Turkish (49%), Vietnamese (62%) and Westrobothnian (30%).

The number refers to the percentage of content that these languages have translations for.

View this comment - View article - View full comments

If that box had a Tux logo next to the IBM one, I'd be tempted to pick this up and place it next to my Quake: The Offering box :D

View this comment - View article - View full comments

Quoting: liamdaweThey responded further, with 75% of sales actually being on console.

So Linux is 15% of 25% of 20,000. So the Linux percentage was good, but that does mean it sold poorly on Steam. Will issue an update when i'm at my PC.

I read it as 15% of total sales being Linux (3,000 copies) and 25% of total sales being on Steam (5,000 copies), which are mighty impressive numbers (60% being Linux sales).

Guess it depends on whether one reads "about 15% of our players so far have been Linux users on Steam!" as written or as "on Steam, about 15% of our players so far have been Linux users!" - can't say for sure which one they really meant.

View this comment - View article - View full comments

I'm sorry for the irrelevant comment, but look at those little T-Rex feet go! It looks like a toddler trying to run; adorable :D

View this comment - View article - View full comments

The most logical speculation I've heard as to why on earth Microsoft would want GitHub is the idea that they might link it to their other recent acquisition, LinkedIn. Doing so would let them compete with the more programmer-focused job sites out there.

I'm not sure whether I'll start migrating my projects just yet, but new ones are likely going on GitLab.

View this comment - View article - View full comments