A new hot pepper database - with an emphasis on keeping track of names and varieties?

Well I was gonna say "thanks for all the posts and interest" till I saw the programming language argument/tangent...
 
Juanitos, I like the format of your website, the simple varieties list looks really nice. However your SSO wasn't working for me, nor was the Captcha for a normal user registration, so I couldn't make an account. Who knows, maybe a glitch on my end.
 
When I was wanting to do this, my main way to target/improve participation was ease of use/simplicity. If you only ask a couple of questions about a pepper, like Describe its shape, color, and give me all the names you know for it, you could pretty quickly build the size of your database yourself, and it wouldn't take too much effort for other contributors to add a lot of data as well. All you'd have to do was pull up a seed seller's website and go down their list, entering what you saw. But if you're asking a veritable survey of questions for each pepper, although you get more info per-pepper, my point (and the falling-short of many lists and databases) is that you don't end up with a lot of records, a lot of different peppers catalogued, because each pepper requires so much effort to log.
 
Unfortunately with a new job and some other responsibilities these days, I don't have a lot of time (or interest) to give to these sorts of projects. However I've set up a spreadsheet tonight that we can try to use as a starting place, and see how that goes:
 
Spreadsheet
 
I haven't had time to enter my data yet, but try starting with just putting the basic info of the specific cultivars you've grown, and go from there. Really, the goal is a big list with a little info on a lot of varieties, crosses, F1 hybrids, etc.
 
Speaking of which - if you are adding a cross or non-stable variety, be sure to note if it is the F1 you are describing and giving a name to, or a cross that's been stabilized over many generations, or something in-between.
 
Let me know what you think.
-Pimental
 
internationalfish said:
 
Haha. First, I didn't say no JS; I said if your site 100% does not work without JS, you've shat the bed. Python has its warts, absolutely, but saying "x isn't perfect so don't criticize y" is truly ridiculous. PHP is fundamentally garbage from a language design standpoint. JS really isn't a lot better, and using it on the server might have been the worst web development idea in the last decade... it seems to me you could benefit from expanding your experience a bit. I made the same kind of arguments before I actually invested myself in learning tools that suck a lot less.
 
SPAs are a terrible idea from the standpoints of usability, indexability, testability, etc... in the first place, so yeah, also not a very compelling point.
 
You don't know what you're talking about. It's easy to test frontend SPAs built in react. It also sounds like you don't know wtf memorization is. Reusable components get no points in usability? SPAs are absolutely brilliant. You're clueless. Yeah, all three of these languages have warts. I'm writing a Linux app in c as we speak, so it's pretty stupid to assume I need to expand my experience. I don't even like php, but I'm not going to crap on someone who does. At least he built something that works. What are you going to suggest he use? He reused code to fit his needs here, which makes more sense than rebuilding it in python, which would be slower btw. Python is also slower than nodeJS, which you're also crapping on because it's not your preferred technology.
 
Dulac said:
You don't know what you're talking about. It's easy to test frontend SPAs built in react. It also sounds like you don't know wtf memorization is. Reusable components get no points in usability? SPAs are absolutely brilliant. You're clueless. Yeah, all three of these languages have warts. I'm writing a Linux app in c as we speak, so it's pretty stupid to assume I need to expand my experience. I don't even like php, but I'm not going to crap on someone who does. At least he built something that works. What are you going to suggest he use? He reused code to fit his needs here, which makes more sense than rebuilding it in python, which would be slower btw. Python is also slower than nodeJS, which you're also crapping on because it's not your preferred technology.
 
Memorization? Do you mean memoization? How very impressive, you manage to fail on both ends of the spectrum, too high and too low. You have no idea what the hell you're talking about. I do feel sorry for you, because I'm pretty sure you're right where I was about ten years ago. I am glad I actually learned those lessons, though, and it'd be just lovely if you could learn them as well without embarrassing yourself at 40. It's almost as pathetic as your chosen ecosystem; pip isn't perfect, but then it doesn't suffer from the juvenile inanity that occasionally results in npm packages just not existing or violating licensing, so hey. Maybe that's something.
 
