I wish more languages support old platforms. I'm working in a company and a lot of our customers are running Windows 7 and 8, few of them running Vista. I have to use ancient versions of development tools to target those. For example stuck on Java 8 for eternity. It's PITA.
Unofficial "Tier 4" Rust Target for older Windows versions
31–40 of 97 posts
Re: Unofficial "Tier 4" Rust Target for older Windows versions
#32I wish more languages support old platforms. I'm working in a company and a lot of our customers are running Windows 7 and 8, few of them running Vista. I have to use ancient versions of development tools to target those. For example stuck on Java 8 for eternity. It's PITA.
seeing Windows 8 called old really did some psychic damage to me. If it's not a secret, what kind of customers do you have? Is it some industrial stuff as usual?
Re: Unofficial "Tier 4" Rust Target for older Windows versions
#33Re: Unofficial "Tier 4" Rust Target for older Windows versions
#34For someone who is not a rust programmer, but would like to keep up to date, can somebody tell me what "Tier 4" is. And why must it be quoted?
[0] https://doc.rust-lang.org/beta/rustc/target-tier-policy.html [1] https://doc.rust-lang.org/rustc/targets/custom.html
Re: Unofficial "Tier 4" Rust Target for older Windows versions
#35I wish more languages support old platforms. I'm working in a company and a lot of our customers are running Windows 7 and 8, few of them running Vista. I have to use ancient versions of development tools to target those. For example stuck on Java 8 for eternity. It's PITA.
The problem is, as usual, that some people want that support, but nobody is actually interested in helping out with that support - and that doesn't only include people willing to help out with the code, it includes things like CI. Just how the riscv targets won't be able to reach tier 1 without GH or someone else offering CI support. Rust's target tiers, while historically not as enforced as they are today, have requ…
Re: Unofficial "Tier 4" Rust Target for older Windows versions
#36For someone who is not a rust programmer, but would like to keep up to date, can somebody tell me what "Tier 4" is. And why must it be quoted?
Re: Unofficial "Tier 4" Rust Target for older Windows versions
#37For someone who is not a rust programmer, but would like to keep up to date, can somebody tell me what "Tier 4" is. And why must it be quoted?
Re: Unofficial "Tier 4" Rust Target for older Windows versions
#38Earlier quoted context omitted.
It's not hard to do either, especially on Windows where backwards-compatibility is almost completely guaranteed. Of course those in the planned obsolescence mindset would fight hard against it, because then it would be harder for us to take the good without the bad.
I really hate my bakery, the buns are only edible for some days, after that, they grow mold! Without sarcasm, it is entirely reasonable that when the OS is EOL by the 1st party, software support for it by 3rd party also ends soon after that.
Re: Unofficial "Tier 4" Rust Target for older Windows versions
#39I wish more languages support old platforms. I'm working in a company and a lot of our customers are running Windows 7 and 8, few of them running Vista. I have to use ancient versions of development tools to target those. For example stuck on Java 8 for eternity. It's PITA.
The way some language runtimes have dropped support for Windows 7 feels outright malicious.
Re: Unofficial "Tier 4" Rust Target for older Windows versions
#40Earlier quoted context omitted.
The problem is, as usual, that some people want that support, but nobody is actually interested in helping out with that support - and that doesn't only include people willing to help out with the code, it includes things like CI. Just how the riscv targets won't be able to reach tier 1 without GH or someone else offering CI support. Rust's target tiers, while historically not as enforced as they are today, have requ…
I do wonder how much support is removed because of genuine maintenance or compatibility burden, because I've encountered enough examples where it was done solely because some target was deemed "too old" arbitrarily, even if it would still work without any modifications.
even in this case, maintenance burden is still real. supporting the old target often prevents you from using features/tools that make maintenance easier