eslint is a good example of why coding in javascript is annoying. Your tools just constantly changing wildly over a version upgrade, so you look for a better one and find there's a new Rust linting tool but it's alpha and is missing half the features.
eslint is also a good example why Javascript runtime is bad choice for static analysis tools. The biggest problem is that it's single threaded.
Recent release of concurrency mode in eslint promised approximately 30% linting speed increase.
So now it uses multiple threads instead of one, and you got only 1.3x improvement. In any compiled language like Rust or Go you should expect time improvement that correlates with number of CPU cores engaged.
You can use worker threads in JS, but unfortunately sharing data between threads in context of static analysis, where there is a lot of deeply nested objects (AST) or basically a lot of data in general, is slow because it needs to be serialised and deserialised when it's passed between threads.
Javascript based tools for codebases with 1m+ lines of code becomes unusable :/
LLMs are going to keep React alive for the indefinite future.
Especially with all the no-code app building tools like Lovable which deal with potential security issues of an LLM running wild on a server, by only allowing it to build client-side React+Vite app using Supabase JWT.
In Canada all the police cars seem to have automated license plate readers these days.
This article explains there was a 2016 law where California won't share local police plate reader data with the feds, so they made a deal in 2024 where Caltrans (dept of transportation) will let Border Patrol pay for it themselves on roads near border crossing like San Diego County.
You can just look at examples in the article. For example "Lithium-Ion Cell Manufacturing"
> Cell manufacturing uses NMP solvent for electrode coating, handles flammable electrolytes, and requires formation cycling that generates heat and gases. Tesla chose Reno for the Gigafactory specifically because of California's permitting environment.
EPA tried to heavily restrict these outright in 2024 [1] and California has air/environmental rules that made it nearly impossible to develop large battery factories in California, which is why Tesla chose Reno in 2014. An alternative didn't exist at the time and now a decade later Tesla recently filed a patent this year for Dry electrode processing [2]
So basically California lost a decade of possible lithium factories
Given the labor challenges in California due to high housing costs, which selectively pushes out those willing to work for lower wages, I am always surprised when manufacturers choose the state at all. Throwing additional challenges doesn't make it any easier.
It helps you can buy an electric car in China for 1/4th the price as California. They also massively invested in every sort of energy (not just solar) where it's cheap and affordable to develop industry. Everyone obsesses about labour costs but almost everything is easier and cheaper to build in China because they allow stuff to be built there. Including the workers far lower housing, utilities, fuel, and food prices which lower the cost of living.
I read an article that dug into public GDPR cases, which is a surprisingly small set, and it explained they have had a near zero impact on the massive advertising and data broker industry. They mostly just have a large back log of legal cases against large US companies like Google which occasionally result in fines - but even that moves very very slowly and has little impact on their global business models. They do also occasionally charged a few smaller European companies a few grand for violations.
The key thing is that companies like Google and Meta run giant ad networks, there's many thousands of companies buying ads then collecting data in their own systems and reselling it.
The privacy issues of data retention on Google/Meta/etc social and SaaS platforms is something to care about but it is only a small piece of the puzzle of data privacy.
Ads will remain a major business for the foreseeable future as nobody is going to pay $5/m to use Instagram with no data collection.
I’ve read the GDPR has zero impacts on national security/law enforcement. It applies weakly to other state functions.
I’ve also seen cases where GDPR is used against religious groups that have a strong religious justification for keeping lists of believers. Think Orthodox Jews and the Catholic Church, which regard family trees and baptismal certificates as semi-sacred. And kept on paper or scrolls.
Not sure what to think about that. Regulating a sacred scroll like a database table seems wrong.
The reason why we're not keeping lists of which people believe what religion, is because such lists were extremely useful to the nazis in WW2 when exterminating Jewish people.
> Think Orthodox Jews
Pretty sure they would remember why this is the case.
> Regulating a sacred scroll like a database table seems wrong.
There is actually no perceivable or material difference between something that is considered "sacred" and that which is not. It really hinges on whether some subset of some splinter of some religion considers it so.
But, I'm not familiar with these cases you mention, I think there's some details left out that should matter. The really weird thing to me, is that a sports club can keep a list of members easily (yes they need to abide by the GDPR but it's not hard), and if somehow a "religious group" can't manage that level of organization, I don't think their opinion on what objects are considered "sacred" should count for much, either.
Another issue is that "religious groups" can have a different opinion of who are their members and who they get to keep data on, and it doesn't matter whether those records are "sacred" or not, according to the GDPR it is not the "religious group", but the people whose data is being kept whose opinion counts. It would be ridiculous otherwise. I had to email a Church to stop tracking me (which happens if you're baptized as a baby), and that should be my choice, it would be insane if they could claim "yeah tough luck, but our records are sacred".
> There is actually no perceivable or material difference between something that is considered "sacred" and that which is not. It really hinges on whether some subset of some splinter of some religion considers it so.
What? To many people, the Bible is just a book. To Christians its sacred. This doesn't mean it's immutable (the original Bible wasn't in English after all), it just means it's important to them.
For the records, the records themselves could be sacred, but the practical implications of them are not sacred. But if Catholics have a sacred record of everyone who had been baptized at a church, then that should be different from their mailing list. God did not instruct the chrich to email everyone who was ever baptized there. Plus, at some point in the church's age, there will be more dead people on the list of people who were baptized than alive people. It doesn't make sense to send an email blast to more dead people than alive, so they must trim the mailing list every so often.
reply