stirner
Joined 10 years ago
Joined 10 years ago
I’m fine with them adding ports back as long as they still let you do PD into the TB3 ports. It’s still not super easy to determine exactly what features are supported by different devices/adapters/cables, especially when dealing with USB-C. However, it seems like a bit of a backslide on a bold move to push the state of the art forward that I believe was the right move.
Re: MagSafe, I honestly think they would be better off making a MagSafe adapter—a pair of small terminals which connect to the end of the power cable and the port that connect to each other magnetically. I imagine they could make this pretty low-profile and clean. But then it wouldn’t be exclusive to Apple’s own hardware, so I doubt they would ever go this route. A quick search turned up an existing adapter [1] that supports 100W PD and 40 GBPs data transfer so it’s definitely doable.
[1] https://www.newsshooter.com/2020/03/30/magrig-magnetic-usb-c...
[1] https://goo.gl/maps/iDZ2TZV4o12DiKtL8
[2] https://www.theatlantic.com/business/archive/2014/06/how-cit...
And it’s usually embedded in another computing environment that happens to revolve around text called UNIX. If only the scripting language of the latter was as elegant as Lisp...
Remote: Yes
Willing to relocate: Can relocate next year if necessary
Technologies: Go, C, Rust, Swift/iOS, JavaScript, HTML/CSS
Résumé/CV: Hosted on my LinkedIn profile in the Featured section
Email: willalexander at alumni usc edu
GitHub: https://github.com/wwalexander
LinkedIn: https://www.linkedin.com/in/wwalexander/
I’m a developer with experience in front end web development, backend and systems development in Golang, and iOS development. I have built a self-hosted music streaming server using Go and FFmpeg, a dynamic DNS system based on the DigitalOcean API, an optimized Rust translation of the UNIX password hashing routine crypt(3) for a password cracker, as well as many other tools focusing on simplicity, correctness, and interoperability. I have worked with iOS and SwiftUI, and led the development of a Python toolkit for hijacking drones at my capstone course at university. I have also helped a small business automate tasks to save time and avert technical issues, including a system for sorting packing lists by warehouse location to improve the ease and efficiency of shipping orders.
I am a fast learner and I love building solutions that get to the core of a particular problem or system. I was recently unemployed due to COVID-19 and would love to talk if you think my skill set could be of use for your business!
[1] https://support.google.com/youtube/thread/16442768?hl=en&msg...
I guess SwiftUI exacerbates the problem since expressions are necessarily very deeply nested.
type of expression is ambiguous without more context
on a straightforward Text() expression halfway up the file). The only way to find the actual source of the error is to undo every change until the error disappears, and coupled with sluggish compilation times this becomes a real pain. I hope they address this issue as part of their improvements.