131–140 of 185 posts
Earlier quoted context omitted.
I do exactly that since 3 years (git though without ftp), having almost stopped using Google Drive. Dropbox I don't use since 5 years or so ;)
If you want a fancy web interface on top on Git, FTP, SFTP, S3, whatever backend, I built this: https://github.com/mickael-kerjean/nuage
We'd been building the tech (realtime GraphQL on Postgres) for a while, but the HN launch gave us the initial visibility and a tremendous number of users, reviews. And within the last few weeks we have several users in production and enterprise clients too. :)
Depends on how you’d define success. My older brother did a Show HN for his startup, NanaGram, about four months ago https://news.ycombinator.com/item?id=17016374 The product’s now delivering family photos in the mail for hundreds of grandparents every month. They might not be making millions of dollars yet, but they are making some money and doing lots of good in the world by helping with elder loneliness. That’s a…
That is a great idea that not only makes you cash--at a very fair price--but also helps people connect in a genuine fashion.
Dropbox: https://news.ycombinator.com/item?id=8863
The first comment on that thread is a typical funny HN comment: “if you’re a Linux user and do x, y, z and connect the flux capacitor to the warp drive you can emulate Dropbox no problem”
"Congrats Dropbox" https://news.ycombinator.com/item?id=16660140
BrandonM: It's funny how often that comment—which I made as a 22-year-old undergrad—resurfaces. Someone even reached out to me 2 weeks ago because they wanted to use it in an article as an example of "the disconnect between the way users and engineers see software"!
I like to think that I've gained a lot of perspective over the last 11 years; it's pretty clear to me that point #1 was short-sighted and exhibited a lot of tunnel vision. Looking back, though, I still think that thread was a reasonable exchange. My 2nd and 3rd points were fair, and I conceded much of point 1 to you after your reply (which was very high quality).
Obviously, we have the benefit of hindsight now in seeing how well you were able to execute. Kudos on that!
Congrats on your success! I wish you nothing but the best going forward!
Zed Shaw's take on the matter. https://zedshaw.com/2018/03/25/the-billionaires-vs-brandonm/
I’ve actually had the exact opposite happen: my ShowHN posts got nowhere, but the product itself became successful. I’m sure that the opposite is also true as well, but figured folks needed to hear that, just because your ShowHN post got nowhere, doesn’t mean there’s not a market fit for what you’re building. It just might not be interesting enough for the HN crowd, or you don’t have any name-recognition. For those w…
It could be the way it's presented too. What does "headless Chrome as a service" even mean? When I look at the Github link, I actually understand what it does: "Severless Chrome on your own infrastructure. Each session gets its own clean Chrome context for total isolation. After the session is complete Chrome is shutdown. You can also think of it like a database connection where your app connects to browserless, runs…
Contentful ( https://www.contentful.com ) was originally a Show HN called StorageRoom: https://news.ycombinator.com/item?id=2616041 It's now a series C startup with over 200 employees and customers like Spotify, WeWork, Samsung, Nike, Jack in the Box, The British Museum (I work there)
I’ve actually had the exact opposite happen: my ShowHN posts got nowhere, but the product itself became successful. I’m sure that the opposite is also true as well, but figured folks needed to hear that, just because your ShowHN post got nowhere, doesn’t mean there’s not a market fit for what you’re building. It just might not be interesting enough for the HN crowd, or you don’t have any name-recognition. For those w…
so how do you compete with Google? Headless chrome is supported in Google Functions
- We've got some REST-based API's that make it dead-simple to interact with Chrome for the majority of the use-cases out there. Plus you're not restricted to having to maintain node-based infra if that's not your stack.
- A lot of good tooling has been developed, for instance a live-debugging tool that lets you visually see the browser (located here: https://chrome.browserless.io/).
- The nature of a lot of folks' business restricts them from using big cloud providers like Google, Amazon, and Microsoft. Just because one of them pivots into your market doesn't mean that they're going to squash you.
- Finally, I've written a driver + am actively involved in puppeteer's repos (plus others). So, in a way, when you sign up for an account you get support from me as well, which has a _ton_ of value if you've never done headless work.
Anyways, hope that helps
Earlier quoted context omitted.
It could be the way it's presented too. What does "headless Chrome as a service" even mean? When I look at the Github link, I actually understand what it does: "Severless Chrome on your own infrastructure. Each session gets its own clean Chrome context for total isolation. After the session is complete Chrome is shutdown. You can also think of it like a database connection where your app connects to browserless, runs…
Also you didn't respond to the person who did leave a comment. Tough to have a post take off that way.
EDIT: yeah, this is my bad. Totally missed it and it's a great comment too :(