Hacker Newsnew | past | comments | ask | show | jobs | submit | timvdalen's commentslogin

Is it? If you're not interested in limited liability it's 85 euros to file for a company. If you do want limited liability, you have to visit a notary to found, but even that's only like 500 euros. Sure, you have to do your taxes every year and that's annoying, but it's not _that_ hard.

> you have to visit a notary to found

Why is that even necessary in the first place? Thats what people hate about bureaucracy. Why can't we just submit a form somewhere from home and someone looks over it from a queue. In the meantime you are allowed to start your business already. Bad process here. No process is 100% times better. An async one with forgiveness is getting you 80% there.


What kind of business would you like to run that it needs to be established today and cannot wait a few weeks? There are many repercussions, social security and tax wise. Do you expect a government to keep up with a free-for-all form that creates companies ?

What's stopping you from just running your business while waiting before the notary has time for you?

It's ultimately the same thing; if in your async queue system your application was denied you'd still be liable.


I'm really used to my Graphite workflow and I can't imagine going without it anymore. An acquisition like this is normally not good news for the product.


I really wanted to give them a try actually, now I definitely won’t.


Any ways I could convince you to?


We currently let loose Gemini, Cursor Bugbot, Qodo, and even Sentry started reviewing PRs now.

My usually prefer Gemini but sometimes other tools catch bugs Gemini doesn't.

As someone who has never heard of Graphite, can anyone share their experience comparing it to any of the tools above?


I've never used Graphite's AI features, so I can't compare!


Graphite predates AI code reviews. Obviously includes it now, but the original selling point was support for stacking PRs.


Graphite isn’t really about code review IMO, it’s actually incredibly useful even if you just use the GitHub PR UI for the actual review. Graphite, its original product anyway, is about managing stacks of dependent pull requests in a sane way.


Their AI review is sub par, but everything else is really good.


Our amazing journey...


Don't worry - we're not going anywhere. The goal is to continue building and maintaining the product.


Heard on the worry, but I can confirm Graphite isn’t going anywhere. We're doubling down on building the best workflow, now with more resourcing than ever before!


We’ve heard this many times before with other acquisitions so don’t be upset if people are a bit skeptical.


Supermaven said the same thing when they were acquired by Cursor and then EOLed a year later. Honestly, it makes sense to me that Cursor would shut down products it acquires - I just dislike pretending that something else is happening.


we are a 70 person team, bringing in significant revenue through our product, have widespread usage at massive companies like shopify robinhood etc, this is a MUCH MUCH MUCH different story than supermaven (which I used myself and was sad to see go) which was a tiny team with a super-early product when they got acquired.

everyone is staying on to keep making the graphite product great. we're all excited to have these resources behind us!


Not your fault at all, but there is a ton of precedent to be skeptical that these pronouncements end up being accurate.


The biggest challenge is that an acquisition like this makes relying on the acquired product a giant risk for us, so our general policy is to stop relying on something once it gets acquired and try to migrate to something else, because it's just way too disruptive to find out a year later it's getting sunsetted and then have a shorter timeline to migrate off.

It's happened so many times that it's just part of how we do business, unfortunately.


I've seen big companies cleave off tens of millions of profitable products on a whim pretty often....


Obviously what you need to say but the reality is that you’re not in control anymore. That’s what an acquisition is.

If Cursor wants to re-allocate resources or merge Graphite into to editor or stagnate development and use it as a marketing/lead gen channel, it will for the business.

Anything said at time of acquisition isn’t trustworthy. Not because people are lying at the time (I don’t think you are!) but because these deals give up leverage and control explicitly. If they only wanted tighter integration, they could fund that via equity investment or staffing engineers (+/- paying Graphite to do the same.) Companies acquire for a reason and it isn’t to let the team + product stay independent


relax


"trust me bro" (6 months later) "An update about your graphite workspaces"


We're aligning our product catalogue to do what we've found is the best fit for what our customers want. We're also excited to announce a migration plan to our new service, PencilLead, and want to offer existing customers preferential pricing to our Professional Services team to assist with the migration.

We know this isn't what all of you want to hear, and we've spent the last year really evaluating this deeply. At the same time, we're glad you're part of our journey to the future of agentic AI and we think you'll find it's the best alignment and fit for you, too, long-term.


