Your numbers for France don't match anything I can find online.
The number of immigrants per year seems to have been max 340k, about 50% have employment quickly, etc.
You complain about "leftists" but as someone who definitely doesn't want open borders, the general fear in your comment and the numbers that seem made up make your comment read a lot more like (far-) "rightist" stuff.
I can't comment on that specifically, but it works with MVVM extensions toolkit, which is handy for decoupling of event handling and is helpful in complex scenario's.
Most import thing to look for are the components you need imho. You can build themselves, but if you can use something ready made, that helps of course. You would best take look at their gallery to see if you see something similar for your needs.
Edit: I've googled it and I can't find anything relevant. I've been working in software for 20+ years and read a myriad things and it's the first time I hear about it...
"Shift-left" was a general term that occurred in the systems engineering / devops space – I'm not surprised to see it used in a security context now. More or less, about a decade ago most systems engineers were recruited into the industry without any application software engineering skills and that became a drag on organizations trying to scale. It was about moving testing, devops, security, etc into the software engineering role and attempting to consolidate systems engineering into SWE roles. It was a part of the larger "devops movement".
I've been writing my own linter that's supposed to check projects regardless of the technology (e.g. something that focuses on architecture and conventions, alongside something like Oxlint/Oxfmt and Ruff and so on), with Go and goja: https://github.com/dop251/goja
Basically just a bunch of .js rules that are executed like:
projectlint run --rules-at ./projectlint-rules ./src
Which in practice works really well and can be in the loop during AI coding. For example, I can disallow stuff like eslint-disable for entire files and demand a reason comment to be added when disabling individual lines (that can then be critiqued in review afterwards), with even the error messages giving clear guidelines on what to do:
var WHAT_TO_DO = "If you absolutely need to disable an ESLint rule, you must follow the EXACT format:\n\n" +
"// prebuild-ignore-disallow-eslint-disable reason for disabling the rule below: [Your detailed justification here, at least 32 characters]\n" +
"// eslint-disable-next-line specific-rule-name\n\n" +
"Requirements:\n" +
"- Must be at least 32 characters long, to enforce someone doesn't leave just a ticket number\n" +
"- Must specify which rule(s) are being disabled (no blanket disables for ALL rules)\n" +
"- File-wide eslint-disable is not allowed\n\n" +
"This is done for long term maintainability of the codebase and to ensure conscious decisions about rule violations.";
The downside is that such an approach does mean that your rules files will need to try to parse what's in the code based on whatever lines of text there are (hasn't been a blocker yet), but the upside is that with slightly different rules I can support Java, .NET, Python, or anything else (and it's very easy to check when a rule works).
And since the rules are there to prevent AI (or me) from doing stupid shit, they don't have to be super complex or perfect either, just usable for me. Furthermore, since it's Go, the executable ends up being a 10 MB tool I can put in CI container images, or on my local machine, and for example add pre-run checks for my app, so that when I try to launch it in a JetBrains IDE, it can also check for example whether my application configuration is actually correct for development.
Currently I have plenty in regards to disabling code checks, that reusable components should show up in a showcase page in the app, checking specific configuration for the back end for specific Git branches, how to use Pinia stores on the front end, that an API abstraction must be used instead of direct Axios or fetch, how Celery tasks must be handled, how the code has to be documented (and what code needs comments, what format) and so on.
Obviously the codebase is more or less slop so I don't have anything publish worthy atm, but anyone can make something like that in a weekend, to supplement already existing language-specific linters. Tbh ECMAScript is probably not the best choice, but hey, it's just code with some imports like:
// Standalone eslint-disable-next-line without prebuild-ignore
if (trimmed.indexOf("// eslint-disable-next-line") === 0) {
projectlint.error(file, "eslint-disable-next-line must be preceded by: " + IGNORE_MARKER, {
line: lineNum,
whatToDo: WHAT_TO_DO
});
continue;
}
Can personally recommend the general approach, maybe someone could even turn it into real software (not just slop for personal use that I have), maybe with a more sane scripting language for writing those rules.
Office was considered a very solid product for many generations. Windows 95 was loved. So were Windows 2000, Windows XP with the SPs, Windows 7, Windows 10.
.NET was the envy of the Java world for many years.
Microsoft had many duds but they also had some great products.
You can't sell as many products as they did without also having some good products.
> Office was considered a very solid product for many generations.
When was that? My introduction to Excel was in the 1990s when a scientist asked about data corruption, and my response was "oh, yeah, Excel does that, you need to fiddle with these options and hope the options do not get turned off, seeing as companies may randomly screw over user preferences". The look in their eyes...they probably had done a whole bunch of data entry before they even noticed the corruption. Anyways, a few decades later those genomes got renamed, for some reason or another. Other customers came to me and pleaded, please do not install Word 6, it's bad, and I was like, well, be that as it may, but Microsoft has broken the file format, again, so if someone sends you a Word 6 document you will not be able to read it. They've got you over the barrel, perhaps consider not using their software? Unless you like being chained to that main-mast, of course, don't shame the kink! Later on a coworker said, try Visio, and I was like, this is sort of bad, and they were like, yeah, it was better before Microsoft bought it. So, when was Microsoft not producing kusogeware? Sometime during the semi-mythical 80s, perhaps?
Imagine creating a brand that became renowned world wide and even created its own verb.
And then throwing all that away for the genius brand name of... "x". Brought to you from the same 50 year old that decided that having car models that spell S3XY is cool.
Nothing has been thrown away, evident by billions of dollars in the continued success of many flagship products that leave the competition in the dust.
"You can always count on Americans to do the right thing—after they have exhausted all other possibilities."
As an outsider and on a more serious note, there's just too much money in cars and car-centric infrastructure. The whole country would need to be rebuilt.
It can be done, they've rebuilt the country a few times, but again, as a outsider, it feels like hope has been dying out in the US. They're giving up because they've given up.
> My plot increased 3 times in price in 10 years. Try to beat that with SP500. It’s virtually immune to inflation no matter how the broader economy fares it will always shield from inflation because you cannot make more land hah.
The number of immigrants per year seems to have been max 340k, about 50% have employment quickly, etc.
You complain about "leftists" but as someone who definitely doesn't want open borders, the general fear in your comment and the numbers that seem made up make your comment read a lot more like (far-) "rightist" stuff.
reply