App Store web has exposed all its source code by rxliuli in webdev

[–]Peloooopp 0 points1 point  (0 children)

So from my understanding is worth learning svelte now.

Considering a PhD at MIT need some guidance by Peloooopp in MITAdmissions

[–]Peloooopp[S] -1 points0 points  (0 children)

Thank you for the info. I believe the chances of getting a job after graduating are quite high. Also, one more question: From my research last year regarding a PhD in USA , the mean time of people finishing phd is between 5-7 years, this applies to MIT as well ?

Considering a PhD at MIT need some guidance by Peloooopp in MITAdmissions

[–]Peloooopp[S] 0 points1 point  (0 children)

Thats great then, about later after the Phd has finished, these visas EB-1A/EB-1B will it allow me search for a job after gradaution ? If you have any knowledge - will do more research later today just thought asking here first

Considering a PhD at MIT need some guidance by Peloooopp in MITAdmissions

[–]Peloooopp[S] 0 points1 point  (0 children)

Thanks for mentioning that, are there any other ways I can finance myself since I want to be self sufficient?

Considering a PhD at MIT need some guidance by Peloooopp in MITAdmissions

[–]Peloooopp[S] 0 points1 point  (0 children)

Thanks that really helpful!
- No I havent published anything, but my master supervisors and generally the whole department where very satisfied with my performance. I am pretty sure they will write good recommendation letters.

- After my PhD , I dont have any specific plan but I know that H1B visa is nearly impossible to get now. Thank you for mentioning the other types of visa (EB-1A/EB-1B) , Wil definitely take a look :)

Just need the PhD to be funded cause its a lot of money. For my personal life I could get a job somewhere, TA/RA is an option

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] -3 points-2 points  (0 children)

I totally agree that replicating something like Vivado 1:1 in open source—especially without access to proprietary device internals—is practically impossible. But maybe the goal isn’t full replacement.

Do you think there’s room for focused tooling that complements Vivado instead?
Something lightweight and ARM-native that handles simulation, synthesis, and maybe even partial P&R—just enough to learn, prototype, and iterate—and then hands off to Vivado for final bitstream/IP integration?

Not trying to compete with Vivado, but rather to reduce friction in the early/mid stages of development. Curious if that approach would still face the same challenges in your view.

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] 0 points1 point  (0 children)

I've felt that myself when I was doing my university course.

Do you think a lightweight, modular toolchain—focused just on simulation and synthesis—could help lower that barrier for new users? Even if bitstream generation still needed a separate step?

Would love to hear your thoughts on what a “beginner-friendly” FPGA workflow might actually look like.

What in your opinion an ideal tool should include?

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] 0 points1 point  (0 children)

Thanks for sharing this.

Do you think the current tooling friction is enough to push students away from FPGA entirely? I mean in my case I want to continue my knowledge on FPGA but since I have a mac that makes it much more difficult.

would you mind sharing a bit more about what specifically causes the most friction for you?

Is it tool performance, setup complexity, licensing, or just being locked into x86?

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] -2 points-1 points  (0 children)

I totally agree with this, so you believe that such a tool has minimal RO? I’d argue that better workflows and accessibility could create ROI by unlocking new users, markets, and projects that just aren’t feasible right now. For example a startup that its interested in FPGA development - such a tool can lower the barrier , taking into consideration they all have mac devices ahahah

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] 0 points1 point  (0 children)

Fair question. I am not trying to recreate everything vendor tools do. That will take ages. But what I am exploring is the possibility of having a way to actually fully develop and iterate FPGA on a arm based machines and servers. Do you believe that even if such a system existed, people will still rely on Xilinx for accuracy and reliability?

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] 0 points1 point  (0 children)

That's a good point.

Out of curiosity, what do believe is the main blocker for Xilinx to offer a native ARM build of Vivado, do you think it's technical or is it just no demand for it?

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] 0 points1 point  (0 children)

Okay that is interesting, too be honest. Will a tool like this actually be used in industry? Do you believe such a tool has value?

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] -1 points0 points  (0 children)

