There was a time when I built games entirely using Visual Studio 6 Edit and Continue. These were the days when debuggers were reliable. Nowadays, I treat the debugger’s output like a best guess: it’s probably right about local variable values and the call stack, but it sometimes has nothing useful to say, and very occasionally is actively misleading.
The 'actively misleading' part is a real killer. I've gone down deep, dark rat holes a couple times because the debugger lied to me. I'm 100% in the "use the debugger" camp, but I sure wish they felt a bit more solid. I haven't used one for a long time that wasn't pretty buggy.
Thanks for this -- have been using Cody a lot and just tried Windsurf on my hobby project. So far it seems immediately like a step up. Has anyone paid for it? The free version is doing good work.
If a company provides a service for free to enable selling something else, and that something else becomes illegal to sell, then it’s up to the company whether they want to keep offering the free service. They can’t continue doing things that are now illegal just because that’s how they made money in the past. No decision-making power has been taken away.
Actually playing doesn't work well on mobile, because you can only "left-click" and can't view inventory, chat, or do much of anything other than attack the cow and pickup the leftover entrails. Ah well, still a neat idea.
Google Apps Script can do all of this. Take the email body and put it into a Google doc, then export the doc as a pdf to drive and attach it from there to send.
Hard to say without more details, though it's certainly plausible.
There's other possibilities though. Like if the timing of other interventions is being delayed until the cardiologist is able to see the patient instead of deferring to a less specialized physician.
No, not necessarily. There's no indication of that whatsoever. The point was just that there's insufficient information to conclude much of anything about why this was observed. It could also be that PCI is over applied leading to increased mortality.
This is a more interesting take to me than others since it seems you’ve actually learned it?
I see the response later that you’d rather use whatever the team already uses, but could you explain this very strong opinion?
I maintained a 200,000 loc TCL codebase running the front end for millions of lines of industrial C spread over hundreds of machines. It was glorious. After moving on, I’m still struggling to figure out why TCL is so unpopular outside that domain. Other comments seem to boil down to not understanding the language or how to apply it. So what’s your take?
That does sound glorious. And, to be clear, I am merely an amateur (lover of) rather than experienced practitioner. It’s also the only lisp-like I’ve learned, and it gets a fair amount of credit from me on those grounds alone. At any rate, the opinion is very strong because 1) the pragmatic angle that I’ve already mentioned, 2) the tooling hasn’t kept up, 3) the performance isn’t worth fighting for (although it’s really still fairly good), 4) the footguns are gloriously just around the corner.
I don’t know if all lisps suffer from that last one, and I don’t know about you, but there seems to be a clever solution hiding in every line. I think it would take discipline to have a codebase that remained cohesive and in a “single language”
