This page is completely empty on iOS. I guess the author should have made a minimalist static HTML page instead.
Is it HN's hug of death? I see the same on my PC.
Minimalism – An undervalued development skill
71–80 of 179 posts
Re: Minimalism – An undervalued development skill
#72I just see a blank grayish blue page.
Re: Minimalism – An undervalued development skill
#73Feature minimalism is a good thing to strive for usually.
Wrote my own dirt simple lazy loader & slider libraries, because I didn't need many of the features other libs had.
On the flip side, if I need a reasonably complex component that would take quite a while for me to implement, like say. A date picker. I just grab the lightest weight, good looking one that I can find. (That also doesn't appear to be abandoned)
Minimalism in everything, even minimalism.
Re: Minimalism – An undervalued development skill
#74Earlier quoted context omitted.
It looks like yours was a case of NIH syndrome. That has nothing to do with minimalism.
NIH is absolutely relevant here since article showed 3 (out of 3) examples of it.
The comment was relevant, and welcomed. Sorry if my response gave other impression. I just don't agree with that premise of the article.
There is extremely bloated software that can be replaced by a few lines of code but, in general, minimalism is hard to get right and requires a high level of expertise.
Re: Minimalism – An undervalued development skill
#75[deleted]
Re: Minimalism – An undervalued development skill
#76I just see a blank grayish blue page.
This was due to a comment from a removed user. Now fixed. Thanks!
Re: Minimalism – An undervalued development skill
#77Re: Minimalism – An undervalued development skill
#78We embraced minimalism on my team a long time ago—no tests, no docs or comments, variable names are usually 1 or 2 characters, no indentation, no code reviews or QA, no meetings, etc.
Re: Minimalism – An undervalued development skill
#79Re: Minimalism – An undervalued development skill
#80I have super mixed feelings on this. Minimalism makes for a clean, easy to understand codebase, that avoids some of the performance pitfalls associated with bigness. But sometimes it’s easy to build 80% of what you need, and then massively difficult to get to 100%, and the ease of getting to 80% can lead you astray. For instance, I can write a pretty fast matrix multiplication algorithm in maybe a few dozen lines of…
If you need the full power of BLAS, etc then it’s absolutely the right call to use the library. The situation outlined in this article is different: you just need one function (say dot product) and so the minimalist approach is to not take the dependency.