-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate Fig with Linux #34
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
@YU5Z8X2CvH1fv4ep And probably more months will pass. They're rewriting the entire Fig core from Swift to Rust, give them time. |
Swift also supports linux, so what's wrong with it? Or are the devs just following the trend of rewriting everything in rust? |
This comment was marked as off-topic.
This comment was marked as off-topic.
Congrats on the work done so far! I had a chance to play with Fig on OSX, and it was wonderful. Looking forward to your Linux release whenever you are ready ❤️ |
I know the original post said "Soon"(TM), but is there any chance that we might see some news on this in the near future? |
I've been proposing some implementation ideas for other OSes which actually solve a lot of fig's bugs and implementation problems in the discord. Check the thread i created on #cross-platform there |
2022 is here now, what is the status of this issue please? |
We are prioritising Linux and the Fig.js API after launching our next product in mid Feb. So aiming for an early April launch date. Stay tuned! |
Calendar marked |
Noice to see so many people rooting for Fig for Linux <3 |
Me too 🎉😅 |
That's some really awesome news! I hope you can show some proptotype or at least blog about it pretty soon |
This comment was marked as resolved.
This comment was marked as resolved.
Some exciting progress to share! 2022-03-14_20-20-58.mp4We've located the caret position, can determine what text has been typed, and got IPC working on Linux. 🥳 There is still lots to do, but some of the key technical challenges have been solved! |
Great! Also good to know Fig is written in rust :) (The ide logs and tabs showed it) |
This comment was marked as off-topic.
This comment was marked as off-topic.
If you're eager for the app, you can give them a thumbs up or some other similar gesture. If you're expressing impatience, it's best not to say so. |
Can it be run in any terminal or does it have to be integrated in each terminal application? If it has to be integrated in the terminal there should be
|
@mschrage Could you lock this issue? There are a lot of people subscribed to this who only want to be notified on actual updates. |
Long time coming, but we just launched Linux as part of the successor product Amazon Q! If you want to install here are the docs. Additional we just open sourced the codebase so its OSS software as well: https://github.com/aws/amazon-q-developer-cli |
"Long time coming" - almost 4 years, the project was considered abandoned for a while and the issue threads were locked. Now all of a sudden the project is being revived after being sold by lazy developers to Amazon. |
I don't think that word means what you think it means. Please archive this repo. It's dead, Jim. |
Careful, you might get some people giving you a thumbs down for telling the truth! |
Breaking news: Truth are lies, lies are truth. Up is down, down is up. ...and now back you your regular distractions... |
Fig, as people wanted to actually use it, died years ago. Archive the repo and cash your check. |
/me unsubscribes from this issue I followed almost 4 years ago... Nevermind the 266 updoots. Nothing to see here folks. Move along.... |
wow, why all the hostility? can anyone explain that to me? |
There was an announcement of a Linux alpha, the features and scope of the project changed dramatically over the next 3 years (not necessarily for the worse), and then you suddenly unlock by saying the corporation you sold your project to has made a Linux port. This was a piece of software I was interested in, but now it's some fragment of a giant corporation's cloud AI package. Users who have followed development closely probably see it from a different lens, but those of us who subscribed to an issue 3+ years ago to get updates on a release of software that no longer exists may be less enthused by this "Linux launch". |
As an addition, not only were we (users interested in/participating in the Linux Alpha) abandoned due to the sale of this project, but the scope changes of the project made me at the very least uncomfortable with it. I don't need AI in my CLI. That is not something I asked for. I don't need yet another attempt to inject AI where it doesn't belong. I don't care for the idea of having a cli tool snooping about in my workspace/system and reporting everything back to "the cloud". As a final thing, this project is dead. Killed by the developers. I don't blame them for getting paid, but if the project is dead, why are you using an issue here to promote your replacement product after you've already done that? The only thing this has done is made me remember to unstar and unsub. I'm happy for you having got paid. Leave me alone |
While I think, every project owner is allowed to do whatever the hell he sees fit, including selling it to one of the biggest and most atrocious, disgusting and sickening, (I could go on and on) etc. companies around the globe, pretending, like this project did not die and then continue to promote it here is a different story and deserves a verbal punch in the face. |
Me? Sorry but you've got that part dramatically wrong. |
Okay, I read some more about "Amazon Q", but have not tested it (and don't necessarily want to). It appears that it might (1) try to push you in the direction of using Amazon services in your code, or (2) only give answers related to Amazon services, or (3) require paying for AI through Amazon to work. But it would be helpful if someone who has followed the project the whole time or tested it or has some deeper knowledge would describe exactly what is wrong rather than merely alluding to it. Obviously so Jeff Bezos is a lowlife slime ball who made literally billions by using his propaganda machine to sow lies and fear about the supposed dangers of Covid and the supposed benefits of the mRNA "vaccine" in order to reap personal rewards, but I doubt that that is the entire reason for the hostility toward Q.... |
This is worse than a license rug pull: the code was never open sourced to begin with so it can't even be forked and continued. The project has an open license but since the actual developed code was never made public and only made available as binaries, it might as well never have existed. Now with the buy-out/sell-out and turning it into a completely different product most of us are not interested in, we can't even check out the thing we were interested in in the first place. |
@alerque can you summarize the differences between the original fig and Q? The claim was made earlier that this is now OSS. Is that a lie? Is the Git history not there? Can't you reconstruct the original fig? |
@brandondrew No the Git history is not here. To my knowledge it was never posted. The entire repo is a place holder and they were supposedly going to publish the source when they were ready to tag a stable release. Their limited access alpha release process was binary-only and not a source release. In other words the original was never open source and cannot be reconstructed. The new product seems to be a thin client primarily driven by a proprietary cloud AI service. Who cares if the thin client is open source, the product itself is not open sourced or available for tinkering with, extending, changing, etc. |
@alerque Thanks for the added context! |
Global "you" towards the devs, bad wording.
I'm not angry at Bezos because of some nutjob conspiracy |
Users having to crawl through Git history, if it was even available, to reconstruct what they once loved should actually tell you a lot about why you're facing so much resistance and hostility with your announcement. It isn't what people wanted, and nobody wants to painstakingly reconstruct what they once loved because the previous owner didn't love it as much. |
It is not my announcement. Do you always make accusations so carelessly? |
Saying it is your announcement is not an accusation, an accusation would be claiming you did something wrong - like a crime. You can continue being hostile and having an attitude with people as much as you like, the thread shows the results with or without your ridiculous input; nobody else here is on your side, or quite frankly the project's side. If you wanted people to be supportive, excited or somewhat enthusiastic regarding the repository, you have certainly lost all hope of that now if it wasn't lost before. Good luck. |
Notice how you pick the 3 last words of the most meaningless sentence of my reply as well, not the actual point I was making about the feedback you were receiving - which is what you had asked for, might I add. You clearly don't actually care for people to add more context to the "hostility" you claim to receive if you're constantly snapping back at people for adding said context. |
@ameasere I fail to understand your words against @brandondrew. He seems like not having anything to do with Fig, but your text implies he was part of the project and he's in fact the one who directed it towards this destination. |
Initially did mistake him for the person who made the Linux announcement, but the then stupid appendix to his comment became more of a problem. Despite the misunderstanding, I stand by what I said: doesn't seem to really care much for the context they were asking for, since they seem to attack the people who wish to provide it. |
ameasure: There is nothing in the definition of "accusation" that only applies to crimes. You called it my announcement, but I didn't make the announcement. That's very clearly an accusation. You can claim I'm being hostile but it's clearly you who is hostile. I was simply trying to understand the hostility here. While the hostility toward Fig might be warranted, I don't think asking a sincere question warrants any of the hostility that you are directing toward me.
This clearly illustrates my point.
Are you not responsible for what you write? Am I obligated to ignore hostile accusations because you regard them as meaningless?
Pointing out falsehood in your accusation is not "constantly snapping back". The only person here I see "constantly snapping back" is you. Do you expect messages of deep gratitude instead? I was thankful to @alerque for the information he gave. But your message was quite unlike his. |
Yeah I'm not reading all that, happy for you or sorry that happened or something - save the essays for your college teacher, not for dead repositories. |
You demonstrate yet more hostility, and also a disinterest in the facts. |
You done delivering your TED talk yet? |
Will you please stop flooding my inbox with this, both of you? God, I don't even remember why I was following this issue... |
Fig currently works on macOS only. We will build a port that integrates with Linux soon.
Please subscribe to this issue to get an update when Fig's autocomplete integration with the Linux is ready 😄
The text was updated successfully, but these errors were encountered: