search

brimdata / super

An analytics database that puts JSON and relational tables on equal footing
https://zed.brimdata.io/
BSD 3-Clause "New" or "Revised" License
1.4k stars 67 forks source link

Windows 7 support #5040

Open sergeevabc opened 9 months ago

sergeevabc commented 9 months ago

Dear zq/zed developers, Windows 7 users like me are unable to use your app on anymore, because @golang team betrayed the community and cut off such users in their recent compiler. Whereas JQ works fine, because C team does not engage in such segregation and thinks about a wider audience. Could you be so kind to do something about that? Examples of apps such as Brename, Croc and Nexttrace (to name a few) convince that this is possible.

$ zq.exe
Exception 0xc0000005 0x8 0x0 0x0
PC=0x0

runtime.asmstdcall()
        /opt/hostedtoolcache/go/1.21.7/x64/src/runtime/sys_windows_amd64.s:65 +0x75 fp=0x22fca0 sp=0x22fc80 pc=0x474015
rax     0x0
rbx     0x2d66800
rcx     0x2dbde60
rdi     0x7fffffdd000
rsi     0x22fea0
rbp     0x22fde0
rsp     0x22fc78
r8      0x0
r9      0x22fee0
r10     0x2d8f638
r11     0x21
r12     0x22fec0
r13     0x1
r14     0x2d65b60
r15     0x0
rip     0x0
rflags  0x10293
cs      0x33
fs      0x53
gs      0x2b
philrz commented 9 months ago

@sergeevabc: Thanks for your interest in Zed and for sharing the links to the other projects where you've had success with motivating Windows 7 ports. I saw your explanation for why you remain passionately devoted to continuing to use Windows 7 despite Microsoft dropping support for it 4+ years ago. While we certainly respect your decision to run whatever you like on your desktop, there's valid reasons why we'd not plan to provide support for this from the core Zed project team. Just to name a couple:

  1. My understanding is that we'd need to compile with an older version of the Go toolchain, and meanwhile we've already evolved the Zed code base to begin relying on functionality in the latest versions of Go. Maintaining a variation of the code base to support an EOS platform is a tough sell.

  2. As it's end-of-support, it's difficult/impossible to run Windows 7 in modern build/CI systems we rely on like GitHub Actions and AWS to create builds, reproduce user issues, and run test automation. We'd be nervous of supplying binaries without any ability to actively test/support them.

We have a small core development team working on Zed, so due to our numerous other priorities, I don't expect we'll be able to justify the effort here. Of course, as the code is all open source, you and/or other passionate Windows 7 users are welcomed to compile/share your own builds within the LICENSE terms. We're happy to hold this issue open so other interested parties can find it, and if the level of activity reaches a point where there's something produced from a community of interest we could call it out in the docs, e.g., "Those interested in Windows 7 support can get builds [from here] and help [from there]."

Sorry the news isn't what you were hoping to hear, but hope that makes sense.