zephod
zephod on Hacker News
Thanks for the reply! I gave it a solid week at the start of this month, about 3 weeks ago.
The only other thing I didn't like (and this is subtle, but I had not realised that I took it for granted): In Cursor, you can close and reopen a tab, and the undo history is kept. Working on a large repo, this comes up surprisingly often.
Save -> Close -> Assume everything is fine -> Do something more -> Oh no! That was a mistake! -> Cmd+Shift+T -> Undo. Cursor will comply; Zed says there's nothing to undo. So you're back to reverting chunks of code in git.
I will try Zeta again shortly. The biggest thing I'm looking for is that I can move between files and the context of recent changes persists, and the assistant treats it has highly relevant. Comes up a lot when refactoring.
I tried Zed for a few days and loved it, but had to switch back to Cursor because I've become dependent on Cursor Tab.
The problem is that Cursor Tab seems kinda psychic, and I didn't realise how conditioned I'd become to just expressing a few keystrokes in the right place and have Tab pick up my intentions. If you're refactoring, you can move between files and it'll remember what you just did in a tab you just closed, and work out how to make the same changes here.
It's also really good at picking up patterns and the right imports from the whole repo. It seems to be working with a much larger, more persistent context.
I tried Zed AI, Copilot, and Mercury. All three seemed forgetful after a year of Cursor Tab. I wish there was a fix because literally everything else about Zed was an improvement.
This lends even more weight to the theory that Massive Attack’s singer is, in fact, Banksy.
We spent our first year as a startup hacking on laptops in the attic of Smithfields, along with a dozen other startups. No idea if Innovation Warehouse is still up there[1]. If you arrived at work early enough they'd still be hosing the blood off the tarmac from the early morning market.
Most startups moved out to WeWork as soon as they could turn a profit. But hey, it was cheap office space in super-central London.
[1] https://www.facebook.com/innovationwarehouselondon/
I have many happy memories of weeks at Herrang. In fact I got offered my first job in open source there after a chance meeting, and my first startup can trace its origin to some conversations with other hackers in between dance classes.
Let's be clear - this affects client-side apps which include the template compiler (ie. the full vue.js bundle). Right? So apps built with Webpack, and using vue.runtime.min.js should be safe?
I'd imagine that represents the majority of Vue apps in production, but I might be wrong.
I think virtualization is a fancy word for cloud.
$3.8B? The average subscription amount is slightly less than $10,000/month...
Offtopic, but does anybody know how the diagrams in this article were generated? I'd love a simple piece of software to generate beautiful, straightforward pictures like this to explain architectural problems.
I'd like to listen to this as a podcast later -- any idea how I can get hold of it, without running a Flash video player in a desktop browser?
My feeling is that a simple revenue multiplier doesn't work as a seed stage business valuation.
For example, how does this work for pre-revenue SaaS startups valued $1M-$5M during seed? Even if they've started generating revenue, much of their value comes from the long-term network effects and potential to create a market (right?)
What data do you need? This is empirically observable. Half the people in this thread are giving you examples.
I took over a domain which had previously 301-redirected HTTP:// to HTTPS://. It caused us no end of trouble getting the alpha site online -- obviously we set up SSL but we didn't realise it was the _first thing we'd have to do_.
It also caused half a day of confusion to understand why some of our web browsers were still failing to connect and others could see the alpha site (because they'd never visited the previous 301 site at that address).
It did say [Flagged] for a while, though. I was reading the discussion and it bounced in-and-out of existence while I was trying to contribute. The Reply button would disappear; at one point the link and title were removed, then restored. I guess this is what the Vouch system is for.
Intuitively I'd agree, but I was surprised at how many people/friends/colleagues didn't know what I was talking about when The Internet's Own Boy was released. If they weren't readers of Hacker News they almost certainly didn't pick up on the story. Again - anecdotal.
This is so sad. I wonder if Noah has considered moving abroad for a bit - in my experience, very few people in the London tech scene know who Aaron Swartz was, or if they've heard the name they will struggle to remember the story behind it. Maybe people will disagree, but I don't think the story had quite the same cultural resonance outside the USA.
I wasn't at all surprised to see this is a funded startup -- it's had a lot of effort put into the design and execution, and it just screams desperation to me. I imagine somebody is under a lot of pressure to hit their growth metrics, and they probably convinced themselves that throwing out the rulebook is ok.
But you could _delete it today_ and it would not be lost. Right?
No idea why this was downvoted. Perfectly legitimate question given unclear circumstances.
> It is possible, or even likely, that a repository switch could lose that history on a project like emacs.
Surely the "D" in DVCS means that many thousands of copies of the project history would be available around the world?
Trying to scroll your website on a Mac trackpad causes it to jump around like crazy. Did you install some too-clever-for-its-own-good Javascript? (Has anyone else noticed this is an increasing - and annoying - trend?)
Does anybody have an idea how I could get a print of this?
I feel the same way, and at this point I'm just holding out for some kind of iPhone Nano product line next year.
What puzzles me is that I don't know anybody else who feels like this. Most people are surprised at me, or don't seem to notice that they suddenly need two hands to operate their smartphone.
I believe the author was making the point that the names are overly descriptive ("Elastic Compute Cloud" -- not at all innaccurate, but not easy to grok; the less descriptive "Amazon Virtual Servers" is easier for a newbie to recognise and intuitively understand).
Like most entries on the list, Amazon S3 _is_ a new concept but try explaining it to somebody without mentioning FTP -- you'll see what I mean.
What was that quote about the only hard problems in Computer Science?
I find it interesting that you're getting consistent downvotes for saying the same thing my startup's legal counsel has repeatedly said about the AGPL: Be extremely careful. Assume nothing and write defensively, because the nature of an "integration" is too vague to risk a company's infrastructure.
I get the impression others here are happily screwing around with AGPL integrations with nothing to lose.
I think that's just a question, as a meta-question would be a question about somebody else's question(?)
Nope, just shows me the landing page with the book cover.