Anonymous
why
Edge + IE in a consumer based Win10 ? Sure, it loaded faster, worked all right, but it was lacking security features
Chungy
...wat?
Anonymous
Also, it didn't add a lot of interesting features
Chungy
Microsoft made it very clear that IE11 was included only for compatibility with corp websites and should not really be used on a regular basis. Edge always got the security features.
Anonymous
But then again it should be removed on the next releases as Edge will incorporate a compatibility layer
jamie@
apps depend on it
Chungy
Edge isn't going away dude
jamie@
Edge isn't going away dude
mshtml and edgehtml will be maintained for at least a decade
jamie@
only thing stopping that is MS successfully succeeding NT by something else
Anonymous
Well, the Edge engine isn't used by a lot of stuff
jamie@
UWP apps as a whole
Anonymous
Hence why it's easy enough to move all that to the new Edge with the Chromium Blink engine
✝️ ☺️🌞 HD Scania
Chromium being the basis of Chrome, Brave, Opera, Edge, and a few others.
Falkon, KDE’s flagship browser, based on Chromium too However, Chromium itself and Firefox are GTK browsers, Falkon is Qt5😊
jamie@
MS had a cute WinRT/UWP JS runtime
jamie@
where you could call WinRT APIs just fine
✝️ ☺️🌞 HD Scania
Hence why it's easy enough to move all that to the new Edge with the Chromium Blink engine
Also to take a look on SmartCookieWeb from F-droid😊i need to port that to desktop and get that interfaced using Qt5😃
Anonymous
where you could call WinRT APIs just fine
btw WinRT is also dying, Surface RTs and Windows RT other convertibles are few and far between
jamie@
WinRT is not Windows RT
✝️ ☺️🌞 HD Scania
Nice !
👍😎
Eris
ah yes, the Windows Runtime is dying
Anonymous
WinRT is not Windows RT
Oh you were talking about the UWP stuff
Chungy
to be fair, Microsoft never had good naming schemes
Anonymous
That's not called WinRT anymore
Anonymous
But instead, UWP, to prepare the migration for Windows 10 everywhere
Eris
Anonymous
Which isn't going to happen until one more decade
Chungy
Eris
UWP merely replaces Windows Runtime
Anonymous
UWP merely replaces Windows Runtime
It's almost the same lmao
jamie@
UWP merely replaces Windows Runtime
no, UWP is Windows Runtime
jamie@
lol
jamie@
well, the rebranding of the next version of it
Anonymous
no, UWP is Windows Runtime
I was right once more ! Oof
Eris
Eris
hm
jamie@
I was right once more ! Oof
a broken clock is right twice a day
jamie@
doesn’t mean that it isn’t a broken clock
Eris
I was right once more ! Oof
dont count on your luck
Anonymous
dont count on your luck
Thinking that luck is a thing is stupid at first
jamie@
the UWP bridges are AoW/Astoria and WinObjC
jamie@
the former is dead
jamie@
the latter is… well not very much alive
Anonymous
UWP's goal is a wrapper free experience, so I bet these two won't last more than 4-5 years
jamie@
oh god
Anonymous
your comment shows ignorance
Well, maybe, but UWP as a whole isn't as documented as Win32
Chungy
Win32 is a totally separate subsystem from UWP
Vitaliy ◀️TriΔng3l▶️
Working with __FIVectorView_1_Windows__CGaming__CInput__CGamepad stuff is fun 😜
Alejandro Jeditobe
https://twitter.com/x86corez/status/1181908765899153408
Alejandro Jeditobe
Upvote!
hacker12455
you got it
hacker12455
Done
Alejandro Jeditobe
Thanx
Anonymous
Well... Again, it'll barely work for four reasons... First, the lack of RAM (zram is like mandatory) or a RAMdisk, a thing that ROS lacks for now. A devkit will work even better. Second, the original hard disk may be swapped for a bigger, more reliable one. These are starting to fail badly (worn out motors, head crashes, dust inside and stuff) Third, I'm not sure if a period correct GeForce III driver is working on ROS (but since I've seen some FX cards working, maybe) Fourth, the Xbox may have a PC architecture, however it lacks the PC bootloader out of the box. Work may be done to softmod an Xbox so it has a PC like BIOS
rosbridge
<hbelusca> huh yes definitively on real HW xbox this is done on a modded xbox with cromwell firmware.
rosbridge
<hbelusca> For the graphics this is done by writing to the framebuffer prepared by the firmware + sending commands to the NV2A controller (as far as I could see from @Stas'M patches).
rosbridge
<hbelusca> The real problem(s) (there are 2 actually) that still exist are:
rosbridge
<hbelusca> 1. need some better USB support (+ implement small support in freeloader) to control input,
rosbridge
<hbelusca> 2. need to fix our FATX support.
rosbridge
<hbelusca> yeah that's the problem too.
Stas'M
I don't think it would be small
I think it would be more interesting to do interacting with firmware, since it have all required USB code
Stas'M
(more interesting and more efficient)
Anonymous
<hbelusca> 1. need some better USB support (+ implement small support in freeloader) to control input,
Well, sure, for now it only does PS2 input, but remember that XP didn't support that everytime as well...
Mike
About hard disks: iirc, compactflash memory card can be seen as ide disks, so this would remove the problems related to old hard disks (and even allow easy access to the files from another PC)
Mike
About geforce: even the geforce 610 I use in my htpc has xp drivers (both xp and xp64), but this doesn't mean it's the perfect card to try reactos, or, on the other side, that it will not work at all. The only thing is trying, and if you just need to send a readable output to monitor and trying to play some old games, IMHO a geforce 3 is OK.
Chungy
yeah CompactFlash uses PATA
Syrufit
Captcha solved, user verified. Welcome to the group ‎@Cherry_Kot
realAceHW
ReactOS Beta when