Hacker Newsnew | past | comments | ask | show | jobs | submit | branneman's commentslogin

Why no MacOS support if you claim cross-platform? That's not honest.


It's still cross platform, just across Linux and Windows, doesn't look dishonest. It's similar to other "linux/macos"-only tools that also call themselves cross platform.

The baffling part though is recommending using homebrew to install it on linux.


> The baffling part though is recommending using homebrew to install it on linux.

Do they really? Probably AI-generated.


April Fools I guess, considering the actual commit content:

- many -> persony

- helps -> theylps

- here -> theyre

- historical -> theirstorical


Buggy bot, looks like a college student trying to help but not fully testing.


this was happening before april fools


Yes. Exactly this.


Agreed. But why choose if it's easy to add an idiomatic pure-JavaScript/EcmaScript 2021 implementation to compare with as well?


Now find some sources to cite with that timeline, and create a wikipedia article from it!


Well, that is the point of software, to change quicker and cheaper.


Doesn't mean you should do things wrong in hardware.



In that case, way I ask why you are not a Racket user? Sounds like it'll save you a ton of time and keep your implementations high level.


When should one use Ohm over Racket?


When they want a library and toolkit for building parsers and languages, rather than a general programming language based on Scheme.


So, I guess you don't know why OP specifically asked about Racket: https://www.cs.utah.edu/plt/dagstuhl19/ https://beautifulracket.com/stacker/why-make-languages.html


Nah, I know about Racket's DSL support and touting itself as friengly to language writing, but it's still not the same as a dedicated parsing toolkit, the same way I wouldn't consider a Lisp with reader macros equivalent either...


... but racket basically exists to create parsers and languages. It happens to also be a general programming language. But so is JS nowadays with Node.


How is Proton a technology/library/sorftware? I got the impression it's just a preconfigured Wine, but not an actual implementation. Sorry if I'm misinformed.

And _if_ that's true, I'm sad about the credits not going to the Wine team.


Proton is Wine + DXVK + d9VK + custom patches.

The 'secret sauce' is actually 'Steam Play' which is the automated wrapping, configuration and execution of Proton wrapped games without the user having to do anything (other than a confirmation box to confirm that a compatibility layer is being used).

The Steam Play component turns it from a 'nice meta-distribution for wine' into 'killer quality of life improvement'.


How much of this is open source? I'd expect everything, including the per-game details?

(Not asking you to do research on demand, just in case you already know...)


Not sure about the per-game config, but the Proton is definitely open source [0], as are DXVK [1] and D9VK [2].

Steam Play is part of the Steam client, so is proprietary. ProtonDB isn't open source but does data dumps to github regularly [3].

[0] https://github.com/ValveSoftware/Proton/

[1] https://github.com/doitsujin/dxvk

[2] https://github.com/Joshua-Ashton/d9vk

[3] https://github.com/bdefore/protondb-data


Thanks!

I guess it somehow makes sense for Valve to keep the per-game tweaks private. With all of that money they're printing though, I sure wish they could feel that they could afford to be less defensive.


None of it is private. The per-game settings are all listed here, the options are all implemented in Proton, which is completely open source: https://steamdb.info/app/891390/info/


That's very nice.

I think this will make game preservation easier in the near future.


If it helps, Lutris has config for most games that are open source and available.

https://lutris.net/


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: