|
| ▲ | basisword 3 hours ago | parent | next [-] |
| Because it's a lazy response. OP might not be a software developer. Should they learn complex software engineering to try and contribute or should they call out a missing feature that's important to them so the actual developers have some data on what to prioritise? |
| |
| ▲ | saghm 3 hours ago | parent [-] | | It's no lazier than saying "Still no <feature> support" | | |
| ▲ | basisword 2 hours ago | parent [-] | | a) that's feedback b) it's useful in a comment thread like this so people can quickly see what the 'caveats' mentioned in the title of the post are | | |
| ▲ | saghm an hour ago | parent [-] | | Feedback in a forum stating something the developers are probably well aware people want in a location the developers might not even be reading is not particularly useful feedback. As for the comment thread utility, sure, I guess if you think that not reading the article is valuable for the HN community, but I could just as easily argue that pushing back against comments like that could be seen as valuable for a community that values more thoughtful feedback. | | |
| ▲ | basisword 18 minutes ago | parent [-] | | It was valuable for me. I've been waiting for Asahi on M3 and quickly wanted to know what the 'caveat' was. Saved me some time. |
|
|
|
|
|
| ▲ | izacus 2 hours ago | parent | prev [-] |
| Apple could contribute as well, like Intel does for their Thunderbolt controllers. Why are you demanding a user does that for free instead of the big corp that made the platform? |
| |
