Honestly the whole Silicon Valley shtick is becoming old. The fake positivity, the quirky writing style, the "I think the most important quality is sticktuitiveness" linkedin-esque bullshit. Not to mention the cargo-cult that is so obvious in every GPT-wrapper startup.
This was mostly born out of counter signalling the businesses that valued serious people over competent people in the 20th century.
But, like with all things, the pendulum has swung too far in the opposite direction. I believe the next wave of tech countersignalling will be people who actually do take themselves seriously, maybe even dress in suits, etc..
I noticed that as well and it oddly made me sit for a minute to think about it. I ended up deciding that it landed a bit more 'real' and unfiltered. Could be interpreted many ways. Nobody knows the actual why but (possibly) Jack.
I've been amazed by this jam. It's like bigger and better every year (in terms of jams going deeper and deeper).
I imagine we're 5 years away of "Make your own OS, language, compiler, VM and game in 12 minutes, 36 seconds. Extra points if you gave yourself a stroke."
Create a simulation of a universe with arbitrary physical laws, have it evolve sentient life, and submit the first video game they develop which matches the theme. The theme this year is "rotations". You have 48 hours. Go.
I agree that’s Zed is very nice but a ticking enshitiation time bomb.
However, you do see how this autocomplete “feature” and its whole copilot everywhere strategy, is about M$’s roi of its ai investment right?
So if you have a problem with VC money you should stop using VSCode as well.
Of course they will just invent more accounting terms, like they do with azure, to hide how much money they are losing on it.
It depends, it can be useful to easily debug some flows. It’s also sometimes better for interactive applications where pausing the execution would break the interface.
They should, but if given the option to only exclusively use one or the other, I would never in a million years pick it. Because I have put in a tiny bit of effort into understanding how to use a debugger.
Most of them provide you with a feature list that's a strict superset of printf, because they let you set conditional non-blocking breakpoints that can have side effects. Which is perfect for the situation you've described - logging state without blocking. Then you can block and look through that state + any additional relevant info.
