Oh good lord. Spare us the beatings of the chest and rending of the garments. "crafting code by hand" like some leftover hipsters from 2010s crafting their own fabric using a handloom. It's fucking code. Were there similar gnashing of the teeth and wails of despair when compilers were first introduced?
> Were there similar gnashing of the teeth and wails of despair when compilers were first introduced?
Yes, at least according to ChatGPT:
"Compilers didn’t arrive to universal applause; they arrived into a world where a chunk of programmers absolutely believed the machine could not be trusted to write “real” code—until the productivity wins (and eventually the performance) became undeniable."
compiler is deterministic, coding models are not. compilers have been unit tested and will generate same output for a given input. They are not the same things.
So, there's a big qualitative difference in whether you can trust the output.
You can either "just believe", and prepare for inevitable, nasty surprises down the line. Or you can verify in ways you don't have to with stable compilers, eating up most of, if not more than all the efficiency gains you felt you had by using the LLM.
The two aren't comparable even remotely. One is a tool, the other is a slot machine. One allows for a new layer of abstraction, the other allows for a new layer of imprecision and hoping for the best.
Yup. Even if you treat the LLMs as just a question answering, brainstorming, code parsing, doc creating bot, it's already a major quality of life improvement for engineers over whatever we were doing before it existed.
My experience on r/programming came as a surprise to me. I know that not everyone in the community is sold on LLM based coding, and I was fully prepared for some pushback. But I was not prepared for the outright hostility and vitriol just for recounting my actual experience with LLM coding as a practitioner. I wrote up the post since it needed to be longer than a reddit comment and I was not feeling the need to engage with that level of negativity in the comments anyway.
> "Is there any proof that actual people use and value Google and Amazon assistant more than Siri?"
This is a common confusion among iPhone users. I suspect the reason is that if all you're used to is Siri (and it's myriad disappointments), it's hard to conceive of the the quantum leaps that is Google Assistant in product polish and usefulness.
First and foremost is the near flawless voice recognition. I, with my India accent even, can just say things to my Android device (and now, my new google home) it just ... gets it. It's spooky.
Then, after it recognizes the question/request correctly, it is very likely to take the correct action with a high enough probability that it's now almost a surprise to hear "Sorry I don't now how to do that yet" when it does happen.
Outside of the active queries, there are things it does automatically that are at the level of what a particularly attentive human assistant might do for you.
It'll check your calendar and remind you that you should start driving for your 4pm appointment because the traffic is unusually heavy on 101 today.
Or that your flight tomorrow morning has been cancelled. It knows about your flight because of the confirmation email in your gmail account.
Remember, you have to take no action for this sort of reminders. Just have to opt in when assistant is setting itself up on your new phone.
There are myriad other such examples. It has saved my bacon numerous times. We're truly living in the future.
You nailed it. People think this technology is not that useful because they have only used Siri and Alexa. Use the Google Assistant and you will see it is very helpful.
I have used all three and can say from personal experience the Google Assistant is head and shoulders in front of the other two in UX.
Packet loss is happening at a lower layer (ethernet, wifi, mobile etc.). It's a property of the physical medium, not whether HTTP1.1 or HTTP2 is running at the higher layer.
The point of this blogpost is that design of HTTP/2 (specifically, multiplexing multiple http transfers over a single TCP connection) behaves badly under packetloss conditions.
