Indeed. Catalan speakers have Spanish forced down their throat no matter if Spanish has never been associated to the Google account in any way, nor in the system or browser language preferences.
In my case, I live in the United States, but Google is determined to serve me Spanish results even for Catalan-related queries. E.g. preferring the Spanish Wikipedia. The search engine's behavior has had ups and downs over the years, but it has never been great.
This is very much a problem for my children, who don't understand Spanish, as well as for the Catalan-speaking regions of the world that are not in Spain, including Andorra.
In my experience, Gemini easily flags any Catalan content as unsafe and prevents the conversation from continuing. Even for prompts like "summarize this article". This may have improved lately, but still.
Google used to be an example in sensitivity to the world's diversity, being a responsible major player. Way back. Now, although I applaud some efforts multiple teams continue making, it is obvious this is no longer a priority.
Arrreg!! So many of these React (et al) sites, with poorly re-built elements and break the built-in functionality! The A tag works perfect! But no, we need three or four nested divs, components, and many lines of JS to end up with something worse.
Is React the driver? Do devs just not know? Is management pushing garbage?
With every client-side routing framework or library I know of, the trivial happy path will involve using their provided link component which performs client-side navigations on click but also renders an underlying anchor tag with href (and works with cmd-click, middle-click etc.).
You really have to go out of your way to break this, and I don't think client-side routers deserve any blame for this. Anyone who is ignorant or careless enough to ship broken links using a client-side router would be just as likely to break anchor tags with their own hand-rolled JavaScript.
> Is React the driver? Do devs just not know? Is management pushing garbage?
I'd say developers who aren't web developers trying to do web dev seems to be the cause of this. Understanding the platform you're developing for is pretty much table stakes for any developer, and not understanding when to use <a> is pretty much the most basic mistake you can make. Literally the first things you learn in web development is about linking to other pages, yet somehow still people fuck up putting a <a> into a webpage properly. Boggles my mind.
React makes it as easy as any other library/framework, but if you don't think about what ends up in the DOM, and why certain things have to be a specific way (often for accessibility and user experience), then you'll screw up even big and expensive projects like this apparently. 2x boggling since this project is literally all about user experience yet they get the most fundamental part of the web wrong.
> I'd say developers who aren't web developers trying to do web dev seems to be the cause of this.
Hard disagree. I've seen a ton of decent web developers (i.e. people who can use modern CSS, layouts, and modern web stacks) reinventing buttons and links and forgetting about accessibility.
It's a completely orthogonal thing to the dev background.
> people who can use modern CSS, layouts, and modern web stacks) reinventing buttons and links
Yes, these are exactly the people I'm talking about :) You and me just differ in that I won't call them "decent" if they don't understand linking properly.
I'll generally excuse things like laziness and incompetence, because I understand that not everyone is good at their jobs.
But this:
> You have to do extra work to fuck it up!
resonates so hard. I get so angry at people who take extra time out of their day to put so much effort into making things worse. So many things on the internet are fine, but people spend so much on making them worse. Who is this good for? Not me, and likely not the person who wasted their time ruining functional things.
And since React doesn’t have built-in support for pushState (Yes I know React Router, but it really wants a hash router), you really need extra work for an internal router. And therefore, every beginner dev does it manually and slightly inconsistently.
So yes, React is absolutely the driver, same as Java is guilty for Guava existing, because it should have been built-in and perfect.
> Yes I know React Router, but it really wants a hash router
This doesn't sound right. The history API has been widely supported by all major browsers (including mobile) since 2013. React was also first released in 2013. Did React Router ever ship a version without a HistoryRouter.
I have been programming in React for 3 years and never heard of HistoryRouter.
You would be plentiful right to say it’s a programmer’s skills issue. But you have a very stinky pattern of masses of problems of programmers skills issue, leading to 90% React apps breaking the history.
In this case we are not talking about beginner devs (to their credit, the React docs are pushing people toward frameworks now) — these are literally the developers of a framework, fucking it up in their own docs!
One of my pet peeves is people blaming things on React that have nothing to do with React. I see this quite frequently on Hacker News. Using an a tag or not has nothing to do with React.
Remembering bugs is not necessarily and indicator for passion. I know I love what I do, and have since I was really young, but I do not keep track of bugs or even feats—they just become a rolling base of knowledge (experience). At least in my case, it is just how my brain works.
This is so different from what comes to mind when I think about how to improve productivity:
- require engineers to present and justify engineering investments (and understand that what you don't accept has real costs)
- have engineers estimate the work in the roadmap, and provide clear risks and possible mitigations
- note all of the above means the goals are clearly defined first
- not everything you wanted to accomplish may fit; be prepared to distinguish essential from good to have, and to change the order of your priorities.
- have teams commit to dates based on estimates, a healthy error margin, additional responsibilities, meetings...
- plans change, things happen, life happens, engineering is hard. It's OK, it's expected! Make sure there are clear communication channels from engineers to the top, and from the top to the engineers, so that expectations are adjusted as soon as possible, and maybe make further adjustments.
- Communication should happen often. Be always available to listen, don't micromanage.
- managers should protect engineers and said communication channels
- managers and PMs do not set deadlines
- don't hire cheap; hire motivated team players.
- the primary role of your >Senior engineers is to be force multipliers (how is a whole different conversation), not to do superhero work
- communication, communication, communication; you'd be shocked how much time is wasted by engineers being unsure how to proceed and not sure who to ask of if the question will be well received; there are no bad questions.
I feel like I could go on and on and expand on many of these.
Yes: multitasking hurts; yes, procrastination is bad; but beyond looking at each "issue" individually, engineering leadership should provide processes and culture that protect, motivate and facilitate success.
I agree. Our kids are very much ahead, in part because when we travel, they learn a lot. They seen new places, new ways of doing things, learn history, apply their math and other acquired knowledge, they often learn things ahead of time just because they interact with other adults, they get to use free time to apply their knowledge and interests creatively. And with the right timing, they get to see their relatives far away without it draining our savings, which makes them happy, which is not only important, but makes them better students as well.
> Or maybe do start saving, so your ancestors can take advantage of compound interest to buy a ticket in a few millenia
My apologies if this is off-topic, but I have recently read and heard a couple cases of "ancestors" being used instead of "descendants", which has sparked my curiosity. Is this a common brain-lapse result?
I've found that keeping a changelog as part of my design docs and similar is a good way to keep engineers, even across teams, confident that what they are looking at is up to date and a good reference, and the right document to update if necessary.
And the browser takes care of the rendering.
Good times.