Live data from Hacker News

Show HN: Get Paid to Build Your Next Side Project

demandrush.com

131–140 of 473 posts

Re: Show HN: Get Paid to Build Your Next Side Project

#131

Earlier quoted context omitted.

Because GIMP has a lot of baggage: a very particular UI, a community of active users (many of whom probably like it exactly how it is thanks), and a terrible name.

So fork it. New name, new UI. Seashore was a try at this a decade ago. http://seashore.sourceforge.net/The_Seashore_Project/Screens...

I think the gp's point is they'd rather rewrite than fork. If you fork you lose the other devs esp as you diverge greatly. But you get all the baggage.

A lot of coders doing side projects do it for fun and to learn and that often means making their own architecture decisions (and mistakes) so they can practice that process and learn

Re: Show HN: Get Paid to Build Your Next Side Project

#132
post #82

Earlier quoted context omitted.

I think the photoshop vs gimp is a bad comparison, mostly because throwing money at gimp to make it better is a bad idea. It would be better to start from scratch. Now if you wanted to throw $400 for a photoshop like system to start from the ground up and work across all three platforms, I think you've got a great idea. You'd avoid the cruft, you could do subscription/pay-per-use cloud based filters, you could start…

What's wrong with GIMP? I use it every day and find it pretty good. On the MAC now it has lots of weird glitches but they seem pretty fixable...

GIMP is perfectly fine (for many use-cases), but its not what you or I think that matters.

Perhaps the best person to ask is a photoshop user who actually paid for it?

Re: Show HN: Get Paid to Build Your Next Side Project

#134
post #52

Photoshop license costs $348 a year. If 1000 people get together and put $400 each, you'll get $400000. That money could be used to leverage a Gimp to be more Photoshop-users friendly. Then you don't have to keep with the subscription model. You have a great piece of open source software available for everyone to use as long as they want. You can do another round to get more features added. This solves the issue that…

$400k pays for 3 people.. maybe a couple of more if you hire from a cheaper country.

If all GIMP needed was a few more developers to be competitive against PS, that would have happened by now.

You're seriously underestimating the amount of work GIMP needs to do.. and/or the amount of work that already goes into GIMP.

Re: Show HN: Get Paid to Build Your Next Side Project

#135
post #86
post #52

Photoshop license costs $348 a year. If 1000 people get together and put $400 each, you'll get $400000. That money could be used to leverage a Gimp to be more Photoshop-users friendly. Then you don't have to keep with the subscription model. You have a great piece of open source software available for everyone to use as long as they want. You can do another round to get more features added. This solves the issue that…

The time that went into Photoshop cost a lot more than $400k, I would guess between two and three orders of magnitude more. Even given that you would not have to start from scratch and that you know your target pretty much exactly and don't have to go through almost 30 years of evolution, $400k would not get you nearly close enough to Photoshop to make switching worthwhile. Also assuming starting with GIMP is a good…

While it would almost certainly cost more than 400k to build a replacement photoshop, the open source community would already be profiting off the fact that a commercial photoshop already exists, and has years of product professionals spending large amounts of resources to understand and cater towards their users.

Re: Show HN: Get Paid to Build Your Next Side Project

#136

Earlier quoted context omitted.

Affinity already has great Photoshop and Illustrator alternatives: https://affinity.serif.com/en-us/ The opportunity with Photoshop may not be to create another Photoshop clone, or add more features, but rather create smaller, specialized editing apps, that each target a subset of the Photoshop user-base, with perhaps less features. Look at how Adobe Lightroom cherry picked a few Photoshop and Bridge components, to c…

Where is the source code or even just Linux binaries? Otherwise Affinity isn't really relevant when discussing GIMP.

wasnt the question about replacing Photoshop?

Hate to break it to you, but not one person who uses photoshop uses Linux.

Re: Show HN: Get Paid to Build Your Next Side Project

#137
post #35
post #6

> GET PAID TO BUILD YOUR NEXT PROJECT > Choose a problem below to get started. Get paid to build _my_ next project or _your_ next project? This is clearly a two-sided platform, but the messaging seems conflated: the headline speaks to builders and the instructions speak to end customers.

It appears to me that this is a tool to identify a market / need that is not being met. There are people who simply want a product/service, no desire for ownership. They post what they'd be will to pay for it, as a customer, and you decide if it is worth your time to build it. Anyone? Am I understanding this correctly?

Oh, so you own it, in an open source way. Is that correct?

Re: Show HN: Get Paid to Build Your Next Side Project

#138
post #6

> GET PAID TO BUILD YOUR NEXT PROJECT > Choose a problem below to get started. Get paid to build _my_ next project or _your_ next project? This is clearly a two-sided platform, but the messaging seems conflated: the headline speaks to builders and the instructions speak to end customers.

I immediately thought the developer would post what they are currently working on (or intend to work on), and businesses would encourage more rapid development by funding it.

Re: Show HN: Get Paid to Build Your Next Side Project

#139
post #52

Photoshop license costs $348 a year. If 1000 people get together and put $400 each, you'll get $400000. That money could be used to leverage a Gimp to be more Photoshop-users friendly. Then you don't have to keep with the subscription model. You have a great piece of open source software available for everyone to use as long as they want. You can do another round to get more features added. This solves the issue that…

The Photoshop license is $10/mo according to Adobe's site. $120/yr. Also, $400k is, like, nothing in developer time (compared to what Adobe puts into their software, at least).

You have many hackers already donating their time to work on free software projects, that might be able to do more if they were compensated to do so. $400k is a lot of money to partially compensate people who are already donating much of their time, especially when you consider that you don't have to worry about paying for benefits.

Re: Show HN: Get Paid to Build Your Next Side Project

#140
post #123

Earlier quoted context omitted.

If I could count on the 999 other people, Kickstarter-style, I just might.

Well... Set it up

He'd also need the GIMP devs to cooperate: to provide tangible feature sets with timelines, part time PR for updating and managing the Kickstarter campaign, and an part time CFO for managing the sudden influx and management of $360,000 (minus Kickstarter and the payment processor's share), dev salaries, taxes, and such.

I would be curious if the GIMP dev team could reach usability parity with Photoshop on only that money. It seems a bit on the low side frankly (about a year's time of a good developer and UX designer, plus support staff).

Post reply on HN