My Macbook Pro 13" Early 2015 w/ 8 GB RAM and 128 GB SSD is still very usable for what most people commonly use a laptop for - browsing the web, e-mail and streaming.
Of course :) It’s interesting to hear the ideas people come up with, but so far no one has demonstrated any practical results that would significantly improve the quality of work in my field. It has, however, increased the amount of slop that I need to deal with on a daily basis. Worse yet, it is not always programming slop :)
> And it is already useful, just not as much as some people sell it
In a general context, I agree. When it comes to programming, however, my experience has been different. If this technology were presented more modestly / realistically, it likely wouldn’t have attracted billions of dollars in investment and the hype. I think this is exactly what many sensible people point to when debating whether this is a bubble :)
> They insist the tech will never work, and avoid learning about it, becoming progressively more paranoid and isolated.
They can always learn the technology later, when and if it proves itself to be useful :) I personally don't understand the hype, even after using Claude and other AI tools - but perhaps that will change in the future.
> Any new software developers entering the field from this point on will have to know how to use and be expected to use AI code-gen tools to get employment
Most open source software tooling Were designed to be dynamically linked. It is non-standard to statically link things together, which causes various random issues.
On what reasoning do you make this prediction? Just because corporations are mandating their employees to use AI right now does not mean it will continue.
After reading your post, I went looking for good C/C++ implementations suitable for embedded development, and honestly, I couldn’t find many! MQTT is typically straightforward to implement, so most companies develop their own version to better adapt to the specific systems they use for data transmission. That said, maybe this is an opportunity to create a well-designed MQTT client implementation tailored specifically for embedded devices! :)
It is not directly comparable because LwM2M was originally developed for device management, while MQTT is primarily used for transferring telemetry or other opaque data.
My personal gripe with LwM2M is that it uses CoAP (Constrained Application Protocol) as its primary transport protocol. Since CoAP is based on UDP, you’re forced to rely on DTLS for authentication and encryption. Managing sessions with DTLS can be quite frustrating, and unlike TCP, there’s no reliable indication of when a session is closed by your peer.
Another issue is that it doesn't strictly follow the client-initiated communication pattern and can receive unsolicited messages from the server. I have found this to be very unreliable in real-world conditions for Device Management use cases.
There aren’t many telemetry transfer protocols suitable for IoT besides MQTT (especially for resource constrained systems). It is incredibly simple to implement, has numerous libraries available in various programming languages, is supported by major cloud providers and is designed to operate over TCP (meaning you avoid DTLS).
We have shipped many products that use MQTT for telemetry transfer to various different vendor servers and it always just worked. It was never a pain-point in stark contrast to CoAP or some proprietary protocols.