I really hope the integration with QubesOS[1] will be completed in the near future. It will allow to run suspicious legacy Windows software without any hassle. [1] https://github.com/QubesOS/qubes-issues/issues/2809
Yeh that would be awesome
ReactOS Updates
41–50 of 142 posts
Re: ReactOS Updates
#42When I followed this link via Chrome, a tool tip popped out of my address bar ("Did you mean reactjs.org?" with some warning about attackers using deceptive URLs). I wonder if there's a way to whitelist URLs with Google to prevent users from seeing this message. Especially since I believe ReactOS has been around long before ReactJS
>Especially since I believe ReactOS has been around long before ReactJS
Well, you just reiterated that ReactJS is newer and newer is always better. /s
Re: ReactOS Updates
#43Earlier quoted context omitted.
On the contrary, I'm sad to see them moving towards "slack clone" solutions rather than sticking with simple chat, a la IRC. I don't think adding stickers and emoticons to a conversation makes it any better.
Emoticons absolutely make it better, just by saving chat traffic for simple acknowledgements. Emoticons are also used as a simple way to poll, which is very useful.
But they're annoying to type. I never end up using them because I'd have to go look up the icon for something, then copy and paste. I think phones have keyboard features or something, but I actively avoid typing messages from a phone because it's so slow. This represents another move towards "mobile-first" stuff, which I generally dislike.
Re: ReactOS Updates
#44ReacOS is a testament to how solid were Windows 2000/XP's UI for everyday tasks. I wouldn't mind being back in a Windows env/shop with ReactOS.
I think you might enjoy Xfce from the GNU/Linux world.
Re: ReactOS Updates
#45ReacOS is a testament to how solid were Windows 2000/XP's UI for everyday tasks. I wouldn't mind being back in a Windows env/shop with ReactOS.
I think you might enjoy Xfce from the GNU/Linux world.
Can confirm, I loved windows 2000 UI and I'm now using XFCE. XFCE is of course better, just sad there is not more maintainers for it.
Re: ReactOS Updates
#46Earlier quoted context omitted.
Emoticons absolutely make it better, just by saving chat traffic for simple acknowledgements. Emoticons are also used as a simple way to poll, which is very useful.
But they're annoying to type. I never end up using them because I'd have to go look up the icon for something, then copy and paste. I think phones have keyboard features or something, but I actively avoid typing messages from a phone because it's so slow. This represents another move towards "mobile-first" stuff, which I generally dislike.
You are entitled to your preferences, but let's not dismiss actual practical advantages of emoticon support in Slack-likes compared to IRC. I agree it has costs as well as benefits, but dismissing the real benefit is a bad manner.
Re: ReactOS Updates
#47The way Microsoft is moving, it's feasible to think that Windows 2000/XP will be open sourced before ReactOS is finished.
Wasn't the code for XP leaked a while ago? Could the ReactOS developers learn how things work from it?
Re: ReactOS Updates
#48Earlier quoted context omitted.
This is false. There was an issue when there was a leak of windows source code to the internet, and ReactOS effectively had to shut down development for months while all code was audited to make sure no helpful folks had used any of it to 'help' the project. That's the only MS IP controversy they've been involved in (and I've been watching the project for waaaay too many years now) (That issue answer reads like someo…
The specific issue is;: > Many internal data structures and internal functions, not exported anywhere and not part of the public symbols, have the exact same names as they appear in the Research Kernel (which, by the way, is quite obsolete). There is an almost surely zero probability that this happened, at that scale, by accident. Unfortunately I don’t think anyone who doesn’t have access to the research kernel is ca…
Even if someone had access to compare it, I wouldn't put the probability at 0. Windows has a pretty specific way of naming types, fields and functions. Some of those leak through error messages and other methods of introspection. They're have to match on a few very esoteric private fields to support that argument.
Re: ReactOS Updates
#49The way Microsoft is moving, it's feasible to think that Windows 2000/XP will be open sourced before ReactOS is finished.
Wasn't the code for XP leaked a while ago? Could the ReactOS developers learn how things work from it?
Quite the opposite, any developer that so much as glances at the leaked source code is banned from the project. The legality of ReactOS rests upon its developers reverse engineering Windows without having access to the source code.
Re: ReactOS Updates
#50The way Microsoft is moving, it's feasible to think that Windows 2000/XP will be open sourced before ReactOS is finished.
Wasn't the code for XP leaked a while ago? Could the ReactOS developers learn how things work from it?
I forget the details, but generally, no. They want a clean room implementation, so if you've seen the code, you might even unconsciously copy it. They've taken license matters very seriously, so ReactOS devs would probably actively avoid looking at the code for the legal safety of the project.