---
title: "Comment by Reza Pratama on \"Switaculous - SwiftUI on Windows and Linux!\" | Hashnode"
description: "an interpreter that only needs to cover the common widgets is the right scope, since the preview loop is what matters for learning. one idea is a small list of"
url: "https://hashnode.com/posts/switaculous-swiftui-on-windows-and-linux/6ad346f0996939fbcb435bcb/comment/6ad38d33ed581d3067924f09"
---

[Discussion](https://hashnode.com/posts/switaculous-swiftui-on-windows-and-linux/6ad346f0996939fbcb435bcb)

Comment [Switaculous - SwiftUI on Windows and Linux!](https://hashnode.com/posts/switaculous-swiftui-on-windows-and-linux/6ad346f0996939fbcb435bcb)

[Reza Pratama](https://hashnode.com/@rezapratama)

[Oct 17](https://hashnode.com/posts/switaculous-swiftui-on-windows-and-linux/6ad346f0996939fbcb435bcb/comment/6ad38d33ed581d3067924f09)

an interpreter that only needs to cover the common widgets is the right scope, since the preview loop is what matters for learning. one idea is a small list of unsupported views shown in the editor, so people know why something renders differently than in xcode.

[Kevin Naidoo](https://hashnode.com/@kwnaidoo)

[Oct 17](https://hashnode.com/posts/switaculous-swiftui-on-windows-and-linux/6ad346f0996939fbcb435bcb/comment/6ad38d33ed581d3067924f09#reply-6ad3be05f6231bc6d5c6ed3d)

Great, thank you for the suggestion; I will definitely look into this. Currently, there's also a console error log that will print errors if there's a syntax problem or if something is not implemented yet.

[Reza Pratama](https://hashnode.com/@rezapratama)

[Oct 18](https://hashnode.com/posts/switaculous-swiftui-on-windows-and-linux/6ad346f0996939fbcb435bcb/comment/6ad38d33ed581d3067924f09#reply-6ad49e10412b3e0f036745dc)

the console log covers a lot. if each "not implemented" error named the view and pointed to the supported list, people could tell a missing feature from their own typo without leaving the editor.
