Only at the very end does the article call out there is actually a performance aspect if you use panic and recover as intended.
> So it seems that panic and recover can be beneficial to performance in at least some situations.
Namely top level & centralized recovery handling. I'll also point out its important your panic recovery must happen in a deferred function if your kicking off new goroutines. For example, your server library probably has default panic recovery on the goroutines handling inbound requests, but any new goroutines you create as part of handling the request (e.g. to parallelize work), will not have this handling built in. See https://go.dev/blog/defer-panic-and-recover for more.
We’re seeing a clear divide where both competitive gamers and hackers are retreating into their own ecosystems, away from public matchmaking. Public matchmaking has simply become too optimized/lucrative to sustain trust or meaningful competition.
Private matchmaking and closed communities are thriving, raising the average skill ceiling in competitive. Similarly, hacking communities are evolving with easier forms of payment and distribution. The monetary aspects are huge. But most importantly, both cultures push each away. Your persona of someone who plays with integrity and crosses the competitive and hacker mentality is pretty much gone.
I vividly remember the difference intense hockey conditioning camps, sleep and recovery can cause. During these camp I pushed my heart, with many drills being 30+ seconds at max heart rate. Afterwards I was exhausted, chest felt terrible. But I was so tired, I didn’t have the usual movements at night, and had much longer deep sleep. The recovery the next day was so dramatic compared to prior workout sessions. Way less inflammation across my joints. As compared to sessions where I only pushed my heart rate to 30-60%
I’ll add that even if the papers we all wanted were more freely accesible, the replication and completeness of their described methods would be another source of slowdown.
Main problem is still just getting good quantitative data and metadata. Most biomedical researchers are motivated to “tell stories”. Few of us care about generating huge mineable data sets.
> Interestingly enough, it’s actually more efficient to send text as images: A 512x512 image with a small but readable font can easily fit 400-500 tokens worth of text, yet you’re only charged for 170 input tokens plus the 85 for the ‘master thumbnail’ for a grand total of 255 tokens—far less than the number of words on the image.
Sounds like an arbitrage opportunity for all those gpt wrappers. Price your cost per token the same, send over the prompt via image, pocket the difference?
For most non-perishables it’s the most time efficient in minimizing the number of trips. Also given how often I go, ~once a month, each time I get the same sort of novelty as a Trader Joe's for they will have swapped out many items.
If the “Lindy effect” holds true for the 911, it might be quite a long time before the 911 and its variants go out of style.
The same cannot be said for the cyber truck, and all of the other short lived prototype cars that have very harsh angular lines.
Yeah, this author sounds more of an up-and-coming software developer. The cited example is something that someone should be easily able to do in their day to day language.
The ability for chatGPT to essentially translate/expand your knowledge out to other languages (eg “how do I read in a file to utf8 again” ). It’s all just more leverage and power to solve the mundane, faster. The key point is you have to know the rough solution space already.
For the example the op gave, probably not for an adult. But younger kids might. Also for complex domains, I find that dreams enumerate more possibilities/scenarios than I would have if awake.
Not the guy you asked, but my guess is that they're are not interested in how and why the computer works [1].
They probably more interested on how the computers can work for them. These students most likely to work in the banking or finance sectors where the payments are good and bonuses are awesome. Don't got me wrong though, they are good students and engineers, but under-the-hood of computers are not their main interests or passions. For example, someone can become a car enthusiast but can't be bother to open the engine bonnet or pump the tires.
[1]CS 61C. Great Ideas of Computer Architecture (Machine Structures):
> So it seems that panic and recover can be beneficial to performance in at least some situations.
Namely top level & centralized recovery handling. I'll also point out its important your panic recovery must happen in a deferred function if your kicking off new goroutines. For example, your server library probably has default panic recovery on the goroutines handling inbound requests, but any new goroutines you create as part of handling the request (e.g. to parallelize work), will not have this handling built in. See https://go.dev/blog/defer-panic-and-recover for more.