713
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Jun 2024
713 points (98.6% liked)
Technology
55610 readers
3532 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
You don't need a laptop to use a framework mainboard, they run without battery and display and everything. So if you have a Framework 13 or are in the market for one this might actually be a very nice thing, especially if the price is comparable to other boards.
I guess? But why would you swap to RISC-V from their x86 boards? It'll be slower and less compatible.
I can see it for devs, but they're going to want a separate laptop or an SBC, they're not going to be swapping mainboards on the regular.
I'm considering it as a second laptop option, but I have a particular niche use case: I'm a developer who writes developer tools and is currently trying to ensure we have first-class RISC-V support.
This is probably what I'll go for if I buy in the next month though: https://liliputing.com/dc-roma-laptop-ii-packs-an-octa-core-risc-v-processor-16gb-of-ram-and-ubuntu-linux/
Hooking up a BananaPi to a keyboard+monitor is going to be quite a bit cheaper, and unlike with the framework laptop you can't re-use case, monitor, etc. with an upgraded board.
It would, but I already have several dev boards I use in that configuration. What I'm looking for now is something I can take with me to use as a semi-daily driver so I can start reporting bugs in real world use cases.
You can develop using it as an SBC, then put it into the laptop when you go to a conference to present your stuff. Or if you really want to code in the park it's not like it'd be a microcontroller, it is fast enough to run an editor and compiler.
But granted it's a hassle to switch out the mainboard. OTOH you can also use the x86 board as an SBC so when you're at home it doesn't really matter which board happens to be inside.
I guess from framework's POV there's not much of an argument, it's less "do people want potato laptops" but "do we want to get our feet wet with RISC-V and the SBC market". Nobody actually needs to use it in a laptop for the whole thing to make sense to them.