ReactOS releases 0.4.8 with experimental Vista/7/10 software compatibility
1–10 of 318 posts
Re: ReactOS releases 0.4.8 with experimental Vista/7/10 software compatibility
#2Re: ReactOS releases 0.4.8 with experimental Vista/7/10 software compatibility
#3Re: ReactOS releases 0.4.8 with experimental Vista/7/10 software compatibility
#4Re: ReactOS releases 0.4.8 with experimental Vista/7/10 software compatibility
#5I think their site is getting the HN hug of death, loads extremely slow/doesn't load at all...
Re: ReactOS releases 0.4.8 with experimental Vista/7/10 software compatibility
#6One of the most interesting changelog that I have read in a While. Well written, thoughtful and gave me good insight into the project.
> Talking about the notification tray, due to Ged’s work, icons of killed and finished process are now automatically removed, even when apps crash. This is something that Windows doesn't even provide with Win10, and many Windows users may have noticed.
Made me chuckle. This has bothered me since forever. It seemed like such a low hanging fruit to fix, I wonder why Microsoft never did.
Re: ReactOS releases 0.4.8 with experimental Vista/7/10 software compatibility
#7One of the most interesting changelog that I have read in a While. Well written, thoughtful and gave me good insight into the project.
Re: ReactOS releases 0.4.8 with experimental Vista/7/10 software compatibility
#8Re: ReactOS releases 0.4.8 with experimental Vista/7/10 software compatibility
#9One of the most interesting changelog that I have read in a While. Well written, thoughtful and gave me good insight into the project.
Indeed a great read to catch up with the project. > Talking about the notification tray, due to Ged’s work, icons of killed and finished process are now automatically removed, even when apps crash. This is something that Windows doesn't even provide with Win10, and many Windows users may have noticed. Made me chuckle. This has bothered me since forever. It seemed like such a low hanging fruit to fix, I wonder why Mic…
I'm assuming it's because of the size of the codebase, available engineering resources, return-on-investment calculation, and a business prioritization of new features over refinement.
Most engineers can look at their own work or codebase and think, "well, that's a bit shit but it works well enough." I can't imagine their backlog. I'm sure it's lurking in an issue queue somewhere.