Yes, the EU did escalate things to such an extent that absolutely countries should be considering leaving over the EU’s insane push to destroy all privacy and thus free speech.
I didn't think this was even possible. Can EU laws actually override the constitutional rights of member states? I was under the impression that the principle of supremacy isn't absolute and doesn't extend to overriding a country's fundamental constitutional rights. If that's not the case, the danger isn't limited to just Germany. With authoritarian regimes gaining power everywhere, it would only take a few of them working together to pass an EU law that makes everything fair game.
> Can EU laws actually override the constitutional rights of member states?
Sometimes yes.
> I was under the impression that the principle of supremacy isn't absolute and doesn't extend to overriding a country's fundamental constitutional rights.
What are a country's fundamental constitutional rights can be "dynamically adjusted" depending on the political wishes. :-(
> With authoritarian regimes gaining power everywhere, it would only take a few of them working together to pass an EU law that makes everything fair game.
There is a reason why more and more EU-skeptical movements gain traction in various EU countries.
Specifically for Ireland, we are the only EU member state where the Constitution ordains a referendum to validate ratification of any amendments that result in a transfer of sovereignty to the European Union; such as the Nice Treaty which we can prevent from passing on an EU level. Ratification of other Treaties without the sovereignty component is decided upon by the states' national parliaments in all other member states.
Ireland, Netherlands, and Luxembourg also have veto powers when it comes to EU wide regulations. That's why Article 116 exists.
In the particular, the Seville Declaration recognised the right of Ireland (and all other member states) to decide in accordance with National Constitutions and laws whether and how to participate in any activities under the European Security and Defence Policy.
No. The EU isn't a federation, there's no supremacy class. The member countries are sovereign and obviously can't go against their constitutions or basic laws.
> The member countries are sovereign and obviously can't go against their constitutions or basic laws
False.
> The principle was derived from an interpretation of the European Court of Justice, which ruled that European law has priority over any contravening national law, including the constitution of a member state itself.
That is sort of like a supremacy clause, and of course it's valid for the EU.
But that doesn't mean that a Swedish or German etc. court can let that override our basic law. Our basic law is after all the foundation of our law, so if something conflicts with that, it obviously can't be valid.
Privacy of communications is usually a normal law not constitutional principle, so slots perfectly fine without any supremacy issues between constitution and EU law.
Nitpick: React compiler is not a transpiler. JSX needs to be transpiled, and that's usually done by TS compiler. React compiler is another optional thing on top that's relatively very recent.
All compilers translate one language to another language. Historically compilers targeted lower-abstraction languages than the source language. "Transpiler" is a compiler whose input and output abstraction levels are similar.
The React cinematic universe has a habit of repurposing existing terminology, but they're both transpilers, to the extent that "transpiler" is even a word.
You are absolutely right! (Here I'm roleplaying an AI chat bot which caught red handed hallucinating).
It appears that I was wrong about the definition of transpilation. It's a specific term for a compiler that compiles from a high-level language to another high-level language, even when those languages are the same with no DSL and even when the logic is optimized.
In JS land, transpile was used to distinguish something like elm->JS from ES6->ES3. One was the same language with different versions and the other was different source languages.
Yes, all transpilers are compilers, but not all compilers are transpilers.
I really don't understand this colored functions debate. Async functions are just functions that return Promise<T> instead of T. You can use them in a non-async function but you must then switch to callbacks, because you hold a promise. I don't get how this is confusing, unless you define the whole concept of concurrency in a single thread that runs your UI as well confusing.
Hooks are functions that need to be called before early returning, in a function that provides a context for them. They are also just Javascript, they can be implemented with no build tools.
It's not confusing. It's an observation on their nature. The colouring isn't specific to promises, or even async/await. It applies to continuation style callbacks too.
I read the original article and many surrounding discussions & follow-up articles. Not confusion perhaps, but many see it as friction, including the complaints from the original article. From where I'm looking at, it's just a side effect of dealing with concurrency with no threads, what the article also mentions. So, you know, it is what it is, at the end? Now we have people coming up with different definitions of color (react hooks, in your case) and complaining that it's bad?
This is like when you are doing embedded programming, holding the API functions you need to call in a special sequence to the same standard as people writing their own DSLs with templates.
I'm not complaining it's bad per se. As I said, it's an observation on their nature.
I would not say it's a different definition of colour. I am somewhat contorting the original definition in the article, but if you compare characteristics listed, many/most of them apply to hooks also
The complaint is that it's not just "function composition" (per GP) at all anymore. You're dealing with "component lifecycles". Composition doesn't really work out with hooks, for reference see any non-toy React codebase.
It's like dealing with event handler registrations. You cannot compose those too, as they are "hooks" for when a specific event occurs.
Hook definitions can be a composition of reusable functions and other hooks, like any event handlers (e => filterKeys('cmd+s, ctrl+s', preventDefault(e)).then(save)). It's possible to break this anology (you can register an event handler in an if branch) but I hope it gets the point across.
> It's like dealing with event handler registrations. You cannot compose those too, as they are "hooks" for when a specific event occurs.
Yes, and those are frequently annoying also. Literally the point of the article is the friction they introduce and questioning whether there are better ways to do things. Sometimes there are.
The whole reason that hooks were created was that they could composed, as opposed to stuff like renderprops or mixins. When you create a custom hook that uses a useState and a useEffect, that's composition. They have the caveat that they can only be composed into new hooks, but that's just like async functions only being able to be called from other async functions.
Javascript has warts, React has warts, Svelte has warts, Python has warts... It's easy to shoot yourself in the foot in any tech - it's leaky abstractions all the way down after all.
useEffect usage needs to die, yes. I don't think it's a case against React, given its age.
Otherwise, using React is straightforward. I started coding in it without reading any docs. As someone who used Dojo, prototype, ext.js, jQuery (+UI), Backbone.js, knockout (still has a special place), Mithril, the classic angular, vue (2), svelte, Marko and even Solid (I'm not totally sold on signals), React is the most straightforward by a mile.
Is it the most performant? Hell no. Is it the one with the least gotchas/warts? Nope. Concise? A giant no. Batteries included? It depends on what you're looking for...
But I can just be productive with it, and it makes sense.
Bro lists like 8 different moms whose food he has, then says he likes react-moms food, and you make it sound like that's the only thing he's ever had. Did you even read the comment you replied to?
It's impossible to provide enough context for translation strings. You need links to mockups, designs, or any other visual aid so that translators don't make huge mistakes. Even then, they'll eventually find that the programmatic parameters are insufficient for returning the correct translation, and they'll have to duplicate strings because the same sentence has different translations in different contexts. It's a never-ending job.
Turkish is especially funny here, but not even close to how creative you might need to get for some other Asian as well as Slavic languages.
Lucky that you never had to translate Ekşi Sözlük, how do you even translate "şükela" :)
Russian having singular, few (2-4), and plural (5+) forms is one from the top of my head. I can't remember any specific examples from non-cryllic ones but remember we having to duplicate a lot of translation keys to make them more context specific.
Not the parent commenter, but -- days of week in Polish are a nice example, IMO.
`Środa` means `Wednesday`, but depending on the grammatical case it's going to be translated either to `środa` or `środę` (or five more, but somewhat less likely to appear in UI [1]).
- Next <Wednesday> is 2018-01-03. = Najbliższa <środa> przypada na 2018-01-03.
- This event happens on <Wednesday>. = To zdarzenie ma miejsce w <środę>.
If you mix the variants, it's going to sound very off (but it will be understandable, so there's that).
What's more, days of week have different genders, which affects qualifiers:
- <this> Wednesday = <ta> środa (Wednesday is a "she")
- <this> Monday = <ten> poniedziałek (Monday is a "he")
... together with the grammatical cases affecting the qualifiers:
- <This> Wednesday is crazy. = <Ta> środa jest szalona.
- <This> Thursday is crazy. = <Ten> czwartek jest szalony.
I once worked with translating an application to polish, and found out we had to have separate placeholders for "name" for persons (nazwisko) and for things (nazwa).
Which is a simple example why you need context.
All UI frameworks should have a "translate" mode, where all labels and static text can be right-clicked and modified...
> Some times boring, done consistently, is where the truly great things come from.
I used to tell myself the same thing. Then one day, a customer misconfigured their NetScaler, and all hell broke loose. We had half-delivered CSS files, misfiring form handlers, random blank screens of death, and a buggy front-end library that would bombard the backend with requests if it received the wrong status code with no back-off logic! There were hundreds of bug reports. You name it, we had it.
Debugging everything was just wild, especially with the constant tension of "What if it's our fault?" In the end, it wasn't! We got paid for our time, and we were able to close a massive number of tickets. It was one of the best weeks of my professional life.
There's a huge difference though between short bursts of intense activity – which are thrilling, and in my experience can forge longlasting team bonds – and an ongoing, constant sense of pressure. The latter you can't maintain excitement about indefinitely, and inevitably the continual stress just leads to burnout. Or apathy: after all, if everything's urgent then nothing feels urgent or special after a while.
i too strive in such a situation, but it still makes a difference whether the work is meaningful or not. especially when you get to sleepless nights. it makes difference if that customer is a hospital or some other meaningful industry, or it is something meaningless like an online game, other entertainment or worse, gambling. i wouldn't work overtime for the latter (unless the pay is worth it or the team is good)
i can definitely confirm that meaningless work is more boring.
So it is essentially all about money, and meaningfulness of the job is just another bonus, along with medical insurance, prolonged vacation period and anything else that might make you choose less paying job.
That said, I can imagine people taking pride and joy in building an online game and making sure it works reliable even as audience grows way past anticipated level.
I use repomix to pack a full repository as an xml file and it works wonders. System prompt is very simple:
please don't add any comments in the code unless explicitly asked to, including the ones that state what you changed. do not modify/remove any existing comments as long as they are valid.
also output the full files that are changed (not the untouched ones), and no placeholders like "no change here" etc. do not output the xml parts in the output.xml file. focus on the individual files.
before and after outputting code, write which file it would be and the path (not as a comment in the code but instead, before and after outputting code).
Attached is a 400k token xml file, being the output of:
