Just another fence for monkeys :)
Zed is our office
71–80 of 343 posts
Re: Zed is our office
#72Earlier quoted context omitted.
Often projects need a history of stable checkpoints, and source control is one way to provide that.
Yes, but does it need all the ceremony surrounding it? If, every time I saved the file, the changes were analyzed and committed to git, and a useful commit message included, and commits squashed automatically and pushed and tested and tagged (using magic, let's say); if the system existed in the background, seamlessly, how would our interactions with source control and with other developers look?
automated commit message will tell you the "what" not the "why".
In any circle of "what makes a good commit message and why even do it" discussions, invariably the recommendation is to explain the "why" and leave out the self-evident "what".
If your stance is that commit and commit messages can be automated away then we might as well not even have them.
I don't share this view, but yeah in this world we don't need AI to do things that shouldn't be done in the first place.
Re: Zed is our office
#73I could imagine that in ten years git will feel strangely slow and ceremonial. Why not just continuously work and continuously deploy live-edited software
Imagine if someone clicks the deploy button when you're in the middle of typing something and then the service goes down due to a syntax error. To prevent this, we will need some sort of way to set a global lock to indicate that "I'm not done typing yet" and you can only deploy once everyone has released this lock.
Or you don't deploy unless it makes it through at least testing, and a build started while someone was editing the code would probably fail fast unless you coincidentally hit the button right when it's valid, but wrong, code.
Re: Zed is our office
#74Haha: Can't find a good Windows laptop. It's true, most of them are bad. Galaxy Book5 Pro or Microsoft Surface are OK.
Ever since Apple Silicon macs came out, it's been a real struggle. Almost 6 years later and there is still nothing on the market that:
* Has the same level of performance
* With the same or better battery life
* With the same quality of screen
* With the same quality of speakers and touchpad
* Runs as quiet or as cool
as the Apple Silicon macbooks. If you add in "needs to be able to run Linux" your choices go down from maybe 1 or 2 to 0.
They all have some sort of compromise. Either the speakers, screen, keyboard, touchpad, build quality, battery life, or thermals.
I have a Surface Laptop 7 with the Snapdragon X Elite, and it's pretty close. Checks the boxes for Screen, build quality, and touchpad. Loses out on speakers and battery life, and the fans need to run a lot more than my M4 Pro MBP does. It also loses on performance, and it doesn't run Linux. Windows on Arm also still has a lot of little quirks and bugs that start to become daily annoyances.
It's incredibly frustrating. I want, essentially, my 14" M4 MacBook Pro, but in a Linux laptop, and there's no OEM out there that's fulfilling that need without compromises.
Apple keeps pulling ahead in silicon and every other laptop OEM is just being left in the dust, shrugging their shoulders, and putting out the same old 1200p 16:9 plastic garbage they have always been putting out.
Re: Zed is our office
#75Earlier quoted context omitted.
It could be easier, but it is supported AFAIK: https://github.com/zed-industries/zed/issues/8260#issuecomme...
Unfortunately, we no longer support self hosting. We're planning on reintroducing it once we've polished the single player experience a bit more :)
Thanks for the update. Can't wait to hear more!
Re: Zed is our office
#76Don't want to sound negative, yet when I read "it's in our DNA", I immediately lose interest.
Re: Zed is our office
#77You guys need to figure out how to create Slack shared channels in Zed and we're all switching until they won't be needed anymore.
Can you share more on this. While I do not work at Zed, I'm curious to hear more about this use case for my own company needs.
Your company has a user pool, you sign a BAA or start working with a partner company that has their user pool. Instead of creating slack accounts in both you can share external slack rooms that only people that are invited in/from their respective orgs can join without having to co-mingle employee user pools.
Re: Zed is our office
#78If you've been a developer long enough, you might recall the teletype package for Atom—both built by Zed's founders. I first experienced this in SubEthaEdit in 2013 or so, but it has been around since the early 2000s : Appropriately working together on a truly collaborative tool, Martin Ott, Martin Pittenauer, Dominik Wagner, and Ulrich Bauer of Technische Universitat Munchen won the Best Mac OS X Student Project for…
SubEthaEdit was a very inspiring software project for me. The fact that a small team could, in a few months, produce an amazing app that solved real problems and gained notoriety was amazing. As time goes on it feels like much of the low hanging fruit opportunities in software is disappearing faster and faster. I'm also a fan of Zed and everything they're doing, but it's notable that shipping next-gen editor software…
> but it's notable that shipping next-gen editor software takes a lot more developer effort now than it did in the 2000s.
Yes, the scope increase is vast, due to more languages, more tooling, more features, higher expectations, and more competition.
Re: Zed is our office
#79Earlier quoted context omitted.
It's just pair programming when you're doing it on code so if you can bear pair programming you'll be fine. Personally, I hate it.
Pair programming usually has a single "driver" on the keyboard to keep things controllable. Here, everybody is driving: "dozens of cursors are concurrently editing the same file in real-time."
my understanding is that this is the dynamic in modern college classrooms. everyone opens a big shared google doc for notes and they all collaboratively edit a set of notes in real-time.
or at least that's what i've heard, no idea if they actually do it.
it is nice to see a crdt backed editor tool for markdown and code though. gdocs markdown support has been lacking for years.
Re: Zed is our office
#80It would have been good to include a link to the collaboration docs https://zed.dev/docs/collaboration in the article. There were a lot of links in that article and a lot of assumptions that I knew how things worked. And I daily drive and like Zed, but I had so many questions.