Programmers of proprietary software: Why they don't belong here

frieza · 01-04-2011, 05:01 PM

i would say LQ is about a community of people volunteering their time to answer questions, no questions asked (well with the exception of where it comes to telling someone how to do something illegal)
even homework questions are acceptable as long as the poster understands he/she might not get a direct answer but a reply that will help the poster understand how to find the answer or an answer that lead the poster to the solution, so why would a professional programmer who gets stuck be treated any differently? even if the code in question ends up in a proprietary program the answer to the question might help out someone else doing a similar open source project. That's what this forum is about, not discriminating why a question is being asked and by whom.

onebuck · 01-04-2011, 05:13 PM

Hi,

Quote:

Originally Posted by Kenny_Strawn

This is LinuxQuestions.org, and people who post here are forced to give away their code anyway when they need help, and I agree with that trend. As such, programmers of proprietary software shouldn't be here unless they want their entire source code revealed to the public. Thanks LQ programming forum for doing its best to kill at least *new* proprietary software!

You are ridiculous with this one! People who write code for contract in no way should be required to adhere to such a ridiculous rule. Loads of Open Source programmers code and program snippets are developed by people who have day jobs or contracts to program for hire.

I have not contracted for a while but in no way would adhere to such an absurd rule.

"Wisdom is only found in truth."-Goethe

Grow up! When you get a job then the picture will change for you or the job will change you or else you won't have that job.

“Politeness goes far, yet costs nothing.”- Samuel Smiles

onebuck · 01-04-2011, 06:31 PM

Hi,

Quote:

Originally Posted by Kenny_Strawn

Well when people submit threads asking for help with their programming they are *forced* to post their entire source code, aren't they?

Enlighten me Kenny! Where do you come up with this or how do you base the requirement?

Kenny_Strawn · 01-04-2011, 07:05 PM

Sorry onebuck; apparently my question was already answered by dugan.

Sergei Steshenko · 01-04-2011, 08:27 PM

Quote:

Originally Posted by onebuck

When you get a job

If ...

onebuck · 01-04-2011, 08:28 PM

Hi,
@kenny
Your questions may have been answered but what about direct queries to you. How do you justify this position.

dugan · 01-05-2011, 01:00 AM

Quote:

Originally Posted by onebuck

Your questions may have been answered but what about direct queries to you. How do you justify this position.

Onebuck, one of Kenny Strawn's merits is that he knows when to quit. The position he took in his first post was indefensible, and he should be allowed to drop it quietly if he wants to. Personally, I think it was the result of partying too hard during the New Year celebrations.

grail · 01-05-2011, 01:25 AM

Quote:

I think it was the result of partying too hard during the New Year celebrations

Well only the hypocrites here would argue against this one ... LOL

resetreset · 01-05-2011, 09:51 AM

Quote:

Originally Posted by dugan

Yes, it's crazy.

If it's a password to get into your system, you store a hash and a salt. When the you get a password to verify, you apply the salt to the password, hash the combination, and compare what you get to the stored hash.

If it's a password to get into another system, you store it in a configuration file and have your source code read that file.

In neither case do you put the password in your source code.

No, I was talking about passwords for MYSQL databases in PHP code. OK, I'll have to read what you said again to understand it

, but how do I do all that in PHP?

dugan · 01-05-2011, 10:19 AM

Put the MySQL password in a configuration file, separate from the PHP source. Have your PHP read that file when it needs to.

frieza · 01-05-2011, 10:20 AM

Quote:

Originally Posted by resetreset

No, I was talking about passwords for MYSQL databases in PHP code. OK, I'll have to read what you said again to understand it

, but how do I do all that in PHP?

file config.inc

Code:

$user=user;
$pwd=password;
$database=dbname;
$dbhost=dbhost(often localhost except on hosting providors);

index.php

Code:

require_once('config.inc');
$sqli = new mysqli($dbhost,$user,$pwd,$database);

hope this helps
even if you don't do something like that you can still replace usernames/passwords with dummy usernames/passwords when posting, most everyone, myself included does that, i even do that with IP addresses in config files/scripts for routers as not to reveal the internal workings of a network, it's called Redaction