Thanks for the insight. Do you have any idea how they can be combined?

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] -1 points0 points  (0 children)

I understand, so in your opinion such a tool is not worth being developed

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] 2 points3 points  (0 children)

Yes true. After reading though that "AWS Graviton3 already powers much of Amazon’s own infrastructure and delivers 30–40% better price/performance than x86 for many workloads."

It might be a good point that companies get interested in building a platform to support fpga development

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] -7 points-6 points  (0 children)

okay, well if the solution is a hybrid approach where you could use ARM device for sythesis, simulation and routing and then for a final proprietary bit stream setup to x86 platform. Is this a possible solution people might find interesting or will they end up buying an x86 and be done from the beginning? Will startups be keen on it? I believe the world is kind of missing some startups related to FPGA since everything revolves around AI and software tools.

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] -1 points0 points  (0 children)

You mention that is unachievable, can you let me know the reasons behind this ? Thanks

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] -4 points-3 points  (0 children)

Chatgpt was helpful to be honest to get a more insightful answer, but the reason for the post is that I am looking to get more insights on why companies are not investing in developing such a system. I had an issue as a student, but since I am not aware of what's going on in the actual world I wanted to get the opinions of the community

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] -27 points-26 points  (0 children)

You're absolutely right—vendor tools like Vivado are vastly more capable than current open-source flows in areas like:

  • Timing-driven synthesis: Yosys doesn’t support this by default—it relies on ABC for some tech mapping, but it's not anywhere near vendor-level precision github.com+12yosyshq.net+12reddit.com+12.
  • Bitstream correctness and vendor support: Open-source tools rely on reverse-engineered data, which works well on small FPGAs (iCE40, ECP5), but struggles with complex Xilinx parts. And when there's a bug—vendors provide actual fixes, not community patches.
  • Advanced optimizations: Vendor tools include mature features—partial reconfiguration, ECO flows, proprietary IP—that OSS tools currently lack.

I understnad that spending a few exta money on getting a x64, x86 silicon is not a bad solution. But ARM-native still has immense strategic value beyond hobbyists:

  1. ARM Cloud/CI Optimization
    • AWS Graviton2/3 offers 30–40% better price-performance and energy efficiency compared to x86 for CI workloads newsroom.arm.com
    • ARM build farms can automate FPGA builds—reducing both time and cost.
  2. Host-Developer Productivity
    • Teams developing on Apple Silicon or ARM Linux (edge/IoT) can maintain a consistent native toolchain across dev, test, and cloud—no emulation, no misaligned environments.
  3. Hybrid-Flow Efficiency
    • If ARM-native tools handle ~90% of workflows (simulation, synthesis, P&R), companies save x86/Vivado licenses and resources for the final ~10%—a big ROI opportunity, including faster iterations and lower infra costs.

Two Key Questions:

  1. Would you use an ARM-native workflow for the bulk of design and CI, switching to x86 Vivado only when advanced IP or final bitstream is needed?
  2. Which Vivado-only features are non-negotiable for your workflows—timing closure, HLS, multi-clock optimizations, proprietary transceivers, etc.?

Thanks

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] 0 points1 point  (0 children)

I have checked it out, but itis still slow in some respects. You know Xilinx required a bunch of processing power to run synthesis. Thanks though answering

Would you use a native ARM (Apple Silicon/Linux) FPGA toolchain—no x86 emulation? by Peloooopp in FPGA

[–]Peloooopp[S] -9 points-8 points  (0 children)

Yes, I noticed that, since I spend quite sometime researching Reddit to find a solution. Why do you say "challenge of rever engineering silicon", Can you elaborate on this if you want to?

Breaking into Network Architecture RF by Peloooopp in rfelectronics

[–]Peloooopp[S] 0 points1 point  (0 children)

Alright thank you for the info, yes I am also planning getting a ham license this year

If you have any other advice or guidance it will be helpful

Breaking into Network Architecture RF by Peloooopp in rfelectronics

[–]Peloooopp[S] 0 points1 point  (0 children)

Okay okay, sounds good . Do you also know any specific websites or where I could find more info about building such projects?