Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
nathansobo
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
nathansobo
4y ago
Thanks very much for your kind words and wishes!
32.
▲
by
nathansobo
4y ago
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.
33.
▲
by
nathansobo
4y ago
We plan to monetize collaboration. Zed is a collaborative platform disguised as a world-class code editor.
34.
▲
by
nathansobo
4y ago
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 app
35.
▲
by
nathansobo
4y ago
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 righ
36.
▲
by
nathansobo
8y ago
I miss the old Whole Foods. I feel like the shopping experience has gone downhill in a variety of ways.
37.
▲
by
nathansobo
9y ago
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.
38.
▲
by
nathansobo
9y ago
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.
39.
▲
by
nathansobo
10y ago
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.
40.
▲
by
nathansobo
11y ago
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 exi
41.
▲
by
nathansobo
11y ago
> 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 incr
42.
▲
by
nathansobo
11y ago
Yeah, still more work to do. There are other things that are slow in that keydown event. We'll get there.
43.
▲
by
nathansobo
12y ago
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.
44.
▲
by
nathansobo
12y ago
Is the talk online?
45.
▲
by
nathansobo
12y ago
Look at your body in the mirror.
46.
▲
by
nathansobo
12y ago
Agree for the most part, so long as there's sufficient liquidity in the target fiat currency.
47.
▲
by
nathansobo
12y ago
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.
48.
▲
by
nathansobo
12y ago
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 ve
49.
▲
by
nathansobo
13y ago
Both behaviors make sense in isolation. It's not always so easy.
50.
▲
by
nathansobo
13y ago
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.
51.
▲
by
nathansobo
13y ago
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?
52.
▲
by
nathansobo
13y ago
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
53.
▲
by
nathansobo
13y ago
The examples for these kinds of frameworks always show you data binding for scalar values. That's easy. What's the story for more complex updates?
54.
▲
by
nathansobo
13y ago
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.
55.
▲
by
nathansobo
14y ago
Tried it. You spend way too much time solving problems that are already easily solved in the existing larger ecosystems.
56.
▲
by
nathansobo
14y ago
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 applic
57.
▲
by
nathansobo
14y ago
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.
58.
▲
by
nathansobo
14y ago
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.
59.
▲
by
nathansobo
14y ago
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.
60.
▲
by
nathansobo
14y ago
I think Apple may end up eventually paying for their treachery.
More ›