hasanhaja

8 ms·

31.
by hasanhaja 1y ago
Syntactical preferences are subjective though and are prone to familiarity bias. I started my webdev career with React so I'm really familiar with JSX and like it, but that alone isn't enough to make engineering decisions. I think
32.
by hasanhaja 1y ago
Great article! The thing I find most frustrating in the "winning by momentum not merit" place we're in, is that the merits aren't just technical. Frameworks like Svelte are simpler to understand and keep in your head, wh
33.
by hasanhaja 1y ago
How's your experience maintaining styles written in this manner? My experience has been increased cognitive load when I come back to tailwind styles after a long time, when compared to dealing with handwritten CSS selectors and classes
34.
by hasanhaja 1y ago
No, but doing the rendering through JavaScript in userland will be slower than letting the browser handle it
35.
by hasanhaja 1y ago
Why does this have to be the baseline architecture when you can render the HTML on the server with the template and data? Why send the data and the JavaScript to parse that data and transform it into HTML in a users browser when you can do
36.
by hasanhaja 1y ago
But this is exactly the point of the article. That'd be like if I needed to build a car, I started with a rocket blueprint in case I also need to go to space in the future. The cost of speculating a highly interactive site that users w
37.
by hasanhaja 1y ago
Are we aligned with the claims in the article that a SPA architecture is not a suitable baseline architecture for content-focused sites with shallow sessions (low number of interactions)?
38.
by hasanhaja 1y ago
How does something like React help with any of the trickier UX problems you're describing?
39.
by hasanhaja 1y ago
But if you don't know the underlying platform, how can you be sure that your framework is high level enough or that it can do everything that's possible on the platform? You either have a framework with escape hatches (that'l
40.
by hasanhaja 1y ago
But don't you need to need to understand the platform you're building on, warts and all? How else can you fully grasp what's possible on that platform and the costs of different abstractions?
41.
by hasanhaja 1y ago
Like what specifically? And why do you think Astro is not a good fit for it?
42.
by hasanhaja 1y ago
There are a lot of moving parts when building an application and the abstractions that Next.js provides doesn't cover the same stuff when compared to frameworks like Ruby on Rails, Django and Laravel. The narrow band of problems Next.j
43.
by hasanhaja 1y ago
Yeah, this is my gut-feeling too! Because the alternative for "complex" being discussed is Next.js, but that doesn't really help you with "complex" applications, and you still have to bootstrap a lot of infrastructu
44.
by hasanhaja 1y ago
What do you mean by complex?
45.
by hasanhaja 1y ago
What about DX in terms of template execution speed? There are many implementations of template fragments on various platforms like Go and Rust [1], which might arguably perform better than their JavaScript counterparts. Wouldn't quicke
46.
by hasanhaja 1y ago
Do you have an intuition of when something becomes hefty and complicated, and would require a full stack solution like Next.js?
47.
by hasanhaja 1y ago
> there wasn’t a developer experience by which you could build a website or web app (or both) as a single, cohesive unit, covering both front-end and back-end How much of the frontend and how much of the backend are we talking about? Con
48.
by hasanhaja 2y ago
Been wanting to learn browser APIs like Service Workers and IndexedDB in depth, and HTMX, so started building a Todo App: https://github.com/hasanhaja/tasks-app It's meant to work entirely offline and the service
49.
by hasanhaja 2y ago
You can just sprinkle in some <script> tags and not have to rely on UI frameworks. I appreciate that Astro let's you do this rather than invent it's own way of doing things.
50.
by hasanhaja 2y ago
How do you think it compares to Vaadin?
51.
by hasanhaja 2y ago
> That's what I mean - the author gives no prescription. Are you expecting a prescription? If so, what could that look like? Specific technologies? When specific technologies are appropriate? > Most teams do not have the privileg
52.
by hasanhaja 2y ago
Why wouldn't simple HTML be a great starting point for simpler sites? What's it missing that React solves, in your opinion?
53.
by hasanhaja 2y ago
I don't think so. You can still generate a significant amount of your static HTML at build before pushing that to a CDN, and load dynamic content using JS; JAM Stack.
54.
by hasanhaja 2y ago
> though once you master it, it can be pretty efficient. Would it be fair to say in which case that React shouldn't be a tool teams reach for unless they have people who have mastery of it or can pay for it? > user won't be
55.
by hasanhaja 2y ago
https://infrequently.org/2024/11/if-not-react-then-what/#%22...
56.
by hasanhaja 2y ago
> and tech requires Javascript to even barely function: see his entire work on web components. I'm confused by this characterization of web components. While they can minimally work without JS now (i.e., declarative shadow DOM), the
57.
by hasanhaja 2y ago
But most people don't use it for the only thing it does well and pick appropriate approaches for the other parts; they use it for everything and this has transpired into the reinventing of browser mechanisms like CSS in user land. This
58.
by hasanhaja 2y ago
How are you getting to O(n)? Is that in terms of the logic you need to read and keep in your mind? Or is it the actual computational complexity?
59.
by hasanhaja 2y ago
Yes, that's the one! Thank you for linking it.
60.
by hasanhaja 2y ago
Why do you think bad developers or teams without sufficient budget may produce bad experiences when using React? What should those teams be caring about that React doesn't solve for them?

More ›