Hacker News new | comments | show | ask | jobs | submit login
Show HN: Get Paid to Build Your Next Side Project (demandrush.com)
1100 points by hackerews on June 14, 2017 | hide | past | web | favorite | 451 comments



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 you get with subscription based services, which is that if you stop paying every month/year you loose access to the tool to do your work.

Instead of building yet another SaaS wouldn't be smarter for users to gather and pay for a software libre solution?


$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.


This reminds me of the joke about the economist who refuses to pick up the $20 bill on the ground because surely someone else would have already picked it up.


Sounds like the Alinsky bit in "Rules for Radicals" about working inside and outside of people's experiences:

"....In a similar situation in Los Angeles four staff members and I were talking in front of the Biltmore Hotel when I demonstrated the same point, saying: "Look, I am holding a ten-dollar bill in my hand. I propose to walk around the Biltmore Hotel, a total of four blocks, and try to give it away. This will certainly be outside of everyone's experience. You four walk behind me and watch the faces of the people I'll approach. I am going to go up to them holding out this ten-dollar bill and say, 'Here, take this.' My guess is that everyone will back off, look confused, insulted, or fearful, and want to get away from this nut fast.

From their experience when someone approaches them he is either out to ask for instructions or to panhandle — particularly the way I'm dressed, no coat or tie."

I walked around, trying to give the ten-dollar bill away. The reactions were all "within the experiences of the people." About three of them, seeing the ten-dollar bill, spoke first — "I'm sorry. I don't have any change." Others hurried past saying, "I'm sorry, I don't have any money on me right now," as though I had been trying to get money from them instead of trying to give them money. One young woman flared up, almost screaming, "I'm not that kind of a girl and if you don't get away from here, I'll call a cop!" Another woman in her thirties snarled, "I don't come that cheap!" There was one man who stopped and said, "What kind of a con game is this?"...."

https://archive.org/stream/RulesForRadicals/RulesForRadicals...


I lived off handouts for a year while I writing up my research results. Finished it and got a job through a friend. When I got my first paycheck, I went to an ATM and took out a $100. I was so disorientated about actually having some money in the bank that, when I removed my bank card, I left my money behind. I walked about 15 meters before I realised what I had done. I naively returned to the bank and went inside to explain what had happened. (I mean did I really expect the teller to believe me or be able to do anything about it?) There were two young guys at the bank's information desk handing in the money. I said "That's mine", took it and walked away. I wanted to give them a reward, but thought their good deed would have to be its own reward.


given that there are a lot of scams that start by giving the mark something in order to create a sense of obligation, it's not an unreasonable response


The trick to those is to take the thing and then not feel obligated to do anything whatsoever.


That's good in theory, but in practice the con men will ask for what they gave back and might get violent if you refuse.

I'd give up on ten dollars if it means not having to fight/argue this way on the street.


oh obviously don't get into a fight, but I see no problem in being annoying to con men if you can do so safely. It's not like you're gonna get decked straight away if you refuse to give it back. As always use your own judgement.


Some people have the human social impulse wired too strongly to do that.


Agreed. I don't believe you are implying this, but neither Saul nor I intend to state their reactions are unreasonable. Merely to indicate how divergent reactions can be in different populations and how this can be utilized.


I tried this and got exact same results in Budapest many years ago.


I am literally laughing imagining the Hungarian reaction to this. (Wife is Hungarian, and I lived in Bp for a few years.)


Well, get this. The first guy who took it was a well known politician, Deutsch Tamás now responsible for "the internet". You can't make this up.


The day trader who picked up the $20, ecstatic from his arbitrage win, puts down on the ground a $100 hoping for larger gains.


Or the high frequency trader who spends $20,000 on a machine to try to find all of the $20 bills on the ground before someone else does.


Yeah, this joke sums up just about every arbitrage situation I think I've found. I think, naw, it must be an illusion, because the market is so efficient...

Means I end up paralysed around starting new endeavours.


Yeah the market for open source is shit. You have tons of corporations deriving billions in total profit off the back of open source that contribute maybe a million back and feel that they have done some great great deed... like say Google. You could easily make the Gimp much much better with a few million in funding. The beauty of capitalism is exactly that it locks out this sort of behavior because of the way that corporations and consumers behave with their money... and how people relegated at to the lowly level of employee is forced to behave by the rules of working for that corporation and the small amount of money it pays for work which may deliver up to 10x its value, value captured by the shareholders.


And I think copyleft licenses offer a solution here: if you are worried that corporations (or rival corporations) might monetize your product (or derive any profit from it indirectly), licensing it under a copyleft license would make their lives very, very hard. It's near impossible, for instance, to keep an AGPLv3-licensed product within a walled-garden, hence good luck while trying to build a *AAS on that.


The issue is not to deprive corporations of profit. Profit is good. The issue is how they behave with the profit once they get it. They lock it up in the hands of the very few rather than distributing it far and wide so good stuff can get done all over the world. The concentration of capital or the good is the problem. The more it is concentrated, the more good that gets done is on the terms of the corporations rather than a scrappy hacker or an individualist or anyone else. That shuts down freedom to do, which is bad. That limits choice and freedom, to live how you want because you are providing a good. Rather than live on the terms dictated by those who hoard the capital. Which happens all over the world the way the current system is architected.


Who is profit good for?


For everyone. Who is profit not good for? Someone has chosen to pay the company for the good, that's their decision to do so. The company has provided the good. The consumer is better off because of it. And he or she has paid for the good. So yeah it's good for everyone.


> Who is profit not good for?

The wage slaves.


Profit is good for wage slaves. People may not agree that the wage slaves get their due share of that profit, but without profit, the wage slaves would be in a sorry state indeed. Their employer needs to be prosperous so they can be comfortable accommodating the employee's needs.


Why?


AFAIK this was the original intent of the GPL as well, but due to the common interpretation that "link" and "distribute" refer exclusively to their meanings within the context of traditional binary building and distribution (that is, they do not apply when a program is "distributed" such that its back-end is accessed through a web-based front-end), the AGPL was necessary.

IANAL


[flagged]


what's bullshit? That the GPL was written with the same aims as the AGPL? I fail to see any bullshit in the post you're replying to…


I wonder if anyone has ever thought of a law that would allow for large corporations to repatriate some of their overseas dollars tax-free, or defer corporate taxes they'd otherwise have to pay, provided they went toward altruistic purposes, where one of those altruistic purposes could be contribution to broadly used open source libraries.

Obviously a lot more of the details would need to be worked out to try and minimize how much companies try and game that to simply fund their own research tax-free, but I wonder if the type of behavior you're looking for could be economically incentivized given the right corporate tax legal reforms.


