Comment by refulgentis
Comment by refulgentis 2 days ago
There's a false equivalence there, between being not-even-wrong and "you have a bunch of UNIX commands followed by a Windows batch file execution."
Note we both agree on that, you seem to assume I claimed something else, like, cd doesn't exist on windows.
Let's say I instead said "this doesn't work on Windows"
I spent probably...8 hours? on Windows this week doing dev, and I'm about 70% sure all of those commands will work on Windows, with dev mode switched on, with WSL on, prereqs installed...
Let's steelman this to the max: any possible prerequisite that could block it, doesn't mean its actually blocked. Dev mode on, WSL, prerequisites wrestled with and installed, can download source and edit then compile, but can only patch build errors, not add new functionality.
Are you 100% sure those commands will work?
(separately, you misunderstand the quote re: glass houses. It would apply if I had used AI to write not-even-wrong claims and then submitted to HN. This misunderstanding leads to a conclusion that it is impermissible to comment on the correctness of anything if you may be incorrect, which we can both recognize leads to absurdities that would lead to 0 communication ever.)
>There's a false equivalence there, between being not-even-wrong and "you have a bunch of UNIX commands followed by a Windows batch file execution."
>Note we both agree on that, you seem to assume I claimed something else, like, cd doesn't exist on windows.
No, you made a specific claim of "Your setup instructions use UNIX commands up until they require running a Windows batch file", when those "UNIX commands" were "pip" and "python". That statement is incorrect because those commands are readily available on windows.
Your remark about "you seem to assume I claimed something else, like, cd doesn't exist on windows" is absurd at best and verges on bad faith that I'm not even going to engage with it.
>I spent probably...8 hours? on Windows this week doing dev, and I'm about 70% sure all of those commands will work on Windows, with dev mode switched on, with WSL on, prereqs installed...
Which commands are those? The only non-native windows commands I see are git, pip, and python, the latter of which are both included in python. You're making it sound like you need to jump through a bunch of hoops to get those commands working, when really all you have to do is run the installers for git and python.
>Are you 100% sure those commands will work?
Again, my claim isn't that the project works 100%, or even that it's not AI generated, it's that your critique makes little sense either.
>(separately, you misunderstand the quote re: glass houses. It would apply if I had used AI to write not-even-wrong claims and then submitted to HN. This misunderstanding leads to a conclusion that it is impermissible to comment on the correctness of anything if you may be incorrect, which we can both recognize leads to absurdities that would lead to 0 communication ever.)
No, the reason why I accused you of AI generated comments and made the remark about glass houses is that claiming "pip" and "python" are "UNIX commands" is so absurdly wrong that it's on the level of the OP. I agree that you don't have to be 100% correct to accuse people of posting dumb stuff, but you shouldn't be posting dumb stuff either.