azangru

22 ms·

331.
by azangru 2y ago
Wouldn't dont be even easier?
332.
by azangru 2y ago
> There was a time when I tried to educate people on the negative effects of browser monoculture. Okay, my mum didn't get it, but I was more disappointed by my fellow devs. Two points. One: dev tools. Chrome's are just so much
333.
by azangru 2y ago
Given the astronomical number of frontend developers currently on the market, I am amazed that you are tasked with frontend work when you explicitly ask not to be. I would have thought it is much harder to find a back-end specialist these d
334.
by azangru 2y ago
> why do we even bother use server side components The naive hope among some web developers is that not everything that we do on the web we do for the sole reason of SEO :-) Sometimes we do things in order to improve end user experience.
335.
by azangru 2y ago
Here's Google search team talking about this in a podcast: https://search-off-the-record.libsyn.com/rendering-javascrip...
336.
by azangru 2y ago
This website uses javascript.
337.
by azangru 2y ago
Yes. Both namespaces and enums (and probably the "private" keyword on class methods) are an early addition to the language, which would have never been added if typescript from the very start aligned closely with Ecmascript.
338.
by azangru 2y ago
There are union types for strings; and there are plain javascript objects (typed as const) if "namespace.name" syntax is desired. With these available, what is the point of enums?
339.
by azangru 2y ago
> Maybe I am missing that or something else, but here I read that "Today most applications can send hundreds of requests for a single page" I liked the following line better: "The main reason a page may contain so many req
340.
by azangru 2y ago
If people want to run Next.js for some reason, especially with react server components, then there is plenty of complexity that Vercel handles. For example, the version mismatch between the long-living client in the user's browser, and
341.
by azangru 2y ago
> but all your engineers hate it. What is it about Jira that you think engineers hate? I personally don't like how a ticket can only be associated with ("assigned to") one person; and how clumsy it is to split a ticket int
342.
by azangru 2y ago
> Scrum tried to fix this in 2011 when “Commitment” was changed to “Forecast” I've checked scrum guides released in 2010 and in 2011. The word "commitment" does not appear in the pre-2011 version. And, as far as I remember
343.
by azangru 2y ago
> Twenty years later, 2026 will be the year of semantic CSS Alas, people are too deep in tailwind for that :-(
344.
by azangru 2y ago
> If nobody "does it right", maybe right is just wrong? It is certainly possible. However, what I have seen in the industry is that there are very few real CSS experts among people who are "busy working on actual software&
345.
by azangru 2y ago
> I'd say that perhaps Git is unsuitable above certain thresholds on numbers of files Scott Chacon in a recent talk about git[0] said that Microsoft uses git to version control Windows. They have ~3.5 million files in the repo, whic
346.
by azangru 2y ago
> Soon after, you're going to need slightly adjust that button The proper thing to do, in my mind, is to gradually set up a collection of such buttons (and other components), and document their properties. A design system, if you wi
347.
by azangru 2y ago
> I really was hoping that tailwind was a fad which died but like everything JavaScript it's here to stay sadly I feel with Tailwind it's worse somehow. At least heavy javascript frameworks are commonly ridiculed by back-end or
348.
by azangru 2y ago
> FWIW for a Button, your engineer should just encapsulate all the “ridiculous” styling into a <Button /> element. Sure thing. What I don't understand though is why not put a Button.css file next to the Button element fil
349.
by azangru 2y ago
> Is React irrelevant? Stack Overflow’s 2023 developer survey places it first overall for web technologies Consider jQuery. It was extremely popular once; was super influential to the point that some of its apis were adopted by the brows
350.
by azangru 2y ago
Same would be true for: - Preact (like react, but tiny) - Solid (like react, but tiny and without the stupid re-rendering, or the stupid rules of hooks) - Lit (like react; but tiny, based on the browser-native web components, and with a cla
351.
by azangru 2y ago
So true! I spend so much time obsessing over how what I am about to write ties in with what has already been written; or fuming over the stupidity of earlier decisions (usually made by myself). A blank slate is incredibly refreshing.
352.
by azangru 2y ago
Even as a suggestion that this is hardly pushed as a Chrome feature?
353.
by azangru 2y ago
> was pushed as a chrome feature Or has it perhaps been accepted as a specification, but Blink-based browsers implemented it first? https://www.w3.org/TR/css-anchor-position-1
354.
by azangru 2y ago
I am not seeing it used much in print though.
355.
by azangru 2y ago
Jamboard was never an infinite canvas. It was a very awkward thing that didn't allow you to select multiple items at once (or if it did, I never discovered how), or to expand the canvas to accommodate more content.
356.
by azangru 2y ago
A caption to a figure in the article reads "Georgi Molotov ... 'the great survivor', was one of Stalin's key enforcers for decades". Wasn't Molotov's name Vyacheslav? [0] [0] - https://en.wikipe
357.
by azangru 2y ago
A lib was heavily relying on React internals for testing, rather than just on components' public api. That this approach was going to be unsustainable was already obvious around 2020. The question is, after you've invested a lot o
358.
by azangru 2y ago
We did this for our codebase (several hundred tests) manually, two or three years ago (the problems were already apparent with React 17). It helped that we never used Enzyme's shallow renderer, because that type of testing was already
359.
by azangru 2y ago
I thought these two short video demos by Ryan Florence of how this problem is mitigated in the upcoming react router 7 would be relevant for this topic. - https://x.com/ryanflorence/status/1801383836250739057 - h
360.
by azangru 2y ago
> as compared to the total uncomposability of class components How do you mean? React components were composable from the get-go; this is practically the definition of a component: you take a piece of ui, you encapsulate it in a componen

More ›