Later a demo was showed with multiple networked boards in one case.
An AMD guy came on later and said they are focusing on Rocm in 2025, let's see what that means.
588 karma · joined July 26, 2013
Later a demo was showed with multiple networked boards in one case.
An AMD guy came on later and said they are focusing on Rocm in 2025, let's see what that means.
I've experimented with 'transpiling' to RST with Pandoc for purposes of digital documentation - but it's not quite there. Would love to see a flavour of Typst that could be viable for digital documentation with a decent live preview experience in VSCode.
I know this isn't the purpose of Typst, but one can hope. Would also welcome advice on this subject of decent authorship digital documentation - some of these frameworks are quite frankly massive, unweildy and painful to deal with.
Double thanks for the 3rd party mac mini SSD tip - eagerly awaiting delivery!
I'd like to hear more from you about the specifics of Angular that work really well in an enterprise (at least, large complex flagship saas webapp) scenario, and how you overcame specific Angular challenges? I hear many negative thing about Angular, but I really just wonder if there is misunderstanding about how things should be done.
If that's not something suitable for a casual HN comment, perhaps something like this would be a good blog article.
Faced with a technology decision, it's been interesting reading what people on HN say about React/Svelte/Angular.
What I seem to read around here is that React is great and simple until it's very large, and you could pay a high price later on if you make poor decisions early. Lots of complaints about complexity in a large codebase, telling me that architecture gets tricky especially with many vendor libraries.
Angular is talked about with disdain mostly, steep learning curve and lack of JSX. That could be a feature or benefit. You don't need to reinvent the wheel or architect everything as there's a strong structure in place, but you have to understand and do everything the prescribed way. What I want to know more about is once you have the right practices in place, how good is it to work with? What compromises and unsolvable issues remain once you get to a significantly large application?
Svelte has a very positive reception, but I'm not sure there are many 'enterprise'-y success stories yet and obviously specialists/talent will be rarer.
Not just the best alternative to GrapheneOS for non-pixel devices, but also a suite of other apps such as Mull, an Android Firefox fork.
This really was a passion project and SkewedZeppelin deserves much respect for the monumental amount of quality work that was involved in this, at massive personal cost. Wish him the best for the future and whatever else he does next.
Thanks for the 3 years of faultless updates. Not sure who else could fill those boots to be honest.
https://www.cpu-monkey.com/en/cpu-raspberry_pi_4_b_broadcom_...
This was a major problem with Pi 4/400, I had to resort to quite an extreme overclock and some hacky custom browser builds to improve this. Bought it for a family member new to computing. I was put off so much of the 'pi as a basic desktop computer' that I wouldn't buy another for this usecase. Never did make sense to me why it struggled so much with a quad core SoC that should have been able to handle it.
First thing I do on an SBC now is to see what resources are consumed playing back a 1080p youtube video.