The problem is a lot of those "altruistic purposes" tend not to be so altruistic, when you look into why they do them. Take for example, when Google recently chose to donate a bunch of hardware to schools instead of giving their employees an annual gift.

Google gifted schools Chromebooks, which seems like an incredible act of charity. Except for the fact that you have to pay a subscription to Google to use them. Which means they really just managed to get a tax write-off while picking up more customers.

How do you ensure a company is doing something in the best interests of society or the charity or organization they are donating to, rather than in the best interests of themselves?


For an educational environment I would be hard pressed to name a more appropriate device than a chromebook. From a hardware perspective the Chromebooks are cheap, practically disposable. ChromeOS is open source, but also secure and easy to manage. And there is no subscription or license cost for the 'G Suite for Education'. Even if that were true, the schools would be under no obligation to accept the gift, so it's hard to see that this is some sort of problem with the state of the law.

Generally speaking, it's pretty difficult to tell if charities are actually being charitable, and there is no way to ensure it -- we can't mark each dollar's fall. But we do have laws that cover those sort of 'hidden catch' scenario; you can't trick people into a financial obligation. Is there some other loophole that you can identify?


ChromeOS is not open source. We need to stop spreading the misleading claims that Chrome or ChromeOS, as distributed widely is open source, because it is not. They are not particularly secure given how poorly policed the Web Store is (malware which can exfiltrate your browsing data is rampant).

And of course, as my source demonstrated, there is definitely a license cost to use Chromebooks in a managed environment, and it is not free for educators.

As the situation is _right now_, the law is probably fine, but I'd be against the parent's suggestion of allowing a loophole for them to get to repatriate cash tax-free for this sort of usage, because it's likely just going to work out in their favor, and not in ours or the public interest.


> Google gifted schools Chromebooks, which seems like an incredible act of charity. Except for the fact that you have to pay a subscription to Google to use them.

Do you happen to have a reference for this? G suite for education is free as far as I know and I wasn't able to find anything else that you might be referring to.


Check out this page for a start on Chrome device licenses: https://support.google.com/chrome/a/answer/2717664?hl=en

You can see an educational portal listing the cost of the management license at $30 here, which isn't really a complete picture, but demonstrates that we aren't talking about something they give schools for free: https://edu.google.com/products/devices/

Note that this is kinda of well-hidden, but that last link cites the "total cost of ownership" of a $149 Chromebook over three years as $588, which should give you an idea the difference between the hardware they give away, and the eventual cost of everything you need to deploy the suckers.

Schools is definitely big money for Google, it's just well-disguised as an altruistic endeavor.


> You can see an educational portal listing the cost of the management license at $30 here, which isn't really a complete picture, but demonstrates that we aren't talking about something they give schools for free

You need to show that those licenses were not included in the gift. And let's just assume that they're not that stupid.

> Note that this is kinda of well-hidden, but that last link cites the "total cost of ownership" of a $149 Chromebook over three years as $588, which should give you an idea the difference between the hardware they give away, and the eventual cost of everything you need to deploy the suckers.

For a budget windows laptop or tablet the hardware cost would be higher and the support cost unlikely to be lesser.

> Schools is definitely big money for Google

Schools are a tiny segment for Google that would not hurt them in the slightest to lose. The margins on low-end hardware are not exactly the stuff dreams are made of, and they really are making peanuts on ChromeOS. We can and should contrast this to Microsoft, who has been playing the "loss leader" pricing game in educational circles for far longer with far more success.


Also worth mentioning how iPads work in an educational setting. So many schools were so ecstatic to get iPads for students and embrace the future that they didn't stop to consider just how quickly an Apple iOS device can start to feel slow from OS updates designed for newer and more capable devices. The difference is pretty stark compared to a regularly imaged workstation which can last 5+ years.


Google doesn't need to charge to make a profit. Don't forget their primary business is advertising, so by getting more people to use their services, they gain. Also, by extending their reach to inside the schools, they effectively set up a way to "educate" kids to use their services.


Wouldn't this already be effective as long as the project was under the umbrella of an appropriate 501(c)3? Not necessarily the repatriation bit. I'm not a tax expert by any means so I am legitimately asking.

From a quick search, it looks like the IRS does sometimes allow businesses to make deductible contributions to a 501(c)3, but that it first attempts to determine if the business expects to receive a "substantial return benefit". [0]

The IRS seems to already have specific rules around "qualified sponsorship payments". [1]

[0] https://www.councilofnonprofits.org/tools-resources/corporat...

[1] https://www.irs.gov/publications/p598/ch03.html#en_US_201701...


One easy way around this is to do what all the NYC foundations do. That is, give to other people's charities, and they in turn will give to yours. That is only small potatoes compared to donating to a political campaign and taking the money you don't spend on the campaign off the table tax free. A lot more things make sense through that lens. I could imagine a situation where Google who doesn't benefit from every OSS project, gives to project that Facebook benefits from, and Facebook to one's that Google does ad infinitem.


I see the myth of the poor developer being robbed of the value it delivers is alive and well around this community.

Here's the thing, in corporate devs are as essential as people toghtening nuts in a factory.

The value one produces there is multiplyed by the internal know how, customer base, marketing reach and tight focus management, none of which it's brough by the developer.

That value is stripped from developer work just to be pocketed by management and sales is a myth, besides, if it werent there'd be plenty developers going solo and the median salary would be in the millions.

Edit: and lo and behold, instant downvote. No wonders the tech community is so blind and guillible when it comes to the value argument, from the extraction myth to the stock options gambling.


I don't disagree with this, but it isn't universally true.

Some developers are just writing code to satisfy a spec and really could be replaced by any other developer; others are uniquely valuable and significantly increase their employers value, without necessarily being recognised for it.

Good software acts as a multiplier, so it's not equivalent to tightening bolts. It's more equivalent to finding optimisations that reduce the number of bolts which need to be tightened. A relatively small amount of software can drastically increase the value of a company/process


Tru but the few of us that really push the envelope are few, are pulling serious $$$ already and hardly move the mean.


Internal knowledge is not held by the company it is held by individuals within the company. At best what you are arguing for is that there are enough people that for a given salary you can use to replace your existing people and can pick up what they are doing quickly enough that they are replaceable. That is not the same as your disrespectful assertion that your average dev is the same as a person who tightens bolts. Even the most simple development tasks require a significant amount of knowledge and at least a few years of experience that only a small number of the population can actually perform.

