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.
[ Parent
| on HN ]
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.