This time we're on our own in the marketplace with no big revenue-generating company supporting us. We'd like to be as open as humanly possible while being able to build a defensible business around the editor.
We plan to make Zed extensible via WebAssembly, but we're taking a different approach than we did with Atom.
Our goal is to make Zed fast, stable, and collaborative first, extensible second. We'll be taking a more conservative approach with our APIs to ensure we can preserve our core values even as users add extensions.
Our goal is for Zed to have the lightweight and snappy vibe of Sublime with the power of a more full-featured IDE. These objectives are obviously in tension, but I think we can build something that balances them well. A collaborative IDE that feels fast and powerful.
Founder of Atom here. We're building the spiritual successor to Atom over at https://zed.dev.
We learned a lot with Atom and had a great time, but it always fell short of our vision. With Zed we're going to get it right. Written in Rust, custom native UI framework, engineered to be collaborative. Just starting our private alpha this week, so the timing of this announcement feels quite fitting.
An embedded scripting language is only part of the story. Think about all of the APIs the browser exposes. For starters there's the DOM... there's no UI toolkit more that's more universally understood. Then there's CSS. Look how many Atom themes there are out there because people can tweak styling with a system they already understand. Then there's the long list of other standardized APIs. WebRTC, fetch, WebGL. Chromium is a very full-featured cross-platform environment that offers us more than embedding a scripting language would. I'm not denying it doesn't come with some negative trade-offs, but I do think those will diminish as Chrome improves and we improve our usage of Chrome... we're also dropping critical components to C++, which Electron makes it easy to do, so over time Atom will evolve into an increasingly "native" application with a cross-platform standards-based interface layer. The overhead of that layer will always be there though.
Using web technology was less about making development easier on us, because in many ways it made it harder. Web technology is about enabling extension authors to use a powerful and familiar technology to achieve their goals.
Takes political mechanisms to enforce those costs on polluters, so it's really important for solar to beat coal even in the presence of this hidden subsidy.
I'm happy about the changes that are being made to JavaScript. For new code, stick to a modern subset of the language and enforce it with a linter. It's not ideal, but I'd rather live in a world where ES6 and ES7 features exist than one in which they don't.
> This suggests another problem they have is a huge constant, in addition to the algorithmic one --- "thousands" shouldn't be something a modern machine would choke on, if updating positions is a simple operation like increasing their offset by 1 after a character is inserted.
As I mentioned in the article, a big part of the cost was updating a different interval storage structure as the markers were updated since the absolute positions approach left us no way to defer it.
Very pleased to hear this. I'd much rather have resources funneled into making v8 and JavaScript in general more performant. It already has so much momentum behind it.
You can disable hardware acceleration in the React editor in the settings view to get subpixel anti-aliasing back at the cost of performance. A frustrating trade-off for us, to be sure.
Have you tried our vim-mode package? It's not perfect yet, but it's getting closer. It's built around an op-stack and is designed to be compositional. We definitely understand the points made in this article, and it's very possible to implement modal editing in a package. Extensibility vs compositionality is a false dichotomy.
I just wrote this line about two hours ago and my tests weren't thorough enough to catch the bug it introduced. Just when I thought I knew JavaScript. Thanks for saving me some time.
I also found his talk fascinating, but the paper he referred to was a bit unapproachable for me. Any suggestions for resources that could help get me more comfortable with reading and understanding type calculi?
JavaScript is fine. We could do a lot worse. We could also do a lot better. The point is that regardless of arguments hypothetically better languages, we are converging on a ubiquitous scripting language, and its name is JavaScript. If you don't like it, use ClojureScript or CoffeeScript or whatnot. Resisting the inevitable is only going to cost you time and mindshare.
My anecdotal experience says there's a ton of demand for skilled programmers. If we're graduating CS students that don't have the skills that tech companies need, that's a problem with quality rather than volume.
It boggles my mind that Google isn't making Chrome OS more developer-friendly. If they could bring developers on board, they'd have a good beachhead for taking over the desktop market. They should enable us to build privileged native applications that use the DOM for their user interface but have unfettered access to the underlying OS just like any other application would.
I actually see there being a lot more room for improvement in DOM performance than in JavaScript. Most of the time, poor DOM performance is a bottleneck in my code long before poor JavaScript performance, now that JS VMs are so fast.
If it doesn't have all of Ruby's weird features, claims of speed don't matter, because it's those weird features that make Ruby slow and hard to optimize.
We need more of this. We need post-secondary education that focuses on giving people real-world, practical skills. There's only so much room in our economy for psychologists and communications majors.
Of course it's a systemic problem. But individuals are components of that system. If you don't punish people who engage in fraud, you remove a valuable disincentive against fraud. So while the system as a whole needs to be reformed, making individuals take personal responsibility for wrongdoing is part of that.