It's true that an individual can't do the same things a company can do. That's not some profound assertion. It's however impossible to go from that and assert that is because they are incapable of doing those things even if they had the funding to do so. That is to say that the marketing issue is more or less an issue of funding or money. That is what keeps that individual devs from capturing more value that is instead captured by companies or by managers, marketers, etc. As well as hiring additional people to form an actual company that performs the functions of a company. However a significant number of founders are developers, many of them including Paul Gahram and Mark Zuckerberg average developers that went to found multi-million to billion dollar companies because of funding. Now after the fact maybe you can argue that there was something special about them, but that's a post-facto assertion. They were average devs and if they had not gotten the funding would be relegated to your nut bolt tighteners not having been able to express their "true" potential.


Yes, people love to laugh at this mythical economist, but seriously, when's the last time you saw a legit $20 bill just lying on the ground? I've never seen this even once in my life. Perhaps this mythical economist is the one having the last laugh.


It's probably happened to me a dozen times that I can actually remember. The first time I can remember was a $20 on the floor of a Blockbuster Video. Most recently I found a 50 euro note on the ground in La Reunion about a year ago. But I guess that's technically not a $20 bill, so maybe it doesn't count.

If you allow for faux currency exchange, keeping your eyes aimed down at a renaissance fairground is pretty much guaranteed to turn up enough food tickets for a turkey leg.


I've once found an 5000 HUF (18 USD) bill on the floor in a pub. I picked it up and wanted to ask "who lost this?" then I realized that everybody would answer "me!" so I just kept it.


My father taught me a trick. It's not foolproof, but it's better than your version.

You ask if anyone lost any money. If someone says they did, you follow up with "how much money, and how big were the bills?"

Then they have to know an amount, how many bills, and what denomination.

You can imagine that it's hard to fake, and anyone being genuine will have a pretty good idea of what you're holding.


Now that's a good trick, thanks!


I have a friend who is notorious for always finding money on the ground. He has found a lot of money just lying around.

Once, while eating a pizza with canned mussels, he felt something hard. It turned out there was a pearl in his pizza.


I found $315 blown against a street curb on my run with my wife one morning. It was roughly 7am and nobody else in sight so we just took it... Admittedly, when people ask the ethical question of "do you report it to the police?", I suppose my answer is "no". I gave myself solace in thinking it might've just been a drug deal that went wrong. ;)


My anecdote: I picked up a £20 note on the sidewalk in London two weeks ago.


"Woman who found £20 note on floor convicted of theft"

http://www.bbc.co.uk/news/uk-england-stoke-staffordshire-391...


I found a handful of money on the sidewalk once walking back from class, about $12. More recently found a $100 bill in my sister's front yard (not her money, presumably blown there by the wind).

It happens.


> Yes, people love to laugh at this mythical economist, but seriously, when's the last time you saw a legit $20 bill just lying on the ground?

1996 (±2 years) in an arcade, actually.


I found a $10 two years ago in a field.

It was really ragged, so much so that the bank wouldn't take it. So I still have it.


That was just about the same timeframe when I found one as well (on a college campus in my town).


Actually, I did a few months ago. Found a twenty on my lawn. Then found more, blown up against the hedge - ended up being a total of $180, plus the bank withdrawal slip. We took it back to the bank to return to the owner.

But it was neat, finding money just right out there on my own lawn.


Just last week I put a 20 euro note on ebay and the highest bid was under 5 euro. I guess everybody was thinking like an economist.

http://www.ebay.com/itm/-/263028687192?


As a counterexample, I regularly lose cash money...

Sometimes money literally falls out my pocket when I fumble out a wad of cash while i'm inebriated.

Other times I carelessly leave my wallet somewhere stupid and the money "walks off."

Over the past 2 years, I've probably lost over $1000 this way.


As a kid I once missed out on a few hundred in cash on the ground at our local golf course. My friend walking behind me was paying more attention to the ground and spotted it after I had just walked past...


What are you trying to proof? How the fact that you or people that read your comment here have not seen any bill changes the probability of a $20 bill sitting somewhere on the ground?


It's an n=1 comment. Take it for what it's worth.

Also, "proof" is a noun. You meant to use verb form "proove". "Proof" as a verb means to "proof-read" (to read with an editorial mindset).


prove


Three months ago while swimming in Miami Beach I found a $20 bill lying on the ocean floor.


Laughing a sinister laugh as I super glue a $20 to the sidewalk...


Classic Candid Camera from the 60s: "Bill Under Tire" https://www.youtube.com/watch?v=zP8V53_YdMI&t=1m08s

The last one is the best.



I find coins on at least a monthly basis. I once found a $10 bill.


Happened to me two or three times in my life so far.


I found a fiver not to long ago...


I found a $10 a few months ago.


Realistically though, how many twenty dollar bills do you find lying around on the ground? Zero so far for me in this life... Maybe a quarter here or there.


I've found a couple 5 dollar bills. My ex found a twenty in the pocket of some jeans at a used clothing store


I found 2000 in the pocket of a thrifed suit jacket


More like they pick it up and it turns out to be a 20 peso bill, because they've never seen pesos before and don't understand it's value.


LOL. Hadn't heard this one before.


That depends where you are hiring from, even within the US. You're also reaching out to people who may be okay taking a lower salary to work on a project they are already passionate about or already donate their time to.

Chris Webber, for example, took less than a $40k salary without benefits to work on MediaGoblin full time for a year:

https://mediagoblin.org/news/we-did-it.html


> You're also reaching out to people who may be okay taking a lower salary to work on a project they are already passionate about or already donate their time to.

The games industry gladly takes advantage of this.


Yes. Many people new to the industry don't understand that the glamor of working for a game company almost always translates to bad working conditions and low-ball pay. Games are hard, but there are just so many people who want to be involved in making them, that there is a pretty excessive supply of prospective developers. Game companies take that as a license to burn people out, because they know once that crew finally tires of the beatings, there will be a fresh crop of bright-eyed devs anxious to replace them.

CRUD apps may be tedious, but getting a job at a local medium-sized company working on them is usually much more pleasant than working for a game developer.


Oh but it is? Do you use the GIMP?

Photoshop's content-aware fill first appeared as a third-party open-source plugin for the GIMP.

While one certainly can't equate the two I have found GIMP works well for a broad array of digital imagery tasks... just like Photoshop.

Much of Photoshop's dominance has to do with the network effects of Adobe's ubiquitous ecosystem as much as the comprehensiveness of their tooling.


> Photoshop's content-aware fill first appeared as a third-party open-source plugin for the GIMP.

Indeed it did, and that plugin was hard to configure and hard to use. I remember installing GIMP just to try that plugin out, and it was not fun, it involved a lot of manual steps to get it working, and I never quite got the hang of it.

In contrast, when I got my hands on a version of PS that supported content aware fill, (which admittedly ships in the box, skipping the installation step) I was able to figure it out in a few minutes and start getting good results in half an hour. I am pretty sure I spent more than half an hour trying to get the GIMP plugin installed.


