151–160 of 322 posts
Also, I realize he's mad, but he really needs to expand his expletive vocabulary :)
I don't think that's remotely true if you keep the responsive web app simple. YNGNI and KISS and what not. I've been doing this for over ten years. In that time I've seen large web applications built for under 4k; I've also seen massively overbuilt simple applications go for 50k+. It comes down to often how needlessly complex you make the stack. If you stick with solid simple guaranteed tech instead of cutting edge y…
Not to mention that every time we add a new feature or change something in the web app, that change now needs to be duplicated in two native code bases as well.
If anything the opposite is true: you can only afford to build native apps as a larger company.
Earlier quoted context omitted.
If only we could get notifications for replies & a decent mobile app existed.
I just check a couple times a day... honestly, I'm usually too busy when I'm not checking HN to deal with a reply right at any given moment anyway. It's a forum.
Earlier quoted context omitted.
Did we read the same article? What is this condescending bullshit. Nobody is arguing these things CAN'T be done, just that it's too much effort on the web, and the only web devs that know the ins and outs of every browser enough to make it work are unaffordable and unavailable.
I'm available... and semi-actively looking... ;-) But I'm not cheap. That said, I provide great value. I've been writing web based applications for about 20 years now. It's a lot better than it was in the late 90's and early 2000's, so stop bitching or get off the lawn. (sarcasm) Seriously though, I'd much rather deal with webpack, babel, react, redux and the like than angular 1&2 (just feels like a decade old soluti…
That's the killer.
Earlier quoted context omitted.
this is also pretty substantive. Fuckity fuck fuck fuck you, and shut the fuck up, dear reader. More fuckity fuck because the author has a keyboard macro that expands "," to "fuck". I don't know, I thought it was pretty much a waste of my time. Read the top of the page you're looking at right now, read my first sentence. There, saved you a few minutes.
It does make a couple of interesting points: 1. The cost of building an app can be calculated in the back of a napkin. The cost of a web app that works consistently across devices? Not so much. 2. The cost of building backend services has been commoditised to a degree. Front end web development? Its downright hard finding someone that can do good front end web work. 3. The reality that big companies (silos) will push…
Seems like you're deferring one dragon for another. Deliver the project got easier; "Control the customer" got significantly harder. You've now got someone's app store in the middle of your customer relationships and are exposed to approval drama, various forms of revenue squeeze, and other meddling from the platform owner. What happens if the folks running the platform decide to launch their own offering? Speaking a…
Apps don't have to be downloaded from stores, thought that certainly does make things nice.
Another thing that stood out to me: "a closed ecosystem will always deliver higher quality in any given moment." Which is so absolute it's ridiculously easily disproved, even while being true at certain points.
Earlier quoted context omitted.
Did we read the same article? What is this condescending bullshit. Nobody is arguing these things CAN'T be done, just that it's too much effort on the web, and the only web devs that know the ins and outs of every browser enough to make it work are unaffordable and unavailable.
What I thought the author was trying to say was that you can make a car that floats. It's just a much better understood problem to buy a car and a boat, then call it a day.