This looks like a lot of effort was put into it, but what pain point / problem does it address?
This looks like a lot of effort was put into it, but what pain point / problem does it address? Embedded applications (bare metal) is usually not that complicated, and when they are they are usually developed either on a RTOS, or on embedded linux which gives you almost all the advantages of desktop application development. Coming back to embedded applications not being that complicated, now you also need to get your developers to learn another framework and IDE while they are already under pressure to develop their current feature set. Like codehero states elsewhere it only adds another abstraction layer between you and the silicon, in a field where exact control of the silicon is paramount (Low power, response latency in real time, limited resources etc). Furthermore what guarantee do you have that Mbeddr will support the latest processor you are working on. At least with C being a defacto standard in the industry you have that guarantee. Furthermore most processor manufacturers supplies demonstration code to use their latest processor features, how easy is it to pull that into Mbeddr? I'm afraid this is a very fancy and polished solution looking for a problem.
Posted by kabouseng on Sep 13, 2014, 7:02 PM
Tags
Related issues
- That Reddit post is feeding more conspiracy thinking than helping.
- Support BYOK/Custom Models for Inline Code Completions
- DNS-PERSIST-01 challenge support (planned for late Q1 2026)
- Yeah I can't really blame people for not realising they have shitty mics and shitty internet because it's really hard for them to tell!
- Onboarding guide for FluentAssertions
- Add WebTransport support
Raise real-world problems, find people facing the same issue, and discuss solutions.9,000 issues0 comments
support (Network)
That Reddit post is feeding more conspiracy thinking than helping.
Support BYOK/Custom Models for Inline Code Completions
DNS-PERSIST-01 challenge support (planned for late Q1 2026)
Yeah I can't really blame people for not realising they have shitty mics and shitty internet because it's really hard for them to tell!
Onboarding guide for FluentAssertions
Add WebTransport support
> solar electricity is already cheaper than natural gas Does that include transmission?
Support for WireGuard only peers
This looks like a lot of effort was put into it, but what pain point / problem does it address?
This looks like a lot of effort was put into it, but what pain point / problem does it address? Embedded applications (bare metal) is usually not that complicated, and when they are they are usually developed either on a RTOS, or on embedded linux which gives you almost all the advantages of desktop application development. Coming back to embedded applications not being that complicated, now you also need to get your developers to learn another framework and IDE while they are already under pressure to develop their current feature set. Like codehero states elsewhere it only adds another abstraction layer between you and the silicon, in a field where exact control of the silicon is paramount (Low power, response latency in real time, limited resources etc). Furthermore what guarantee do you have that Mbeddr will support the latest processor you are working on. At least with C being a defacto standard in the industry you have that guarantee. Furthermore most processor manufacturers supplies demonstration code to use their latest processor features, how easy is it to pull that into Mbeddr? I'm afraid this is a very fancy and polished solution looking for a problem.
Comments (0)
No comments yet. Start the discussion.