guest3456 wrote: ↑
14 Dec 2019, 01:41
boiler wrote: ↑
13 Dec 2019, 10:22
I thought it was a shame that a user who is clearly very interested in this topic was basically driven away from the discussion of it. It made me think that discussion is only allowed on the forum if it is in line with some viewpoint held by some. I would hope that's not what's happening.
Of course, everyone is free to voice their disagreement with anyone's posts, but when it's made by forum leadership and in the manner it was made, it's not just expressing an opinion, it's saying "your perspective is not welcome here."
i understand where you're coming from, but that's not how i read things. this topic is old, and for quite a while, the topic went on just as you would have hoped: people interested in an AHK version for other operating systems, discussing the viability, etc. nothing being quashed, just other interested parties sharing thoughts and opinions. the thread was normal, nothing was unwelcomed.
it wasn't until a very specific comment was made which seemed to send the thread sideways:
edit: i will censor myself and edit out the quote. and dont even know if i should edit the next paragraph. second guessing all of this now.
there are subtleties to be read between the lines. that implies that AHK is not trying to innovate currently, and takes a shot at ongoing development, as if AHK doesn't move to other OS's then it will be left behind. i dont know how others read that, but i took it negatively. sometimes there is an entitlement where users feel they deserve x,y,z. if the author of that quote "thinks it might be better for x,y,z" then why don't they get to work to provide x,y,z instead of coming and making comments about AHK being un-innovative.
The topic is "We want AHK for Linux!"
People should be freely allowed to discuss a topic, without bullying or suppression. If a person doesn't like the topic, they don't have to comment on it. If a person disagrees with a comment, we can at least show civility. And I feel compelled to comment again, to stop possible misconceptions or false narratives.
That is, if you just discuss the topic of AHK on a different OS, you must develop the solution
I don't ever remember that being a requirement. But if that's so, are the people making disparaging comments actively developing any solutions for AHK on alternative OSes? Are they all themselves active developers, even for Windows? So if we are attacking posters who aren't developers just because they want to discuss AHK on Linux, what's really going on?
Being against the present development of AHK on Windows
I am not
. Because a person is for one thing, doesn't make them against the other. I can speak for myself, not have words put into my mouth. For the record, I've said that I like AutoHotkey. I'm pro all versions of AutoHotkey, be it AHK_L v1, AHK_L v2, AHK_H, IronAHK, etc... I think the concept behind the language is great.
The topic is about the possibility and wish to have AHK on Linux. To include something similar or a subset of it. To want AutoHotkey on Linux, does not make me or others against the present AutoHotkey on Windows. In fact, I think it might be more of the reverse. There appears to be those that don't want any projects started on an alternative version of AutoHotkey that could run on other OSes. Because if that's not the case, I don't understand what is with the negativity and attempting to silence those that do. For those people that are not interested in AHK on Linux, it is possible to leave those people who do want it alone. And there are multiple versions/forks of AutoHotkey now (to include the past) so that shouldn't be an issue.
No offered solutions or that any solutions weren't being discussed
On the first page, I gave the suggest to make a transpiler that can translate the AutoHotkey scripting language to corresponding code in Object Pascal. And Object Pascal has existing automation tools, libraries, and code to help. So, that's quite possible and valid. To include the possibility of a transpiler in other languages like Python or Lua, for people that are "fluent" in those langauges.
I stated it's possible to restart the IronAHK project, which already has C# code that allows it to run on Linux and macOS. That's more than quite possible, there is already existing code
, which is sadly collecting dust.
That's put on the table, as part of a discussion, for those that want to consider those routes. To be a developer, you need to have the knowledge, time, and interest to do it. It's not a pressing need for me, but it can be for others, and if they want to be a developer then there are some ideas and paths forward that they might not have known about. We don't need to force or bully anybody
to do anything that they don't want to do, let them volunteer on their own when they are ready or want to.
That development of AHK for Linux, will interfere or hamper development of AHK for Windows
Being involved in one project doesn't mean a person has to be involved with the other. If a person contributes to the C++ source code for AHK on Windows, they don't have to have anything to do with say IronAHK C# source code, an AutoHotkey to Object Pascal Transpiler (to possibly include other languages like Lua or Python), or some new alternative fork of AutoHotkey that works on Linux. They don't even have to comment about it. And if they do, I hope it would be to encourage or volunteer, and not attack or discourage the discussion of it.
That the present development of AHK is innovative or not
That would be an opinion not a personal shot or attack. I personally respect the present AutoHotkey developers, creator, and foundation members. Who have done a fantastic job
. The context was about developing alternative versions of AutoHotkey that could run on different OSes, not to take shots at present Windows development. The discussion was not centered around the present state of AutoHotkey Windows development, which is great, but rather would it be possible to develop something for other OSes.
I was not the one bringing the conversation to intertwining and mixing present Windows development with future Linux development together, as if it was or must be the same project, done by the same development team. Nor do I see Windows and Linux development being in competition with each other.
Rather, I saw it as likely separate projects and initiatives, which would have separate teams or people that volunteer to work on them. Debatably, the very nature of attempting to create a multi-OS version of AutoHotkey (or something similar) would require various levels of innovativeness or to do what hasn't been done before.