[HN Gopher] Platform Strategy and Its Discontents
       ___________________________________________________________________
        
       Platform Strategy and Its Discontents
        
       Author : wmanley
       Score  : 41 points
       Date   : 2024-10-27 19:46 UTC (3 hours ago)
        
 (HTM) web link (infrequently.org)
 (TXT) w3m dump (infrequently.org)
        
       | kevinsync wrote:
       | PREACH
        
       | ickelbawd wrote:
       | I have some sympathy for this viewpoint. And I think Alex's heart
       | is in the right place--Nextjs is a dumpster fire and react server
       | components are when react finally jumped the shark for me.
       | 
       | Maybe if we had HTML6 we wouldn't be in this scenario. HTML5 was
       | great but form building on the web (without JS) is a second-rate
       | experience. And it's even more miserable once JS is in the mix,
       | but hey developers can provide a much better UX for end users
       | than HTML and CSS alone could possibly provide.
       | 
       | Sorry Alex, but without JS the web would have died a decade ago
       | as phones took over. It's only JS that keeps us in the ring.
        
         | Devasta wrote:
         | HTML can never be improved, that is at the very foundation of
         | its current form. We are 20 years into the takeover from the
         | W3C and still can't even do a PUT request without JS, nevermind
         | anything approaching even one tenth of the functionality of
         | XForms.
         | 
         | The web of semantic documents died years ago, it's an
         | application platform now and that means JS. HTML is naught but
         | a payload carrier.
        
       | devjab wrote:
       | This is a very good article and I agree with most of it. I never
       | really understood why React and Angular became big for the
       | general web. They have a lot of usage in enterprise applications,
       | where you typically access them from a "pc", but even then they
       | suck on the tablets your employees drive around with. At least
       | for the most part they don't suck that much worse than the
       | terrible native clients that came before (and still do in the
       | rare case that a supplier actually build a native mobile app).
       | Why that spread to the wider web is beyond me though. I get why
       | you would use it for personal projects if it's your day time job
       | anyway, but a page reload never hurt anyone.
       | 
       | I personally think that the most responsible "father" is finance.
       | The article states that there is more money with the web, but in
       | my experience it's far easier to lock down payments through apps.
       | I agree that part of this is because native apps are better on
       | mobile, but they are also much easier to work with and consume.
       | It's not easy to make payments function well on the web while in
       | a native app it's just a click with well powered api behind it.
       | Serving both users and developers. Now, it probably could be
       | easier on the web, but who would deliver it? The article calls
       | out Apple and to some degree Google as guilty of not making
       | browsers competitive with mobile apps, but why would they? If
       | anything it's in their best interest to keep the web shitty on
       | mobile.
        
       ___________________________________________________________________
       (page generated 2024-10-27 23:00 UTC)