Microsoft Will Release Their Edge Web Browser For Linux

[starshipeleven]

1. Stop using all those bad words. Can't you behave like a normal person just for once?

Don't anger me and I will not use bad words.

2. I can read and understand "plain" English.

No you don't. I never said I could read the future events, yet you said I did.

3. I think this one is most important. Is Server 2012/16/19 a 20 yeard old, closed source project? Can you be absolutely certain of it?

Yes. There is only one Windows, and that is used to make all different Windows versions. Maybe it's not 20 years old, it's the evolution of Windows NT, not of WIndows 3.1. https://en.wikipedia.org/wiki/Windows_NT

If it's closed source than what can we say about it?

Official documentation.
Decompiling binaries for reverse-engineering and hacking.

Any CVE affecting a core windows component affects Server editions of the same age too. That's proof enough that they are the same?

4. Yes. I said it myself that CEOs don't always do what makes most sense. Which means switching to other kernel doesn't have to "make most sense from purely economical standpoint". Your words with my words in your last comment makes contradiction. Very easy to spot.

I also said this (switching to Linux kernel) is what is most likely to happen in my opinion too.

We are discussing possibilities, and you just can't read english properly.

It is possible for M$ to make a switch.

Yes it is, but not by open-sourcing old core stuff.

[DebianXFCE Jr]

Don't anger me and I will not use bad words.

Your life really has to be very, very sad. Maybe you need a friend? A therapy? Or some tranquilizers? I suggest trying elsewhere. Phoronix isn't the right place for that.

No you don't.

Assumption #1

I never said I could read the future events, yet you said I did.

Your behaviour point to this conclusion.

https://en.wikipedia.org/wiki/Windows_NT

I can't believe you gave a link to wiki.

Decompiling binaries for reverse-engineering and hacking.

Does Wintrash license allows for that?

Any CVE affecting a core windows component affects Server editions of the same age too. That's proof enough that they are the same?

Same but what? Windows 10 with Server 2003? Or Server 2019 with Server 2000? I never wrote that Desktop and Server of the same age have different kernels. I did however wrote that kernel changes with time. In other words Server 2019 kernel isn't a 20 years old project (or Server 2000 kernel). And because it's closed sourced I can't even check what's inside. License!
Btw. I use Qualys for vulnerability management. You don't need to prove your knowledge by putting CVEs in a comment. We are talking about a kernel switch here, not security.

I also said this (switching to Linux kernel) is what is most likely to happen in my opinion too.

Yes I know you did. You don't have to repeat yourself. Low self esteem or something? You want me to pat you on the shoulder?

We are discussing possibilities, and you just can't read english properly.

Of course we are discussing possibilities. Did you just made assumption about my English? Assumption #2

Yes it is, but not by open-sourcing old core stuff.

Switch is one thing. And open-sourcing old core stuff is a second thing. Why do you mix those two things? I hope you can remember id Software engines and what they did with them after some time? Oh, yeah. I can't download source code for older id tech engines, because you can't open source old core stuff. Is Server 2019 kernel really that old? Why are you so certain about it? I hope you know that API and implementation are not the same thing.

[starshipeleven]

Your life really has to be very, very sad. Maybe you need a friend? A therapy? Or some tranquilizers? I suggest trying elsewhere. Phoronix isn't the right place for that.

Yeah, I find morons even in places where I would like to be. What a sad life I'm living.

Assumption #1

If you read things I didn't write, that's a fact

Your behaviour point to this conclusion.

Not really.

I can't believe you gave a link to wiki.

I'm lazy and the wiki is good enough, spank me daddy.

Does Wintrash license allows for that?

Does it matter?

Same but what?

Why are you so fucking stupid.
Windows Server releases are timed the same as Windows consumer releases. Features between such releases are also similar. WinServer 2019 is the same as Win10 Enterprise LTSB in 2019 (or however they called this release, they dropped the "LTSB" name but it's the same), WinServer 2016 is same as Win10 Enterprise LTSB 2016

In other words Server 2019 kernel isn't a 20 years old project (or Server 2000 kernel).

Server 2019 kernel is Windows NT and as such THE PROJECT started back in the day. So it is a 20 years old project.

Linux is also a 20 years old project (more or less). Does it mean that latest Linux kernel is 20 years old? No! You just can't read english.

And because it's closed sourced I can't even check what's inside.

Your own problem.
Also older Windows kernel versions are available as source under non-open licenses (you can look and study them but not use them)

Btw. I use Qualys for vulnerability management.

I have no idea of what that is and I don't care.

You don't need to prove your knowledge by putting CVEs in a comment.

I'm not. You could swap CVE with "vulnerability" and it would still be the same.

We are talking about a kernel switch here, not security.

No we were talking about Windows Server 2019 being the same as Windows 10 2019 and I said that the same vulnerabilities always affects both Server and Windows consumer of the same age.

Yes I know you did. You don't have to repeat yourself. Low self esteem or something? You want me to pat you on the shoulder?

come closer, I dare you.

Did you just made assumption about my English? Assumption #2

Still a fact, also proven by this very post.

Switch is one thing. And open-sourcing old core stuff is a second thing. Why do you mix those two things?

I'm not mixing. You are mixing, I'm clarifying.

I hope you can remember id Software engines and what they did with them after some time?

No and I don't care about that.

Is Server 2019 kernel really that old?

It is the newest Windows NT version. It has evolved over time of course, just like Linux.

Why are you so certain about it?

Official documentation.
Decompiling binaries for reverse-engineering and hacking done by various security specialists over the years.

Any CVE affecting a core windows component affects Server editions of the same age too. That's proof enough that they are the same?

I hope you know that API and implementation are not the same thing.

Yes.
And even then it does not matter for my point.

The more long is the life of a project, the more likely it is to have additional dependencies and licensed stuff inside it.

[DebianXFCE Jr]

Yeah, I find morons even in places where I would like to be.

I'm lazy and the wiki is good enough, spank me daddy.

Does it matter?

Why are you so fucking stupid.

No! You just can't read english.

Your own problem.

I have no idea of what that is and I don't care.

No we were talking about Windows Server 2019 being the same as Windows 10 2019 [!!!!!]

come closer, I dare you.

I'm not mixing. You are mixing, I'm clarifying. [!!!!!]

No and I don't care about that.

And even then it does not matter for my point.

https://www.youtube.com/watch?v=3O8J2locx5o

[betam4x]

Well, sure. It's just a Chromium re-spin. So, why not? When they release Office for Linux then I'll actually sit up and pay attention. Microsoft is becoming a Azure cloud company that happens to sell an OS and some applications. All their billing, etc... is moving to a cloud subscription model.

Office on Linux is actually a bit harder to pull off. The codebase of office does some absolutely batshit crazy stuff. The only way we'll get office working on Linux is via Wine and people like me (former Wine and ReactOS developer), and I'm planning on cancelling my office subscription next month, so there is that.

[starshipeleven]

https://www.youtube.com/watch?v=3O8J2locx5o

https://www.youtube.com/watch?v=oHg5SJYRHA0

[fuzz]

Office on Linux is actually a bit harder to pull off. The codebase of office does some absolutely batshit crazy stuff. The only way we'll get office working on Linux is via Wine and people like me (former Wine and ReactOS developer), and I'm planning on cancelling my office subscription next month, so there is that.

Or they could release the web versions as desktop applications?