I still can't get the GIMP resynthesis plugins to run on most of my machines...


Last time I tried the lack of Adjustment Layers and Smart Objects was a dealbreaker for me. Maybe that's changed but those are things I use daily (I can deal with lack of content-aware fill).


I find Photoshop v Gimp akin to Android v iOS.


You mean other way around?


This comparison also ignores other products in the market which already fill this gap. Yes, GIMP could be improved with a bigger budget, but in that time frame would it be better than Pixelmator which only costs $30? And if it is better, would that type of customer value it at your proposed $400 vs $30 for a product which already works right now?

[1] http://www.pixelmator.com/mac/


Lol - you can get 6 senior devs (3+ years experience/independent), or a 4/4 split senior/junior devs depending on what skills you're looking for (in East Europe)

The bigger issue is if you can pull a 400k Kickstarter and manage such a team why the hell would you be wasting your time on GIMP dev - you could do waay more profitable and interesting stuff.


Seriously, how much work goes into Gimp nowadays? I seem to have the same version today as 5 years ago. I'd love to help kickstart a new beginning (run a kickstarter with a specific proposal?) but I'm afraid they're stuck with bad UI decisions and the bad decision workflow which lead to them.


My biggest complaint is how painful it is to change brush size and brush opacity.


I agree. Gimp will need just as many developers as Adobe employs, and just as much money as Adobe makes, to be more 'like' Photoshop.


I think they are also underestimating how much Adobe spends on developing photoshop.


When you load up PS, you see a list of people involved. It's a lot more than 3 FTEs.


I wish my company spent 400k per 3 employees.


It very well may after you factor in office space, benefits, vacation, unemployment insurance, FICA, etc.


I was assuming non-sf salaries... but yes, even then, it's really pushing it to say it would pay for 3 people in the us. I was being generous.


What senior dev makes less than 100k in the USA these days?


Who said anything about senior devs?

If you're really hung up on whether 3 is the right number, I think you've entirely missed the point of my post. Adobe has far more people working on photoshop.


Plenty, outside of the usual suspect locations (SF, NY). A six figure salary for devs, senior or otherwise, is unusual outside those areas. It's not unheard of, but it's not typical, either.


I'm not convinced the $150K+ salary figures I see sniffed at on HN as "bare minimums" are quite as common even in SF/NY/etc. as people imagine they are. Startups and (some) "star name" tech companies in those areas hit those figures, but even today I still see more technical jobs than one might imagine in the $80-120K range. I'm aware a lot of software engineers insist that when they're only making $140K they're underpaid given all the Amazing Stupendous Value™ they bring to their companies, but I have some doubts about how sustainable such figures are going to be at most employers as the VC markets tighten (which is definitely happening now).


I don't work at a "star name" company, but it's in the Bay Area. $150k (+/- a few percent) is the typical base for Senior and Lead Engineer positions here. I don't know if that's typical for "not star name" places, though.

And most developers are definitely underpaid relative to the value we provide. From shabby CRUD through deep machine learning research, we're generally underpaid. Partly it's our own collective fault, though: as a group we're told constantly that passion for the product and satisfaction at "being paid [anything] for doing what you love" should be enough, and enough of us buy that crap that it effectively depresses wages.


> $400k pays for 3 people

Yes, but it is three full time people. Don't underestimate the difference being able to focus on a codebase for an extended period makes...

Also, knowing that you will be able to continue that focus carries it's own benefit.


I am not sure if GIMP is truly the competitor for PS. I do almost all of my editing with a handful of apps. Back then I tried doing it all with PS and the results were a lot worse as it was way to complex to understand all its features.


Yeah ~3 FTE sounds about right. But if offered as grants for students to work on over internships or something, it would go a bit further. But I don't know enough about the GIMP codebase to know how feasible that would really be.


The question isn't whether 400k would make gimp replace PS. The question is whether 400k could get the users who contributed the features they want. It still is a gamble but it's more attainable.


400k is plenty if you can hire people from developing countries.

From my experience, you can hire a good developer from Vietnam for approx ~2k per month; which is 24k per year.


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 idea in the first place, I know almost nothing about its features, architecture and code base.


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.


and if you're building on Gimp you're WAY past "from scratch". The bulk of it is already there. Mostly Gimp just needs usability / human interaction changes.


> and if you're building on Gimp you're WAY past "from scratch". The bulk of it is already there.

This could be a good thing or a bad thing if major changes are needed. A project of GIMP's size is a big ship to steer.


There is a neat feature of large fundraiser campaigns in free software you can take advantage of, in that if you do get 400k and hire 5 devs and have them work a year on a wide range of features for some software, it doesn't really matter what upstream says if the users want those features. You just fork if upstream isn't "on board", work on your own separate branch for a year, and then when all the users start downloading and using the fork the upstream will have to work with you to merge all the work done since 8000 hours of work on their project is not something they can discard.

As long as you wrote useful features then GIMP, for example, wouldn't be able to argue semantics on the patch set and tie up merging for a long time on politics. Their users would demand the features.


Surely the big problem with this (and the wider site concept, much as I generally favour it) is that the donating users who say they also want GIMP to be as good as Photoshop don't all have the same idea about what constitutes better UX. So you get a high proportion of dropouts from the funding subscription, as well as disagreements with GIMP's existing user base and team about whether they forget their original roadmap in favour of merging your patch, assuming you can still afford to finish it.

(Key difference with Kickstarter etc is that people are pledging for a specific solution rather that for people to solve a problem, and the cash is paid up front rather than a promised monthly commitment. And still there are issues with execution of many projects, particularly once third parties with different goals are involved. "I also need GIMP to be as Photoshop" on the other hand, is basically asking for a "nice unicorn" and hoping both that unicorns can exist and that everybody else involved - especially the unicorn-breeder - shares your definition of "nice" ones)


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 create a more specialized app that does a specialized job that Photoshop might have done in the past.

Or how Adobe's iPad Pro apps again deliver just a small subset of the total available features from their parent apps, making them more specialized for specific use-cases.

Photoshop's massive fragmented user base is ripe for the pickin' for sure. Could you tear down Gimp like that? Or would it be better to start from scratch?


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.


>but not one person who uses photoshop uses Linux

Not true: I use photoshop (albeit, not professionally) and have a subscription for it, but am writing this from linux. Dualboot exists, you know.


That's absurd.


FYI Photoshop doesn't work on Linux.. so not so much absurd, as factual


PS CS6 runs well in WINE.


And iirc, Google sponsored the patchset that allowed CS6 to run on it. So someone out there wants Photoshop to work on Linux, and is even willing to pay for it.