There is literally nothing anyone can say to convince me any product or person is safe during an acquisition. Time and time again it's proven to just not be true. Some manager/product owner/VP/c-suite will eventually have the deciding factor and I trust none of them to actually care about the product they're building or the community that uses it


> Cursor acquires Supermaven.

> "Will the plugin remain up? Yes!"

> https://supermaven.com/blog/sunsetting-supermaven


Doesn't getting acquired mean that you no longer have the authority to confirm that?



> I can confirm Graphite isn’t going anywhere...

sweet summer child.


mhm


LOL. Just by bayesian logic this statement makes it more likely that it will go to trash.


That discussion is for the original announcement of the price changes, they're now going back on that announcement


whoops, too many dupes. updated. Maybe look for the discussion yourself before submitting.


Thanks! I did, but must have missed this one, thought the announcement was more recent.


Our current GitHub bill is $90/month, this would add an additional $700/month. I don't see how this doesn't cause a mass outflux.


How much do you pay for the servers that run actions? Is it much more than $610? Then it kinda makes sense.


No it's much less. Our runners are hosted in AWS ECS, you'd be surprised how affordable you can make that given the right optimizations (which is probably why GH made this decision).


Curious: Can you expand a little bit on your usage? $700/month equates to 350,000 minutes. Are you just running a truck-load of different Actions, or are the Actions themselves long-lived (waiting on something to complete)?


Just a lot of different actions, none of them long-lived. It's CI/CD for a large monorepo maintained by a relatively small team.

We use feature branch deployments, so we trigger a lot of builds.


We'd be at roughly $700/month at current usage.


Wow, just plain 500s on customer sites. That's a level of down you don't see that often.


Yeah that's a hard 500 right? Not even Cloudflare's 500 branded page like last time. What could have caused this, I wonder.


"A cable!"

"How do you know?"

"I'm holding it!"


I hope it’s not another Result.unwrap().


maybe this would cause rust to adopt exception handling, and by exception I mean panic


Mine [0] seems to be very high latency but no 500s. But yes, most cloudflare-proxied websites I tried seems to just return 500s.

[0] https://www.merklemap.com/


A precious glimpse of the less seen page renders.


So. I don't understand the 5 nines they promote. One bad day those nines are gone. So they next year you are pushing 2 nines.


Its just fabricated bullshit. It's how all the companies do it. 99.999% over a year is literally 5 minutes. Or under an hour in a decade, that's wildly unrealistic.

Reddit was once down for a full day and that month they reported 99.5% uptime instead of 99.99% as they normally claimed for most months.

There is this amazing combination of nonsense going on to achieve these kinds of numbers:

1. Straight up fraudulent information on status page. Reporting incendents as more minor than any internal monitors would claim.

2. If it's working for at least a few percent of customers it's not down. Degraded is not counted.

3. If any part of anything is working then it's not down. For example with the reddit example even if the site was dead as long as the image server is still at 1% functional with some internal ping the status is good.


Funnily enough an hour in a decade on a good hoster, with a stable service running on it, occasionally updated by version number ... it might even be possible. Maybe not quite, but close, if one tries. While it seems completely impossible with cloudflare, AWS, and whatnot, who are having outages every other week these days.


Unlike the previous outage, my server seems fine, and I can use Cloudflare's tunnel to ssh to the host as well.


Yes Claude is down with a 500 (cloudflare).


At least they branded it!


its like someone-shut-down-the-power 500s


Another VS code fork?


Hah, one of the apps I published is still in there, fun to see


The Changelog recently did a long form interview with this guy: https://changelog.com/news/refactored-in-prison-0X1D


Me too, I hope there will be a replacement with the same low friction.

I've been using IFTTT with RSS feeds to add serialized stories to my Kobo as they release.


They should be able to change it with fairly minimal changes. I managed to modify some things to proxy articles from Omnivore to it, and the functionality remained largely the same across the two services.

They'd have to implement some kind of login, but they they should just be able to build some kind of converter between whatever format and the format that is expected by the Kobo device.


Could you share the flow if someone wanted to replicate it for their own Kobo?


Yes, but it currently depends on Pocket working.

I have an RSS feed from RoyalRoad that new episodes come in on. Using IFTTT, I have an action set up to, whenever a new item comes in on that feed, add the _URL_ of it to my Pocket account. Then, Kobo just syncs the Pocket articles automatically, and the new episode is added.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: