to learn vulkan every time they want to use a GUI for their job
Not every time, just the first time. But yes. Devs should stop being so lazy
compiler design whenever they wanna use java for their job
Every dev should at least know the basics of language design and compiler design, yes. Again, you also only have to learn it once
I've really fallen in love with the Iced framework lately. It just clicks.
A modified version of it is what System76 is using for the new COSMIC DE
So no 2XKO? :(
I was so excited
I would really prefer native if there is the opportunity
I prefer native apps too, but I'll still use websites and some electron apps, and I'll still use applications built in C#, Java, Python, etc. None of those are really native either. Proton is analogous to a virtual environment for running an interpreter. Potentially, it's slower and has issues a la Python, but if the program can work, then I don't care about the theoretical problems; it works despite them. So I think it's fine.
If it means more games for Linux and a standard that developers can target, encouraging them to "support Linux," then that's a win I think. Like I said in another comment, a studio can buy a steam deck, throw the same Windows export on it, and then have someone run through the same set of tests they'd normally go through. If it works there, it'll work on most Linux machines. Having a standard API is not a bad thing imo
The way I like to think about it is that Proton essentially provides a standard, stable API across both Windows and Linux for gaming (Win32). We typically talk about it as a translation layer, and it is, but also to some degree it's also "here's an implementation of Win32 for Linux."
If game devs can, say, buy a steam deck and know their game works on it, that means it's gonna work on other steam decks and probably most Linux machines. It's making it easy for devs to test and develop for Linux, even if it's not really "on Linux." Copy the Windows files to the steam deck, run your release checklist, and you're good to go.
In Rust and Haskell you have to at least annotate the parameter types and return type of functions.
In OCaml type inference is a lot more powerful: you don’t have to annotate function signatures
Actually, Haskell and OCaml have this in common. Only Rust requires parameter types of the three.
I could do
add2 a b = a + b
main = do
putStrLn $ "5 + 3 = " ++ (show $ add2 5 3)
And that would work
And?
Seems really difficult to learn/switch to
People need to learn to be careful