7 ms·

> There is a huge amount of man-hours poured into making these frameworks work correctly under any condition. The path is littered with the ghosts of framework

• enlyth 4y ago
  That's like saying I should use a steam engine today because the electric motor will be superseded someday.
  • furyofantares 4y ago
    The way it played out with jQuery is that there was a transition period; gradually more and more classes of app didn't need to be built with jQuery and it was easier to build them without it. The implication was that we're in a transition like that presently.
  • wwweston 4y ago
    Or maybe it’s more like saying ICEs will be a ghost one day? EVs were once the path not taken…
  • louthy 4y ago
    I said no such thing.
    • xwdv 4y ago
      You implied it. What you should have alluded to is that it is necessary to use technologies today that won’t necessarily be in use in the future, merely as a stepping stone to get us to the next destination, where we will use a new but still temporary technology.
      • NegativeLatency 4y ago
        I think op was suggesting someday we’d be on hoverboard or something
        • warcher 4y ago
          We're all gonna be debugging wordpress apps in the metaverse while our self-driving cars whisk us down the freeway.
      • ldiracdelta 4y ago
        As Scott Adams says, "Analogies are for fighting." If you try to counter a statement with an analogy you almost always simply get a fight.
        • MonaroVXR 4y ago
          Never thought about that, where do you get this from? But it kinda rings true for me in life.
          • ldiracdelta 4y ago
            I heard it from Scott Adams, the creator of Dilbert. In addition to writing that comic he is a very interesting thinker. He is also a trained hypnotist.
            • slkdk32 4y ago
        • eyelidlessness 4y ago
          Quoting absolutes expressed by highly opinionated people is also for fighting. Not saying you shouldn’t, but maybe there’s some nuance missing. Not even saying the particular analogy was devoid of conflict, it has plenty of room for disagreement. But it didn’t feel to me like it was inviting any which wasn’t already present.
          • ldiracdelta 4y ago
            I would classify Scott Adam's statement as a trueism -- true for most people, under most circumstances, for most times. Unfortunately, couching a trueism in its most precise linguistic form with associated probabilities and error margins is a path to simply being ignored. Once a thread switches to rhetoric, dialectic responses are like pissing in the wind, forgive the analogy :-)
            • 4y ago
  • orangepurple 4y ago
    The steam engines will continue to run on coal after the natural gas to the power plant is shut off and the power stops working for the electric trains
  • kristopolous 4y ago
    That's not the dynamic. It's people that think electric motors are always the right solution to every problem and it's only a matter of rube Goldberging it up to shoehorn electric motors in to places that that's better without them. It's against arrogant dogmatic rose colored glasses fanboyism being mistaken for software engineering And this isn't straw-manning, the internet is full of these evangelists that exist as effectively marketing arms, as if they're bicycling around wearing nametags on behalf of the Church of Current Day Frameworks. All it does is create messy piles of tangled garbage that wastes people's times and gets thrown away to be rewritten when the next flashy thing comes around. It's hot fashion for programming It's gross and needs to stop. Seriously. Let's build the future, help fix the world's problems and quit fucking around. This fetishism for shiny things have left us impotent executioners of meaningful change and thus we are amidst the tech stagnation
  • xigoi 4y ago
    If an electric engine makes your vehicle noticeably slower and heavier, there's a reason to keep using a steam engine.
• nawgz 4y ago
  That’s a pretty funny stance. The library has a gigantic developer share and is supported by a tech giant. A world where React isn’t used and remembered is one where the web isn’t based on the same primitive. The idea of a thin layer on top of JS offering composition is not complex, and the execution by react is still trend setting. Remember when they introduced hooks and now tons of libraries have the same thing? That’s not because React is behind the times and possible to supplant as a small team
  • metadat 4y ago
    > The library has a gigantic developer share.. So did jQuery, and that google framework used to create Gmail, what was it called? Oh yeah, nobody cares anymore because they're irrelevant in 2022.
    • leodriesch 4y ago
      And jQuery is still used in lots of places without any problems AFAIK. Even if the React development team would stop the framework will for sure be around for a couple more years and receive at least security patches.
      • mst 4y ago
        I've worked on webapps that are part jquery, part classic angular, part react, and part angularjs. My opinion of each of those parts has been primarily down to the developers, not the underlying choice of framework. Things that work in production last.
      • metadat 4y ago
        jQuery has faded into the background, no longer interesting. React has too many sharp edges, it'll only be here until something shinier supercedes it.
        • sebmellen 4y ago
          What sharp edges? (This is an honest, curious question.) I don't find many sharp edges in day-to-day React work. I say this having once been a very strong proponent of framework-less frontends, before trying Vue, then Svelte, and then settling on React.
• panny 4y ago
  I can advertise for a "React developer" and find people familiar with react rendering. I will never be able to do that with in-house render solution. This will apply to whatever replaces react as well. Unless I'm selling a render solution, I don't want to be maintaining a render solution. Maintaining glue code might suck, but writing everything from scratch limits the scale of the work that a person can accomplish. I liken it to polishing gears rather than driving the car.
  • ludamad 4y ago
    I think that's the biggest thing to me. It's easy to say 'we can do just fine without $BAG_OF_TOOLS, there's no real need for it, it's simpler and faster and we get off the ground with it', but then once you have enough people that a bag of tools is needed, you create an in-house bag and soon you have a 'simple' system for managing state that is nevertheless much less exciting to the new cohort of $BAG_OF_TOOLS bootcamp graduates, etc. And people pointing to the framework graveyard ignore that you need to hire people now, not 10 years from now. If 10 years from now React is as obscure as an in-house framework, meh?
• Gigachad 4y ago
  The longer something has existed on top, the longer it will continue to. React still hasn't peaked yet. Its tail to obsolescence will outlast anything you build in it today.
  • ehnto 4y ago
    Which is certainly more about popularity and subsequently littering the world with soon to be legacy apps. React and Wordpress, pick those up and you'll have work for your whole career I suspect. Also a legacy knowledgebase on how to achieve just about anything with both of those tools.