You're technically right

But I would still say Linux support isn't what's holding back any photoshop replacement


I'll be the negative Nancy here - you'll never get 1000 people to pay $400 each for any OSS software, no matter the price of the competitor.

The reason is a simple value estimation. It's open source (and so free to get) therefore its price is $0. Any product that is free signals that the product has correspondingly low value. I think it's simply unrealistic to expect people to put forward $400 for something with such low value perception and whose fair market price is $0.

This is especially true when Photoshop has such a high value perception (in part because it is better, and in part as a justification for shelling out the $400).

Ask yourself this - Have you, or will you, paid (donated, ...) $70 for using Vim (atom, neovim, emacs, VSC, ...) to support development? Have you paid $200 to Debian, Ubuntu, or Redhat for your Linux OS? $5,000 for (open|libre)ssl? $13,000 per core for PostgreSQL/MySQL?


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


I think something more limited (like get GEGL out the door, if that isn't done yet) along the lines of the Django migrations kickstarter would be more realistic: https://www.kickstarter.com/projects/andrewgodwin/schema-mig...


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).


he could always fork it and pay for other developers if the core team didn't want to participate in this. You'd rather the core team's approval and participation, but you don't NEED it.


Call it Pimp.

I would say that I'm in too, but I also need a quality Illustrator alternative that works well on Mac.


To cacarr: Inkscape is not at its best in Mac. It's clunky because you have to use control instead of command, can't zoom with the trackpad, can't go fullscreen.

I use it and love it and it's one of my favourite programs, but really it's better in Linux.


A key mapping function sounds like one of them more easy things to add into a piece of software


I assume you've tried Inkscape?


If you don't get their support, then that $400,000 has to go a lot further (or you have to work towards a branch reconciliation at the end of the work). Ongoing maintenance is not free.


I'm in.


> you'll never get 1000 people to pay $400 each for any OSS software, no matter the price of the competitor.

Yes and no. I'm doing that right now...

The key is that I don't charge for the software as such. I charge for services, etc. around the software.

People are happy to pay for value-add, even if the underlying software is free. You just need to show value-add...


Sure - but then you're not really charging $400 for the software. You're charging $400 for the services associated with that software, and a (typically significant) portion of that money will go towards funding the service, not the OSS software.

This change in how the money is allocated is a subtle, but important, distinction. Monetizing a service means you now have a minimum of two products to manage, and from my time at a company which did exactly this I've found that the OSS software development is the product which absorbs any shortfalls. It's hard to watch the budget for OSS development shrink constantly; to watch developers passionate about the OSS software being reassigned to grow the service instead.

It's probably still the best way to handle a crummy situation, but it's not what the OP described.


> The key is that I don't charge for the software as such. I charge for services, etc. around the software.

Yep. Matt Mullenweg & his crew at WordPress have been doing the same thing, and are wildly profitable at it.


It's not just about profit. It's about lifestyle.


I don't know. 1000 is [ed: not] that large a number of people. But it might be easier to get 40 from 10.000 people, than 400 from a thousand.

I'm reminded about the kickstarter for Django migrations: https://www.kickstarter.com/projects/andrewgodwin/schema-mig...

Most backers gave 5 or 10 pounds, but on average ~500 people gave ~35 each.

You might be half-right about perceived value though - I think anyone that is a serious Gimp user see value in the software, but might still think 400 is too steep, given that it is free now. But I also think many users would be willing to pay for getting some features in/some polish done - personally I'd say my current limit would be around 100 USD for any one OSS project.

Now one one hand, Debian does much more than any small project, but I also think it's more likely that 10 000 USD would do more for something like the Gimp, than for Debian (assuming we had a developer or two on standby that could take the opportunity of devoting a month full time on getting some pain points resolved, say).


Also, Free software, creates a large tree at $0 that will kill everything that tries to grow under it, like a $5 decent alternative (nothing grows under large trees).


Yeah. This is a classic free rider problem. Game theorists have known about it for decades. See Mancur Olson, The Logic of Collective Action.


Crowdfunding open source seems like a good idea in general (in fact I could see a platform built around that specifically), but you may be underestimating the amount of money/effort required to build something comparable to Photoshop. So I like the idea in principle, but not in this particular instance.

For what it's worth, I think Sketch is much more user friendly and is $99 one-time. Certainly not OSS, but a better deal than Photoshop for most things, and a much more user-friendly interface than Gimp (though I suppose that's subjective).


The logistics themselves are already giving me a headache. You have $400k, but are Gimp's developers (and they exist, right?) ready to just get an infusion of somewhere on the order of three years of salary and get to work? I assume the roadmap would change with that amount of funding.


I've seen some cases where patreon.com is used to fund open source projects. Vue.js is founded there for example [1].

1: https://www.patreon.com/evanyou


It's probably attainable if those 1000 people manage to confine their feature requests to something 400k can fund.


There are crowdfunding sites that either just happen to be used for these things or are focused on them, the issues are complex. Here's a run-down (that needs a couple updates like including Open Collective): https://wiki.snowdrift.coop/market-research/other-crowdfundi... (on the wiki for a still in-progress platform designing a new funding approach around the specific challenges of free/libre/open projects)


Sketch is 99 dollars a year. After the year you can still use it but you won't get updates. If you work on a team you'll pretty much be forced to always have the latest version.

Still, 99/year is a drop in the bucket. Even 50/month for all of creative suite isn't all that much considering many of us will just add it to our business expenses and write it off.


No Linux version.


Paying $400, even once a year for 10 years for something that works is probably cheaper in the long run than paying $400 once with a high likelihood that you get a bunch of garbage for the next 10 years.


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.


A lot of people's open source work is mainly limited by competition for time -- namely, their job, spending time with family, chores/housework, other hobbies, relaxing and sleeping.

More money may help entice more time to be taken from some of those other things, but some of those are more or less fixed (job, chores), not sustainable to give up for long (sleep, relaxing) or simply not worth a small (or any) amount of money to give up (family).

Enough money and stability that someone can give up their day job -- that's a different story. But that's a very big jump, and suddenly even $400k doesn't really go that far, assuming you can even get that money. There's a reason very few open source projects have a full-time developer being compensated by the community.


Pure Fantasy.


And GNU/Linux will never take off.


As far as casual user is concerned, it didn't. Large corporations instead enjoy a very nice free ride (all the servers).


Chromebooks are already outselling Macs. A lot of (most, even?) American schools are buying Chromebooks for students to use because they're simple and work well.

ChromeOS uses the Linux kernel.


I'd add that to the list of free rides for large corporations.

