Comment by mhitza

Comment by mhitza 9 hours ago

15 replies

The javascript people should stop innovating for a couple of years. To much innovation that lead nowhere. How many ways can one build a web javascript project?

Browser people should pick up slack and start developing sane components for the web. How about a backend-supporting combobox, or a standardized date picker across browsers? Then we wouldn't need to constantly innovate how we manage the state of those fundamental operating controls that browser still don't have in 2025.

mrsilencedogood 8 hours ago

I think part of the problem is that browsers don't really serve their original purpose anymore.

Google functionally controls just enough of a monopoly via chrome that they can generally do whatever they want (and not do whatever they don't want to do). So that standards still mostly can't do anything google isn't enthusiastic about dumping dev time into.

And they're just barely not enough of a monopoly that they can't just go wild and actually turn the browser into a locked down capital-P Product. Safari and Firefox (in that order... much to my chagrin) are holding them back from that.

So browsers just kind of hang out, not doing too terribly much, when obviously there are strong technical forces that want the browser to finally finish morphing from a document viewer to an application runtime. Finally fulfill the dream of silverlight and java applets/JNLP and so on. But nobody wants to bother doing that if they don't get to control it (and firefox doesn't have the dev power to just trailblaze alone in OSS spirit).

So instead the js people just have to plow along doing their best with the app-runtime version of NAND chips since the incentives don't want to offer them anything better at the browser/platform level.

  • branko_d 26 minutes ago

    > app-runtime version of NAND

    In the last 10 years, 3D NAND memory has scaled 10x (in bits per unit area). So… maybe not the best analogy?

  • ChadNauseam 7 hours ago

    > Google functionally controls just enough of a monopoly via chrome that they can generally do whatever they want

    Crazy statement. Any API not supported by Safari might as well not exist.

    • paulryanrogers 2 hours ago

      How many APIs in Chrome today will never appear in Safari?

      WebSQL? WebUSB?

      It seems like Safari bends towards whatever is in common use, at least within a few years.

  • jgalt212 8 hours ago

    > there are strong technical forces that want the browser to finally finish morphing from a document viewer to an application runtime

    I really hope that never happens if only because the web dev on ramp will discourage anyone without preexisting technical chops.

    • ozim 4 hours ago

      We are mostly there and I am all for it.

      No other GUI runtime or framework delivers true cross platform implementation. HTML, CSS and js are as open and as standard as it gets.

      GTK sucks in its own ways and is not international standard.

    • pdntspa 2 hours ago

      > because the web dev on ramp will discourage anyone without preexisting technical chops.

      This is a good thing! It keeps salaries high and keeps the dilettantes out. I am sick of getting my work devalued by morons

      There are too many people trying to build "tech" who shouldn't be. We need more gatekeepers

ggregoryarms 7 hours ago

To be fair browsers/CSS have been solving a lot of use cases you'd normally turn to js for, lately. We should continue escalating this effort.

__MatrixMan__ 4 hours ago

I'd go further and suggest that we need maybe five or six browsers. One for shopping, one for banking, one for socializing...

Let the platforms for these things compete on the back end only and provide a uniform experience on the front end across competitors. This way the people writing the code that runs on our devices don't have conflicts of interest that lead them to betray their users.

It would also be easier to use because once you know the structure/flow/hotkeys for one bank you're now wizardly at navigating the interface for every other bank.

It's just such a waste to have each business writing a separate front end even though what they end up with is always more or less identical to their competitor.

Sandwich shops should compete by making a better sandwich, not by outmaneuvering each other re: how they leverage the app they managed to get 8% of their customers to install.

scuff3d 7 hours ago

Frankly it's incredible what any of these frameworks have been able to accomplish given the bonkers platform they have to work on.

HTML, CSS, and JS made sense back when the web was primarily text with some simple forms. It's a dog shit foundation to build highly interactive apps on. The whole thing needs to be thrown out and rebuilt.

  • MiiMe19 6 hours ago

    Webapps were a mistake :(

    • scuff3d 4 hours ago

      The frustrating part is that the idea is incredible. Everyone has this piece of software on their computer that lets them run anything as long as there is a server to talk to. I love it. I don't want to have to download a thousand apps, especially not for shopping or banking. Just using a web interface is awesome.

      Unfortunately we decided the correct way to provide the functionality was by layering bonkers ass abstractions on top of a system meant to largely display static text and images. In the year 2025 there is absolutely no reason we shouldn't have a unified coding language that allows you to render things in a web browser in a sane way.

      At the very least we should have seen a substantial expansion of what HTML is capable of, closer to what HTMX is doing now, with a better way to style everything then fucking CSS. People complain about JavaScript but for my money CSS is the greatest sin.

    • Tubelord 6 hours ago

      Almost all phone apps could be a web app

      • tcoff91 2 hours ago

        A great native app on an iPhone feels far superior to a mobile website. The gestures, the stack navigator, haptics, scrolling, native ui primitives, etc…

        Also iOS accessibility screen reader APIs are way better than the web. Accessibility actions for instance are great.

        • bave8672 2 hours ago

          It doesn't have to be this way though. What you're describing is a result of Apple intentionally prioritizing native over web apps to maintain control of their lucrative walled garden.