4 ms·

> how your frameworkless design handles a dozen different features that their use case absolutely requires Would you mind sharing one or two kind of feature th

> how your frameworkless design handles a dozen different features that their use case absolutely requires Would you mind sharing one or two kind of feature that are required by these development team ?

lolinder 1y ago
I could, but it would be a distraction because my entire point is that there are an enormous variety of apps with a large variety of requirements being deployed on the web. If I give examples that's going to turn into an argument over whether these specific examples actually need a framework, which will turn into a whole bunch of other hypotheticals of situations that would justify it or situations that won't. Rather than opening up that can of worms I'm going to leave it where I left it.
- aucisson_masque 1y ago
  Holy moly, that's pretentious. I was genuinely curious because i never faced the kind of issue a web development team would have, it wasn't about counter argumenting. You could have just said "x and y".
  - lolinder 1y ago
    I'm not trying to be pretentious, but wrangling an HN thread is hard and I don't have time to get into an argument about a bunch of different implementation details. Rather than just ignore your post I decided to respond explaining why I couldn't answer. The only valid short answer is what I said: that it really depends on the details and how they all work together. I truly can't give you features in isolation that won't be questionable, because the decision hinges on the whole combination of factors. Had I said "x and y" someone would have come along and argued that X and Y didn't call for a framework because Z. Me identifying the two points would have accomplished nothing and would actually have undermined my primary point of "it depends". Edit: btw, I just corrected the downvote on your original post with an upvote. Whoever did that probably assumed you were being belligerent, but that's not fair.
    - aucisson_masque 1y ago
      Well thank you for at least being willing to reason. I get its complicated, wasn't trying to nail you or web framework.

lolinder 1y ago

I could, but it would be a distraction because my entire point is that there are an enormous variety of apps with a large variety of requirements being deployed on the web. If I give examples that's going to turn into an argument over whether these specific examples actually need a framework, which will turn into a whole bunch of other hypotheticals of situations that would justify it or situations that won't. Rather than opening up that can of worms I'm going to leave it where I left it.

aucisson_masque 1y ago
Holy moly, that's pretentious. I was genuinely curious because i never faced the kind of issue a web development team would have, it wasn't about counter argumenting. You could have just said "x and y".
- lolinder 1y ago
  I'm not trying to be pretentious, but wrangling an HN thread is hard and I don't have time to get into an argument about a bunch of different implementation details. Rather than just ignore your post I decided to respond explaining why I couldn't answer. The only valid short answer is what I said: that it really depends on the details and how they all work together. I truly can't give you features in isolation that won't be questionable, because the decision hinges on the whole combination of factors. Had I said "x and y" someone would have come along and argued that X and Y didn't call for a framework because Z. Me identifying the two points would have accomplished nothing and would actually have undermined my primary point of "it depends". Edit: btw, I just corrected the downvote on your original post with an upvote. Whoever did that probably assumed you were being belligerent, but that's not fair.
  - aucisson_masque 1y ago
    Well thank you for at least being willing to reason. I get its complicated, wasn't trying to nail you or web framework.