Students getting Chromebooks aren't sucked into the Linux ecosystem and open source community that encourages you to improve parts of the system yourself. Instead, it leaves system maintenance (and learning experience) entirely to the administrator and really only provides Chrome as the operating system, with all implications.

Control your data locally? Why not upload it to Google Drive instead. Learn git commands? Better find that hidden Developer Mode switch, because crosh isn't going to get you very far. Get involved in improving Linux or Chromium? Nah, better edit some JavaScript in a web view with someone else's proprietary online code editor.

Google can (and will) swap Linux out of Chromium whenever they want to, because none of the interfaces and none of the community overlap. When Fuchsia gets swapped in, neither you nor the students will notice, and it won't have made a difference other than Linux having helped Google's locked-down, centrally controlled platform to succeed.


Sure, then I'll get a different laptop. Or maybe by that point free software on other devices will be far enough along that I won't need a laptop? The future is networked, inescapably. It's fine to advocate for local data, but don't expect that to mean data on a drive in a box on my desk.


If we can make a future happen where I can control software and data on a remote device, in a way that works for students, then sure. Otherwise, I wouldn't count pure access to the internet/web as actual victory for GNU/Linux. (Maybe as victory for education opportunities, productivity, etc., but tying that back to Linux is a very indirect connection.)

Either way, ChromeOS doesn't contribute to taking (co-)ownership of any of the above and encouraging the freedoms commonly associated with the use of Linux. Neither does it sustainably establish even the Linux kernel as pillar of the OS, it's just an implementation detail to be hidden and potentially replaced later. So why exactly should we look at ChromeOS as GNU/Linux having taken off for the casual user?


If you're defining Linux as the free-for-all open source community product, you're inherently defining why it will never take off for the casual user. That's not who that's for and that's not what the casual user does.


It took off thanks to the efforts of professional paid programmers.


The year of the Linux desktop is always ten years from now ;-)


You're right. I googled for "photoshop license price" and Google gave me old information from this page https://www.cnet.com/news/adobes-new-pricing-plan-ouch-users...


I pay $10/mo and that includes Lightroom, which is impressing me more every time I use it. In fact I'd probably pay the $10/mo just for Lightroom, and then I could say that Photoshop is free. :-)


If you're using Photoshop instead of GIMP, you're probably a business. If you're a business and $348 a year is a big deal to you, you probably aren't going to remain in business for long.


Hey if you can find 1000 people to pay $400, I will make it.

But it's hard to convince people to hand over their money. SaaS works because the profits are reinvested into marketing.


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 with 32bits per channel from the start, instead of the slow transition to GEGL...


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?


I pay for creative suite. GIMP is very far behind. There are many significant core features missing, and many tools missing that make it difficult and time consuming to use. It would be more accurate to call it 'advanced paint' than photoshop.

CS is expensive and I use a small part of its features... if GIMP covered just 25% of what photoshop could do, I would use it. But I think the only people who think GIMP is close to replacing it are those that have never used/learned photoshop.


Do you really use GIMP? Because I don't think you use it very much if you think that it is a quarter of Photoshop.

Adobe regularly copies features from the GIMP, like content-aware fill


I'm well aware of the status of GIMP. I first used it 15+ years ago. I used it for many years before buying PS. I last used it maybe 6 months ago. I like to check it out occasionally when my CS subscription is up for renewal.

I actually pay, not just for CS, but an entire Windows computer to run it. The rest of my computers run Linux, and I use open source software everywhere.

I would absolutely love to switch to GIMP, if it were at all possible.


Well, GIMP's interface is definitely different from PS. And I wouldn't argue better...

But PS is the only program I have ever had to take a class in to be productive in, as it was clearly built to be familiar to people with very clearly-formed ideas about workflow, e.g. old-school photography and design folks.

And switching to GIMP is possible methinks, you just have to learn the interface. Just like Photoshop...


GIMP does not even have a circle tool, and I don't think working around pointless limitations like that counts as "learning the interface."

The commenter above you used the software for 15+ years and specifically cited that lack of feature parity is the only criticism keeping them on CC. I have used both as well and do not follow your opinion about Photoshop, maybe because I never used those old school design tools. To me it looks like an Adobe UI.

Overall I just don't understand how you read the comments above and determined the solution is to learn the interface - honestly, the most tired and uninformed defense of GIMP there is. Especially when your primary criticism of Photoshop was... The interface. I guess the argument could be made you eventually get used to working around inexplicable deficiencies like above, but switching to GIMP is not possible if you need the features only included in Photoshop. There's not some random cosmic reason Blender and Inkscape are considered healthy competitors in their respective domains but not GIMP.


I like how you use more words to explaining (what you think) I think than I spent writing the original opinions. I don't have strong criticisms against either... Photoshop did take a while to learn -- I remember struggling to complete tasks when I first started with it because my frame of reference was Paint Shop Pro -- and GIMP also takes a while to learn.

Why do you feel so strongly against 'learning the interface'? That "tired and uninformed defense" is also... what you must do. Why is everyone so afraid of learning?? Fucking wimps. You have a problem, you google it, repeat til you know the product. SO HARD!


Because, again, learning the interface does not replace what the software cannot do. People who have both learned gimp and who need photoshop for their jobs are tired of hearing these lecture points.

I write a lot because I want to clearly explain my points on the Internet where there's no verbal nuance. Sorry if it was too much. Are you really criticizing me for thorough explanation on a discussion forum?

Edit: I should probably qualify that in the capacity I use photoshop it's kind of a moot point anyway, since I depend on illustrator just as much and the convenience of smart objects and the interoperability with stuff like libraries are more than worth the price of admission for me.


People have said that, but they can only mention the one feature. That, from what others have said, didn't work very well on GIMP, but worked well on Photoshop.


There was nothing wrong with Windows 95.


1. It took forever to get to more than 8 bits per channel. 2. ...

I could list 4 other points, but really it's just about that one. Photoshop has had 16 bits per channel since 1992 when version 2.5 was released. That's what... 25 YEARS!

Gimp is FINALLY 16bit per channel now in 2017 with their latest beta.


Why would spending money on a brand new system with no proof of success be better than a matured application with plugin support?


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


Sure. I was responding to the suggestion that the key problems with GIMP are the UI and name. The image manipulation code is surely pretty mature by now.


The name was "terrible" right after the film "Pulp Fiction" was released. Decades later, is that still true?


That word existed well before Pulp Fiction.

From Dictionary.com:

>> Usually Disparaging and Offensive. a term used to refer to a person who limps or is lame.

>> Origin

>> An Americanism dating back to 1920-25; origin uncertain

>> Usage note

>> When describing someone who is lame, gimp is used with disparaging intent and perceived as insulting. But within the disability community, it is sometimes a term of self-reference.


