Skip to main content
IntelCustomer feedback

Intel faces negative developer feedback regarding Quartus Prime, with users describing poor documentation, difficult installation, and a clunky workflow compared to AMD Vivado.

What happened

Post: "Why is Intel Quartus so clunky?"

Source

RedditOct 30, 2026By u/SignalPalpitation327

r/FPGA

Why is Intel Quartus so clunky?

upvotes
9
comments
6

Post

Highlighted: the lines this signal was extracted from

I started learning FPGA development on AMD Vivado on a Basys3 board. After some fundamentals and learning the FPGA workflow, it all worked coherently for me. Troubleshooting designs has a good flow, easy to check critical paths/timing. There is abundant documentation and easy access to every element like IP cores, templates for implementing pretty much anything… Then, I happen to find a good deal on a DE1-SoC board and got it in excitement. However Intel Quartus have been a nightmare to work with. Nothing works, everything requires a custom workaround. I wouldn’t even be able to intall it and get it running without extensive AI help. Documentation is very bad. Even now I can actually do some work on it, I have to stick to the GHRD as a baseline or things won’t work. I really liked the DE1-SoC board, it is a beast but not being able to use it properly feels sad. Maybe I am doing something wrong or missing essentials that would make the experience better? I wanted to ask the community’s current opinions on the topic. How has been your experience with Vivado suite or Quartus Prime?

reddit.com/r/FPGA/comments/1xjblb2/why_is_intel_quartus_so_clunkyRead the full source

Comments on the post

1 of 6 comments
  • “Can you give some examples of what doesn't work? I have a lot of complaints about Quartus, but it does generally work well enough. Most of the complaints I have are around some of the more advanced features / tools that you only really need in a professional environment when working on larger designs. Documentation can be hit or miss, depends on where you're looking. They do tend to improve it”

    u/captain_wiggles_5 points · Oct 30, 2026View

Extracted by Autobound

From the Signal API record
Signal
Customer feedback

What this signalsUser posts often show product pain before it reaches reviews or churn.

Subreddit
r/FPGA

Companies

  • AMDAlso named

The full record

From the Signal API record

Numbers

Mentions
4

Details

Timing
Ongoing state
Category
Usability
Virality
Medium
Post kind
Text
Prominence
Core
Company's role
Vendor

Topics and mentions

Topics

  • developer experience
  • documentation
  • usability
  • fpga
  • eda

Products named

  • Intel Quartus
  • Quartus Prime

Extraction

Sentiment
Negative
Detected
Oct 30, 2026
signal_type
reddit-company
signal_subtype
customerFeedback

Use this data

Get every Reddit signal for Intel and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Intel this week?”

  2. Send it to your own tools

    The Signal API returns Reddit signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full reddit-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/cf77ae5b-3c13-5062-a2d1-42d587cea2fa returns this record as JSON. POST /v1/companies/enrich returns every signal for intel.com.

{
  "signal_id": "cf77ae5b-3c13-5062-a2d1-42d587cea2fa",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-10-30T10:21:13+00:00",
  "company": {
    "name": "Intel",
    "domain": "intel.com"
  },
  "data": {
    "nsfw": false,
    "stage": "none",
    "awards": 0,
    "timing": "ongoing_state",
    "topics": [
      "fpga",
      "eda",
      "developer experience",
      "documentation",
      "usability"
    ],
    "post_id": "1xjblb2",
    "summary": "Intel faces negative developer feedback regarding Quartus Prime, with users describing poor documentation, difficult installation, and a clunky workflow compared to AMD Vivado.",
    "category": "usability",
    "comments": [
      {
        "url": "https://www.reddit.com/r/FPGA/comments/1xjblb2/comment/19rvjvm9wfnk5/",
        "depth": 0,
        "score": 5,
        "author": "captain_wiggles_",
        "excerpt": "Can you give some examples of what doesn't work?\n\n I have a lot of complaints about Quartus, but it does generally work well enough. Most of the complaints I have are around some of the more advanced features / tools that you only really need in a professional environment when working on larger designs.\n\n Documentation can be hit or miss, depends on where you're looking. They do tend to improve it",
        "posted_at": "2026-10-30T10:34:53.000Z",
        "author_url": "https://www.reddit.com/user/captain_wiggles_/"
      }
    ],
    "evidence": [
      "[post] However Intel Quartus have been a nightmare to work with. Nothing works, everything requires a custom workaround.",
      "[post] Documentation is very bad. Even now I can actually do some work on it, I have to stick to the GHRD as a baseline or things won’t work."
    ],
    "virality": "medium",
    "post_date": "2026-10-30T10:21:13.000Z",
    "post_kind": "text",
    "post_text": "I started learning FPGA development on AMD Vivado on a Basys3 board. After some fundamentals and learning the FPGA workflow, it all worked coherently for me. Troubleshooting designs has a good flow, easy to check critical paths/timing. There is abundant documentation and easy access to every element like IP cores, templates for implementing pretty much anything… Then, I happen to find a good deal on a DE1-SoC board and got it in excitement. However Intel Quartus have been a nightmare to work with. Nothing works, everything requires a custom workaround. I wouldn’t even be able to intall it and get it running without extensive AI help. Documentation is very bad. Even now I can actually do some work on it, I have to stick to the GHRD as a baseline or things won’t work. I really liked the DE1-SoC board, it is a beast but not being able to use it properly feels sad. Maybe I am doing something wrong or missing essentials that would make the experience better? I wanted to ask the community’s current opinions on the topic. How has been your experience with Vivado suite or Quartus Prime?",
    "sentiment": "negative",
    "subreddit": "FPGA",
    "post_title": "Why is Intel Quartus so clunky?",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/FPGA/comments/1xjblb2/why_is_intel_quartus_so_clunky/",
    "entity_role": "vendor",
    "post_author": "SignalPalpitation327",
    "upvote_ratio": 0.7647058823529411,
    "mention_count": 4,
    "mention_surge": true,
    "subreddit_url": "https://www.reddit.com/r/FPGA/",
    "total_upvotes": 9,
    "comments_total": 6,
    "total_comments": 6,
    "other_companies": [
      {
        "name": "AMD",
        "role": "competitor",
        "domain": "amd.com"
      }
    ],
    "post_author_url": "https://www.reddit.com/user/SignalPalpitation327/",
    "signal_category": "feedback",
    "comments_included": 1,
    "products_mentioned": [
      "Intel Quartus",
      "Quartus Prime"
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.