The context hovering seems to have its advantages tho. When I ask claude why a given output was produced by a given program configuration it delivers a slop wall of guesses while Argon seems to actually understand what the code does.
And how does this disprove their point? I don’t think its the lines of code you write that allow you to decide whether or not you should roll your own crypto…
Isn’t writing Go for embedded systems kinda like eating soup with a fork tho?
This language was designed to write multithreaded asynchronous code to power microservice meshes.
If it's within like 90% of your targets and it's a far easier development experience, but you need to optimize a small bit to fit in the budget, tools like this can be fantastically useful. Rewriting the whole thing in, like, C, complete with a coroutine stack, would be a hell of a lot more work than "avoid allocations here".
There are commercial products using Go in embedded systems already, via TinyGo and TamaGo compilers.
Even ESP32 is much better than any MS-DOS PC, we have to update our understanding of embedded platforms, not everyone is writing Assembly or C dialects to PIC like microcontrollers.
Imo if you’re reprompting you’re losing. If the agent oneshots the task its good but if it doesn’t manage it on the first try you will get there faster by doing it yourself.
I don’t think this is true at all. Maybe if you have an agent writing some of your code it will be 99% because its so verbose but I don’t think the modal software engineer is a vibecoder.
The certitude with which you condemn your peer without the slightest consideration for subtlety or alternate explanations for what you've understood to be true -- this comment is such a beautiful encapsulation of the state of discourse today. In some ways it is the modal comment of the moment. Tastelessness and mediocrity and inability to grasp nuance or feign at humility are on full display, not to mention a fantasy for violence
How is that the same thing at all? You didn't understand the comment you replied to and were confidently wrong. The person replying to you understood what you were saying very clearly and didn't make any ridiculous "you may not last long" comments like you did...
I think this is an uncharitable misinterpretation of the parent comment. I took “modal engineer” to mean “the statistical mode of engineers”, not a misspelling of “model engineer”. Which means I think you’re in agreement that using AI to write code is not necessarily vibe coding and that vibe coding is not what the majority (mode) are doing.
AI is just another way to not use your brain, I think there’s plenty of consensus around the fact that not using your brain makes you dumber.
So actually, yes you can say that definitely.
Unfortunately I was like this long before LLMs, trust me ;)
And yes I know it's a word, I know at least two meanings it has but in this particular usage I was not familiar with it. Anyways, I was wrong and I will take the L
Yes, those are not conflicting statements. All rectangles are not squares after all. If you can reply to me and actually put the point that you are attempting to make into words I would be shocked. Give it a try!
reply