Yes. "Gimp" in UK English is not a word you say in polite company, like calling your software "slut". Sure, it's fine to speak of with a close friend but difficult to even mention to people in certain circles. I don't know what's wrong with calling it "The [GNU] Imp", an imp being like a fairy/pixy (but with a sense of mischief too), like Puck. The mascot could be kept as it fits the description imp as well as it fits anything (I've no idea after c.20 years what it's supposed to be, though I recall looking it up once).

Maybe "Imp" is offensive in other languages? (Nothing other than alternate English meanings shows on Wiktionary).


This GIT thing is never going to take off because it has a lot of baggage: a very particular CLI and grammar, a community of active users (many of whom probably like it exactly how it is), and a "terrible" name.


You could ask the same question comparing your project with Photoshop.


Photoshop has a lot of engineering/product work going into making it better. Unless the price of it were totally absurd, it's always going to be a worthwhile expense if it's the most efficient piece of software to use, because software is typically much cheaper than labor. "Good enough" isn't the goal in this regard.

In this case, Photoshop will continue to dominate (unless they get lazy/give up) because they have recurring cash to reinvest.


Probably many people would be happy just using an open source version of Photoshopp 6 an they would be ok missing some of the features released in the last 10 years (like painting 3D surfaces or automatically fill a region of the picture that you delete). Sometimes companies forcing you to update your software to get your money it's not a good thing (Windows 10?). With open source there is always the chance of forking as what happened with OpenOffice and LibreOffice.

The issue of having to pay to get access to your tool it's a big issue.

For big companies having to pay for 100 workstations yearly the monetary incentive is big.

Once many people is aware that in the long term it's a better deal to put their money into software libre projects, maybe different companies could compite to get your money.


> they would be ok missing some of the features released in the last 10 years (like painting 3D surfaces or automatically fill a region of the picture that you delete)

Content aware fill was in Gimp before Photoshop. It was an open-source PhD project.


Photoshop version 2 was given away for free on the adobe site a year or so ago. It works great and does most things fine.


Note to OP.

1) You need a 3rd button for each submission that says "Already Solved". People can post links to SaaS products that already solve the exact problem the users are posting...

Example: Following 2 Submission have several products that solve the exact same problem.

- Gamify budgeting so I save more money => https://www.demandrush.com/problems/gamified-savings-app

- Community chat on my website => https://www.demandrush.com/problems/onsite-community-chat

2) You also should introduce some sort of flagging or curation, because quite a few "Problems" read like 1 off specific requests, and some descriptions are also really vague and too broad

3) Might also wanna provide Upvote (only, and no downvote, like ProductHunt and Facebook "Likes" :) button to assess popularity, because not everyone might be mentally willing to commit to monthly payments, but might really "like" the idea and think it deserves to be solved.


These are great suggestions. Thank you!


Rather than "Already Solved" I'd prefer "Potential Solution."

Just because a solution exists does not mean that it's a suitable one, or can't be improved upon.


I find Krita to be a more user-friendly program than The Gimp, though it's more painting-oriented: https://krita.org/


My question is, what is preventing GIMP from tapping into their existing userbase?

I get they are FOSS. But, they could still add in their GUI options that don't exist; then prompt donations that would go towards the features development.

For example, Image > Rotate, triggers a pop-up, "Sorry, Rotating image is not currently a feature but with your support we'd love to add it to GIMP! We expect it will cost $10,000 and we've already raised $4,235 from users like you. Contribute now..."


I can't quite tell if you're serious, but I don't think users would like that sort of bait and switch tactic. It would make GIMP feel like shareware that tries to trick you into paying money.


I'm serious but I don't use gimp so what do I know. I'm posing it more as a theoretical question of why can't the collective we be asked to pay for features we want. What I know of Gimp is that it has majority of the features of PS so why would the power users not be willing to pay for advanced features that probably only they use. The answer in my mind is that they are willing to pay but they pay adobe because gimp doesn't ask for money.


You could avoid the bait-and-switch feeling if the non-implemented features were grayed out to distinguish them from the ones that were already available.


What if I told you that the non-user friendly aspects of GIMP were by design? I belive there was a battle a decade ago to get rid of odd floating side bars.


Well yeah, there was a battle, and they added single window mode like 6 years ago. Solved the floating bars.


FWIW there is the Photography plan which is $120/yr instead-- http://www.adobe.com/creativecloud/photography.html, but point taken.


You should be using adobe xd or sketch for any app/web work, photoshop is best for photo manipulation and raster images. And yes it is needed for stock heavy websites...


The problem is that as soon as you start paying for something you demand support and OSS often completely lacks this. It even says so in license files.


GIMP is a steaming pile of shit. It's not 400k away from being a Photoshop competitor. Maybe it is less so now, but when I last used it, I said never again. If you need Photoshop to actually get work done, the $120 it costs ($120 gets you both Photoshop and Lightroom) is well worth your money. Many people charge more for one hour of contract work than Photoshop costs to buy for an entire year.

But there are very good Photoshop competitors that don't cost a lot of money. Pixelmator is $29 and a better program for many users. It's lightning fast to open and use and it requires less computing resources.

I remain deeply unconvinced that any software that requires an elite UI and interaction model will ever come out of a software libre solution. In addition, most software libre solutions are simply copies off of someone's else's ideas and hard work. It can't exist without paid software to copy first.

What are we even doing in tech and software if we are arguing that people should copy other people's work and then make it free, causing people to lose their jobs?


> GIMP is a steaming pile of shit.

Hyperbole much? GIMP is high quality software and I'm sure I'm not the only one who prefers it to Photoshop.


I second that. While I can't realistically say I prefer it over Photoshop since I've never used the later, I can certainly state that GIMP meets ALL my graphics editing requirements (which are not many, but that's besides the point).


Blender, Krita, and Inkscape are all excellent in their domains. What is this nonsense about free software can't have good UX?

> copy other people's work and then make it free, causing people to lose their jobs?

Wikipedia is a fully free project and the foundation employs ~300 people funded mostly by an annual donation drive. Free software != no jobs.

And I really don't want to get into it, but for a lot of free software advocates extorting money from people for licenses using legally granted artificial monopoly of scarcity on software you don't even have to disclose for the cost is highly unethical.


There as several affordable and easy-to-use Photoshop alternatives around these days. My personal favourites (on MacOS) are Affinity Designer and Pixelmator. I'm sure that there are others which save you the price tag of Photoshop and the learning curve of Gimp.


The freebsd foundation gets over a million dollars a year. That isn't enough to beat out Windows or even linux. (I know linux has a foundation as well and I presume has a larger budget, I just don't know the numbers off hand)


