-
-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop support for windows #897
Comments
I am not aware of anything bad with it, but let me summon @cescoffier here |
+1 |
/cc @violetagg |
I’m fine with it. What’s less work for you. |
+1 |
@normanmaurer I'm fine with that |
I'm biased, but I'm in favor. We already don't support any native transports for Windows. |
Isin't the windows JDK implementation much worse performance wise than BoringSSL? |
@zekronium maybe ? Honestly I don't know ... That said no-one of our core developers has any use-case for windows so I feel we should better invest our energy in things that matter to us :) |
@ejona86 so any concerns from the GRPC side or not ? |
I'm fine with dropping Windows support, but I'm curious about why. Is it because of complex build and release process? |
Windows seems least complex to build atleast for me. What is windows specific here that requires/required significant amount of maintenance work? |
It's more about that if something does not work no-one will be able to fix it... |
Has that happened? |
I propose to drop support for windows and just focus on linux / macOS. Users of windows can just use the JDK implementation for SSL
The text was updated successfully, but these errors were encountered: