8 ms·
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 i
by 999_cirno 3mo ago
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
- DrewADesign 3mo agoGenerally, assuming an RYO solution is a reasonable first approach is is a trap beginners fall into.
- 999_cirno 3mo agoStrong StackOverflow "don't do anything new, god forbid you may actually learn something" vibes On "Hacker" News of all places :)
- ben_w 3mo ago> don't do anything new, god forbid you may actually learn something vs > vibe code your own wrapper around the OS API
- 999_cirno 3mo agoIn fact, I suggest reviewing the documentation to assess your own level: https://developer.apple.com/documentation/virtualization/running-macos-in-a-virtual-machine-on-apple-silicon 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)") } })
- DrewADesign 2mo agoStrong “I’ve never had to deal with serious security problems stemming from a weird edge case, so this all seems silly to me” vibes.
- pmontra 3mo agoRYO 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.
- Someone 3mo ago> 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.
- deleted 3mo ago[deleted]
- brookst 2mo agoHonest question: is there anyone truly good at security who never made a potentially-disastrous dogfooding mistake while learning? Not to decent mistakes or amateur brain surgery, but there has to be some level of risk tolerance among tinkerers.
- DrewADesign 2mo agoDeveloping software that has the sole purpose of preventing something dangerous from happening is exactly when people should strive to be engineers, not tinkerers. Beginners often don’t know the difference.
- DrewADesign 2mo agoLearning as you go is great if you’re not basing your core development workflow or data integrity on it.