AFAIK, for most tasks GNU/Linux is already good enough. Look for example, at a successful project in Munich to replace Windows for public employees https://en.wikipedia.org/wiki/LiMux.

The main problem is people do not want to learn a new interface or have programs running only on Windows.


companies pay for photoshop licenses, not people, and few hundreds companies can easily put together way more than $400k - if only "cooperation" wasn't such a taboo concept.



For simple drag + drop design needs, have you tried Canva?

https://www.canva.com


Kickstarter?


Kickstarter or Patreon would seem to be the kind of thing made for this problem. Maybe those that donate more get their pet issue moved up the queue.


What about you pay to get hours of work (HoW). Then people put their HoW into the issues that they want to solve. Example: Having different keymaps scheme support in Gimp would take 100 hours. So once people put enough HoW into that issue the team can start to tackle it.


Keymaps being sets of shortcut keys? GIMP used to have that with dynamic update and easily​ shared keymap files.



This 4chan thread is pretty illustrative of Gimp's UI shortcomings: http://boards.4chan.org/g/thread/60884056


Oh wow. No wonder my mom switched from trying linux back to windows after I tried to tell her "you can just use gimp for basic Photoshop stuff"

It doesn't even have a circle tool and the best "solution" seems to be ellipse select with shift -> fill -> shrink selection -> delete

What a dystopian ux nightmare.

Sorry Mom, for inadvertently inflicting gimp on you.


Er, no. The best solution is to use the circle (select) tool, convert the selection to path, then stroke the path.

I don't think it's that far from how one goes about drawing bezier paths in PS (although it is a little more convoluted).

https://graphicdesign.stackexchange.com/questions/28344/how-...


I loved the reply where they opened Python inside GIMP and draw the circle with "import turtle".


ugh. thank you for reminding my why i never visit 4chan


> 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?


I think also it's possible that by chance you already have something that is a solve and this connects you to people looking...


That's right!


First, I think this is a great idea. People have problems they think might be solved / automated. But I agree it definitely needs some language clarity.

Businesses: have a problem you need solved with software? Post your problem!

Programmers: looking for a challenging project with identified customers? Apply to solve a problem!


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


No. You own it in a business way.


Yeah it's a little confusing, I agree. "Your next side project" out of context sounds like you get to pick the project. Might be better to explain it as: "looking for a side project to work on that's worth money?"


I suppose you could post your project idea on there, and see if it takes off. Although it's not clear who makes the decision of who "officially" gets to tackle it, there's really nothing stopping you from tackling it anyway.


The whole point of this site is to find problems that are worth solving. Not, to build yet another useless yik yak app, that nobody needs, wants or isn't willing to pay for.


Except there is no guarantee that you will build anything that anybody is willing to pay for.


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.


But a dev can solve that themselves: apply #lean principals and launch a marketing site cheaply and start taking advance subscriptions using one of many tools that solve that white-label Kickstarter need.


It's a market, so it clears when my next project and your next project are the same project.


This is a shallow equals, though. I can guarantee that we will differ in implementation specifics.

This sounds like a good idea on paper, but the reality is that most of the value of a project is in the implementation details. There are countless meetings for each individual feature.

I'm pretty sure the above description is how a lot of the end users (clients) are seeing this. Their contribution amounts are also insanely low (orders of magnitude lower than I would dare to value some of their projects).

I don't know how contracts or SLAs (if any) apply here, but this just seems like a good way to get yourself on the hook for getting paid (I'm guessing) a tenth of minimum wage.

Source: I do this sort of contract work for a living.


There are a lot of posts on programming forums about "I want to build something but I don't have any ideas". This is meant for those people.


> Industry-specific deep learning interviews and walkthroughs

> 1 customer paying $5/mo

Sounds about right.


I agree about that specific example, but I think a lot of people are missing the point.

> Developers own the products they build for customers, and charge a monthly fee for access.

So, what you're seeing is what a single user is expecting to pay. This is not like a contracting / free-lance website where someone hires you under contract to do some development work.

Instead, you create the SaaS or whatever, and then you have at least x number of people that are willing to pay $y/month for said service; your market is not limited to the people who use this website, too.

I think it's really just a way for people to find what projects people want, and what a select few are willing to pay for it.


So in essence the product's growth will depend on how well I built it, how much marketing I put into it and lastly how many more people will want this in the future? Nothing new there.


Yeah but at least you have some ideas laid out for you. I'm always looking for a side project, but I never know what people need.


Yeah I had to laugh about that one as well. Especially the part about ImageNet being too general. If they knew anything about deep neural networks, they would understand why these base models are important and necessary for a candidate to understand, because they can be used to form a foundation for the solution.

In many cases, you can use the model as-is (and likely pre-trained) for a use case outside of "match label to an image", with only some additional training with your specific dataset - which may only be tangentially related (or not even that!).

These models (and the surrounding tools) have become for many problems more like Lego in my opinion - which is a good thing! It means they are more approachable for everyone, rather than being something mysterious and complex. Ok - if you dig, things become complicated quickly, but for many problems, you don't have to worry about these internals.

Are there problems which don't fit neatly into using a modified ImageNet or LeNet or one of the other "standards"? Certainly. But I think a candidate who understands the standards and basics well is likely a better one than one who only understands a specific subset for a particular industry (if there even is such a thing, which I am sceptical of).

Furthermore - it would be even better when a candidate can say "you know what - your problem doesn't need a neural network of any kind, let me introduce you to <insert standard statistical machine learning method>" - because there are tons of problems out there which can still benefit, and be a robust, easy to understand, and fast (to implement, to maintain, to execute - whatever).

I love neural networks, certainly - but there's been so much hype in the news, everyone thinks they need one, which will probably lead to many investing money into worthless (or expensive) solutions, where simpler (but less "sexy") ones would have sufficed.

The candidate who could know and tell the difference would be even more ideal - being able to interview/walkthru that might be a way to get a better candidate.


Every single one of the projects that are on this site right now are super underpaid...

It's sad that even the highest bidding project is $500/mo.


I don't think that's the bid to build it. The site's premise seems to be that multiple people would commit to being customers of a new app/service - pre-validating the market, in other words.


In which you have to "provide your own accountant"


To the now 9 people who said they want this and the rest like me who didn't enter your information - do you want industry-specific (but of course company-agnostic) code examples or are you amply satisfied with audio walkthroughs, as in once or twice a week you get a free podcast, and your $11/month could pay for, e.g., transcripts of the conversations?


Some zeros are definitively missing.

I know a company which paid around 1M euros to get such data ( and some software ) for just one industry.


Do you think the management who made this decision would pay for this service in an industry-specific but company non-specific form on a subscription basis?

More

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

Search: