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

What does Rust have to do with it? You can write MIT or GPL licensed code in any language.


It's not the language selection, but the license selection what bothers many.


This is a bad idea. You can make Linux look like Windows on the surface but people are going to then be surprised and frustrated when it doesn't act like Windows, it will come off as cheap imitation. People get confused about the idea of something as simple as the concept of a single root file system, they will not understand that coming from a world of C, D, and E drives. It's best to make it look foreign to them so that they don't have their expectations subverted when they realize it actually is a fundamentally different operating system.


I wish it would get LSP support. There are some plugins but they seem buggy/ incomplete/ abandoned. It could be a nice lightweight alternative to VSCode.


I'm surprised no one's mentioned Virtualization-based security in this thread. I suspect this is responsible for a big part of the gap.

https://www.tomshardware.com/news/windows-vbs-harms-performa...


What are these APIs? Why isn't this possible on standard cross platform graphics APIs?

Edit: I guess it's probably this sort of thing https://learn.microsoft.com/en-us/windows/win32/directcomp/a...


On the Mac, it's the Core Animation layers API.


What do you mean by this? Rust has multiple game engines that support hot reloading and/ or scripting.

https://fyrox-book.github.io/beginning/hot_reloading.html

https://github.com/jarkonik/bevy_scriptum


This the bare minimum, https://liveplusplus.tech/

Also supports is kind of relative,

"CHR is very new and experimental feature of the engine, it is based on wildly unsafe functionality which could result in memory corruption, subtle bugs, etc."


Why is that the bare minimum?

I also think that doc page is a little old. The feature is over 2 years old now and hot reloading is inherently "unsafe" in any compiled language. It's just letting you know that Rust's safety guarantees might go out the window if there are bugs in the code that handles hot-reloading.


Because that is what existing game studios expect, as shown by their customer list.

Also that was only one example, there are other similar ones.


Funnily enough, Mojang is on that list, and I remember recently watching a video[1] of Notch hot-reloading code while developing Minecraft, except it was with Java and I'm sure he didn't pay a dime for the ability to do that.

[1] - https://youtu.be/BES9EKK4Aw4


That live reload probably already works with Rust — they say they don't parse any source code, and instead analyze the compiled binary and debug info.


On my laptop there is a noticeable keystroke delay compared to other editors.


Bandcamp and RYM.


It opened instantly and worked smoothly in Firefox on my 8 year old android.


Yes, on my phone it's fine but on my laptop it's a nightmare.


The code generation is certainly a build step. This kind of code generation is common for interfaces defined outside of a project's programming language.


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

Search: