News for hackers. Stuff that matters.
Re:The art of over-engineering your side projects by kerkeslager on Friday September 01, 2017 @09:20AM (#15148106)
Potential customers do care about the stack you're running. They care if they have to download Java or Flash. They care if they have to be connected to the internet or can use your product offline. They care if your program starts quickly. They care if your program runs quickly once started. They care if your program has bugs (let's not pretend different languages aren't more or less error-prone). They care if your program is cross-platform. They care if your UI is consistent with their platform. They care if your product releases new features quickly.

All of these are stack-related.

Re:The art of over-engineering your side projects by scott_karana on Friday September 01, 2017 @11:50AM (#15149526)
Those are all client usability concerns, and none of them are stack intrinsic.
Re:The art of over-engineering your side projects by mark-r on Friday September 01, 2017 @12:38PM (#15150058)
I think the point was that user doesn't care about your stack, but they care about the consequences of the stack you've chosen. It's a subtle but important distinction.
Re:The art of over-engineering your side projects by scott_karana on Friday September 01, 2017 @10:44PM (#15153922)
Of course. My point was that it's fairly common to write slow/unsuitable applications in spite of a stack's strengths, while stack limitations (or strengths) are generally overstated, depending on trends.

Proper engineering and design are required no matter what you choose.

No silver bullets ;-)

Re:The art of over-engineering your side projects by kerkeslager on Saturday September 02, 2017 @06:55AM (#15155338)
There are no silver bullets, but there are wooden bullets that are totally ineffective.
Re:The art of over-engineering your side projects by kerkeslager on Saturday September 02, 2017 @02:31PM (#15157471)
Have you figured out a way to make a mature implementation of the JVM start up fast? Nobody else in the industry has.

Is there some way I know of to package Flash games so that Firefox users can play them without downloading Flash?

I get that done of the examples I mentioned are arguable, but some of these are pretty unambiguously stack intrinsic. Some usability concerns cannot be addressed in some stacks.

Re:The art of over-engineering your side projects by user5994461 on Friday September 01, 2017 @09:54AM (#15148315)
Packaging and designing an application is a developer's problem, not a user problem.
Re:The art of over-engineering your side projects by always_good on Friday September 01, 2017 @11:57AM (#15149597)
Notice how just about none of them are the user caring about your stack.

In other words, when confronted about your high bug rate, you're not going to get anywhere going "heh, you see, Python was just more convenient than a statically-typed language and this lead to..."

Re:The art of over-engineering your side projects by marcosdumay on Friday September 01, 2017 @07:08PM (#15153014)
All of those are pretty much influenced by your stack. If you need a highly reliable software, you would be stupid to write it in Python.

You are right that nobody will care if you use them as excuses. But that is not what the GP said.