upvote

points

by DrewADesign5 hours ago |
comments
upvoteby 999_cirno4 hours ago|
next
[-]
Of course, if you're not comfortable with reading or designing code, or don't feel like tinkering, you can use an existing project and they work great

But it is to note that the OS APIs do the heavy lifting, the projects are just wrappers

reply
upvoteby DrewADesign4 hours ago|
parent|
[-]
Generally, assuming an RYO solution is a reasonable first approach is is a trap beginners fall into.
reply
upvoteby pmontra1 hours ago|
parent|
next
[-]
RYO is the best way to learn, if you have the time to learn. After building one own solution one is able to assess the strengths and weaknesses of what other more experienced people built. Without the learning phase those other solutions are incomprehensible black boxes. The trick is not to skip the phase in which one researches available solutions.
reply
upvoteby Someone53 minutes ago|
parent|
[-]
> RYO is the best way to learn, if you have the time to learn

The problem is that nowadays, people roll their own solution, don’t take the time to learn (somewhat understandably, given the complexity of today’s stuff. You simply cannot learn all details about your hardware, OS, and third-party libraries anymore) but immediately deploy things in production.

Eating your own dog food can be good, but for security related stuff, it can easily be disastrous.

reply
upvoteby 999_cirno26 minutes ago|
parent|
[-]
I could never have thought adding the word "vibe" would draw so much public ire :)

I for one would encourage people to learn how the stuff works, including various low-level internals. But Tart and VirtualBuddy et cetera are again convenience wrappers (settings, pulling packages, friendly UI, and so on), the OS framework (Virtualization.framework) here does the actual work. If someone for personal use constructs a bad UI or chooses to store their settings on a public server then that's on them. And maybe a good learning opportunity, everyone has to start somewhere.

Not to forget, people are letting agents run loose in their home directory on their main box, surely we can do better than that here.

reply
upvoteby 999_cirno4 hours ago|
parent|
prev|
[-]
Strong StackOverflow "don't do anything new, god forbid you may actually learn something" vibes

On "Hacker" News of all places :)

reply
upvoteby ben_w3 hours ago|
parent|
[-]
> don't do anything new, god forbid you may actually learn something

vs

> vibe code your own wrapper around the OS API

reply
upvoteby 999_cirno3 hours ago|
parent|
[-]
In fact, I suggest reviewing the documentation to assess your own level:

https://developer.apple.com/documentation/virtualization/run...

If the below sounds too complex to work with, can review more basics first. Can start with a Swift tutorial

  virtualMachine.start(completionHandler: { (result) in
      if case let .failure(error) = result {
           fatalError("Virtual machine failed to start with \(error)")
      }
  })
reply
upvoteby iririririr3 hours ago|
prev|
[-]
all community projects (specially the ones maintained or opensourced by model owners) will certainly have the security-convenience trade offs set all the way to convenience while advertising all the (off by default) security features
reply