The idea that one programming language being slower than another in execution time is important is incredibly facile. No one would argue that Python is fast compared to most popular languages. But then if running fast is the only metric you think is important, just pipe everything to /dev/null. Your precious Linux C app will run like wildfire. I disagree with your choice of technology because you have chosen poorly, and being an asshole about it doesn't make you any less wrong.
 
Pimental, I apologize for my role in derailing this, but I just have a really hard time watching morons like this guy spray stupidity. I hope your project goes well, and I'll bow out now.
 
internationalfish said:
 
Memorization? Do you mean memoization? How very impressive, you manage to fail on both ends of the spectrum, too high and too low. You have no idea what the hell you're talking about. I do feel sorry for you, because I'm pretty sure you're right where I was about ten years ago. I am glad I actually learned those lessons, though, and it'd be just lovely if you could learn them as well without embarrassing yourself at 40. It's almost as pathetic as your chosen ecosystem; pip isn't perfect, but then it doesn't suffer from the juvenile inanity that occasionally results in npm packages just not existing or violating licensing, so hey. Maybe that's something.
 
The idea that one programming language being slower than another in execution time is important is incredibly facile. No one would argue that Python is fast compared to most popular languages. But then if running fast is the only metric you think is important, just pipe everything to /dev/null. Your precious Linux C app will run like wildfire. I disagree with your choice of technology because you have chosen poorly, and being an asshole about it doesn't make you any less wrong.
 
Pimental, I apologize for my role in derailing this, but I just have a really hard time watching morons like this guy spray stupidity. I hope your project goes well, and I'll bow out now.
 
It was a typo. Point out the problem with the stack and show a better option or shut up. SPAs were not around 10 years ago. JS has changed big time. I use MERN professionally and other stacks. Not sure why you feel the need to berate people. I'm guessing you feel like a insecure hack. My c app runs well /shrug. Python is slow. Show me a benchmark where it beats another popular language. I agree that doesn't make it bad. It's the crappy OOP, FP, and module system that do. Its perk is libraries built in c/c++.
 
Edit: I suggest you take a look around and see what major websites are using. Mostly React.
 
Welp, I was hoping someone would contribute to the list, but...^
 
Actually, there are definitely some good suggestions early on about how to get people to contribute, thanks juanitos, slewis, and especially pollennut. I'm not sure what my thoughts are yet, the spreadsheet is still open, and I'll try to add my own peppers soon. It may be a flop of an idea, and it is a lot of work to put together, regardless. I did add a 'source' column, so that you can put a way to get each variety if you're interested. Honestly the best thing to do might just be to just attach to some existing database, like that of juanitos.
 
Pimental said:
Welp, I was hoping someone would contribute to the list, but...^
 
Actually, there are definitely some good suggestions early on about how to get people to contribute, thanks juanitos, slewis, and especially pollennut. I'm not sure what my thoughts are yet, the spreadsheet is still open, and I'll try to add my own peppers soon. It may be a flop of an idea, and it is a lot of work to put together, regardless. I did add a 'source' column, so that you can put a way to get each variety if you're interested. Honestly the best thing to do might just be to just attach to some existing database, like that of juanitos.
 
I think a few more columns would be good such as heat level and species.
 
Honestly, in looking more at the database website @juanitos made (pepperdatabase.org), I really like it and I think it's probably suitable for what I'd want.
 
Right now, you have to add a photo of each pepper variety you add, but if you've grown it before, all you'd have to do is add the photo and the most basic info about the pepper, and we'd probably be able to expand the PepperBase pretty significantly.
 
I guess I can keep the spreadsheet open, but I don't think it's as useful as what juanitos has already put together, even if the spreadsheet is a little faster right now.
 
Best,
Pimental
 
Top