pauleveritt
Joined 11 years ago
Joined 11 years ago
I will say though: I hope we keep you and earn keeping you, because you are EXACTLY our bulls-eye. Folks who still believe in code and coding and still want to put their hands on the wheel sometimes.
About compared with Codex, we have some tricks up our sleeve that are actually valuable for the target market we're going after: folks that want to understand and own what they've done. Watch for the videos we'll be doing (and look for my shining face in the PyCharm channel.)
On the last point...yes, the downside of choice is choice.
The answer is more like the obvious one...our category is getting redefined, at hyper-speed, and all of the players are all over the map trying to sort this out.
I like what we're doing with JetBrains Air. We know what we bring to the table, who it's for, and we're doubling down on developers and development.
That said, CPU fan on Markdown is not cool. Want me to look through it with you?
I'm happy about our Air launch because we're being AI "realists"...neither too much sunshine pumping nor too much skeptic. We're doubling down on developers and development, both when you type and when you don't.
On to the point..I can promise the PyCharm is doing some pretty massive non-AI stuff on the deterministic side. I think determinism is the best path to trusting the code generated by the box.
About the terminal, honest question...is that because you are looking at code less and less? Writing code less and less?
After using Air in PyCharm, it's some good stuff. It's re-imagined for this hybrid world. But my question for you, honest question: do you think you still want to look at code? How about write code? If so, what are some things you'd do, if you were in charge of our IDEs?
We have put a lot of thought into how we can add value for the workflow you just described. Here's the way I think about it: FSD for a car. Can you imagine trying to sell a car without a steering wheel? I still want to code, I still want the deterministic side, even in cases where I'm letting the machine do the work.
But there's still a group that needs to own the result, who still read code and write code. Folks who still believe in developers and development. This group might not be loud in SV, but they are big out in the world.
I'm a Python advocate at JetBrains and our team runs into folks like this all the time.
I've been enjoying using Air inside the IDE as a way to get the acceleration without giving up coding. I get the speed side from the agent and the trust side from the deterministic IDE.
With template strings, the symbols in the HTML string a just like Python code. Static analysis tooling can step in and do things.
We have ambitions to start an interoperability movement in Python HTML, so htpy and tdom could agree on a common Node structure.