I chose my wording very intentionally. My criticism is exactly what I said.
It’s like comparing a bicycle to a light duty farm truck.
2,940 karma · joined November 20, 2020
I chose my wording very intentionally. My criticism is exactly what I said.
It’s like comparing a bicycle to a light duty farm truck.
While people do often use pis to do things you could do with an esp32, an ESP32 cannot do the majority of things a Pi can do.
Of course there are problems where knowing the code deeply is essential to solve the problem, but those really aren't the majority, if even less than 1% of business problems.
When it comes to what the average developer needs to understand, having a strong grasp on one functional and one procedural language can enable you to solve almost every problem in any language ecosystem, provided the correct resources. If you can do this, you can utilize an LLM for programming assistance well. If you can't, you probably should not heavily rely on one at all yet.
You should own and be the expert on the architecture and design of what you're building regardless of whether yourself, an LLM or another person is writing the code.
The LLM isn't "smarter" than you, it's more resourceful. It can (to varying degrees of success) translate your design into code. If you aren't still taking ownership and driving the design of that logic, the LLM isn't going to bring you success with anything other than single-use or hobby applications.
The vast majority of tech support scams come through apps on the Play Store. Not only that, but malicious apps get approved on the Play Store constantly.
There is no reason to take any claim that this change is meant to mitigate scams seriously, because there's no evidence to support that it makes a noticeable dent in such activity.
What this change does noticeably and impactfully do, is prevent, via chilling effects, users from being able to use their phones in ways that could lose Google and its partner vendors post-sales revenue.
As you said, serving people should be the end in itself, and this change doesn't do that - it hurts people.
My agentic workloads happen on two physical machines dedicated only to agentic workloads that share a VLAN with only eachother, with single token access to the specific repositories they are meant to push to and limited scope, hard limited credentials pulled from the hardware store on hardware token/fingerprint request only.
I view the safety around unmonitored agentic work in a similar way to how I view working with viruses or bacteria in a disease lab.
This stuff isn’t magic, it isn’t intelligent, but it is dangerous and needs to be handled with careful intent.
They cause traffic obstructions during rush hour every single day. Blocking entire lanes of traffic to pick up Uber customers.
> that being said of course I think it’s going to be way less than $5 an hour if you have a robot do it.
This is about an LLM-powered robot, not just a robot. At standard API prices, it'd run over $5 before it finished opening the door.
But is it cheaper than paying someone around $5 in labor to do it? Because until it is, it's not economical to have a robot do it.
You can train a specialized model for this, but a frontier model is ill-fitting.
It is not more complex in “many cases” at all.
Do you have any more detailed or up to date information? I’m not doubting that they built ISL capabilities, since ISL is often used for collision avoidance and small scale satcom - I’m doubting that it is being actively used to route internet traffic.
From a technical standpoint, the difference is scale and intent, but ultimately people and/or and organization are culpable for the output.
As I see it, in either case, the program can be fixed, or the compiler can be fixed. The only difference as I see it is that the C++ spec does not expect the compiler to be fixed.
Did I misunderstand your post?
I simply cannot imagine a situation where you can’t find an alternate solution to a problem with the compiler. Even if the compiler would optimize your intended solution away, you can write an asm! macro.
It sounds to me like you have simply decided that one language cannot do what the other can because you personally would not do it, which is very silly.
If this is not the case then I restate my request for an example, for the third time - an example would prove the point you are not making through explanation.
Can you provide an example of such a program that can’t be fixed at the program level like a C++ example?