Yeah that 3rd condition means that even if it was a valid license it wouldn't be FLOSS.

View this comment - View article - View full comments

GSC's inaction is puzzling. I could understand them sending take down notices and C&D letters. I could understand them officially sanctioning this project. I could understand them making an official source code release. But doing absolutely nothing? I don't get it.

View this comment - View article - View full comments

Do VP ever do native ports or do they just automatically, instinctly and uncrictically use their eON wrapper

View this comment - View article - View full comments

Quoting: ArehandoroI can't imagine the amount of work and effort the team have put into this. It's amazing and as a future user of xoreos I can't thank you all enough for it. You are the best!

Yeah, it is crazy impressive. Just think of all the programming man hours that went into the original engine and all of the individual games.

View this comment - View article - View full comments

Quoting: Hori

Quoting: WorMzyHere's hoping the dev moves away from using GTK3.

So that we end up with yet another application that doesn't properly or at all respect the system-wide theme that we want to have?
No thanks.

They could get it to work out fine if they basically imitate the official Steam Controller Configurator. In that case, they would keep consistency with Steam (as opposed to the DE theme) which is fine. Actually, in my personal opinion that would be even better.
Of course, people who don't use Steam might disagree... but then again, how many people (if any) are there who use an SC but not the Steam client?

Quoting: Shmerl

Quoting: GuestAh ok, a personal preference thing rather than a technical one.
On a technical level, C is a better choice here, for ease of cross-platform support on something that is lower level and may require kernel interaction. Pretty much everything is going to have a form of libc, and target platforms will have a lot of support (from compilers and build systems, to additional libraries that might be needed) already in C.

It's both and the reason for preference is technical, not simply one of taste. Rust can interact with kernel all the same by the way. Rust does depend on libc at present.

See https://github.com/rust-lang-nursery/portability-wg/issues/13 [External Link]

And an interesting example here: https://github.com/tsgates/rust.ko [External Link]

You all forget that there are waaay more people able to program in C than there are people able to program in Rust. Unless there's a very good improvement from which the application would get a real, noticeable benefit, you'd want to stick with the more popular choice.

"Unless there's a very good improvement from which the application would get a real, noticeable benefit, you'd want to stick with the more popular choice."

On a side note, way too many programmers have a similar attitude towards open APIs like OpenGL and Vulkan and sadly they don't consider cross platform support as a considerable benefit.

View this comment - View article - View full comments

Quoting: kit89

Quoting: liamdawe

Quoting: Guest

Quoting: Xpander

Quoting: liamdaweOuch, another botched release? Was hoping that wouldn't happen after The Witcher 2.

I wonder how they tested it on their systems or did they validate it at all.
I't might be just simple silly thing like missing some files from the build they sent up to steam though..
I wouldnt call this a botched release yet. Lets give them some time. But it worries me that theres even not a single reply from devs/VP to the issue.

Give it another 12 hours. Time zones and all that - VP employees are probably not at work right now. They'll be having a fun day tomorrow though I guess.

Either way it's not a very good look. I am constantly surprised when devs release something and then go home without waiting on reports first.

I would hope they have a life outside of the office, and their company ensures they work the contracted hours, no more no less.

The total amount of hours is one thing. But this issue could be avoided with releases earlier in the work day so that you actually have time to receive(and act on) feedback.

View this comment - View article - View full comments

Virtual Programming is still a thing?

View this comment - View article - View full comments

Quoting: ShmerlThere is some hiccup with DRM-free release, they didn't get GOG to accept the game yet which is surprising.

Interesting. Got a source for that?

View this comment - View article - View full comments

"There have been a number of nuisance bugs, but Oxymoron Games have been releasing patches constantly to fix issues that users discover so they're doing a good job of supporting it so far."

There are some not so good reviews on GOG, have those issues Bern fixed, if so did GOG get the patches?

View this comment - View article - View full comments

Quoting: ElectricPrism

Quoting: GustyGhostMeanwhile on ARK:SE's upcoming features (since 2016) "Linux - Vulkan support". Here's their chance. But we all know that Wildcard will fail to take advantage of it.

AFAIK Ark engine has sufficiently deviated from Unreal 4 Engine so they are basically both 2 different things.

The absolute clusterf _ _ k that has been Ark Engine over the years has showed how development is a un-unified uncordinated rush-fest to graft features on to a unstable core increasing technical debt [External Link].

I wonder what my game dev friends who code in unreal will think of this.

Got any source or further info on the extent and nature of their changes to UE4?

View this comment - View article - View full comments