Our firefighters collaborate with Croatian aerial firefighters (our neighbouring country). They say there is often pressure from politicians to drop water on wildfires in mined areas, however this is still dangerous to the planes as they have to go real low (a mine could explode spontaneously in their flight path) and after a few near misses they've adopted a policy: if it's not worth demining it's not worth saving from fire either.
He ended up on React because it just works and doesn't change all the time. Now both my React and .NET times are some way behind me, but I'd definitely say it's the other way around..
It's changed a LOT over the years though... it's just kind of glossed over at this point... the move to hooks and quasi-functional components was a massive paradigm shift, but most saw it as a raw improvement. I personally think server components are still a bit of a mess and am actively avoiding them for now... they're improving but I think it's a waste of server resources most of the time.
My dad and my uncle had a code under the Bush administration
My uncle had moved to the US and either still was on a green card or had just recently got his US citizenship and thet said why risk it? .. (they were kinda cute about it though, they just wrote "Jure Grm" which literally translates to "George Bush" in our language so if anyone was actually looking, they wouldn't have fooled them for a second).
They were just bitching about politics, not planning a coup or something, yet they felt insecure, even with the US.
Both ASCIIdoc and reStructured text are older and better (subjective, of course), yet Markdown still won. Happens sometimes, nothing to see, I've moved on (with just a little grumbling). Now I often can't remember their syntaxes anymore, Markdown is everywhere.
The matrix, which you can download, aims to provide an objective comparison. Any idea what features are missing, or can you qualify what makes the other text formats "better"? From my perspective, they are largely equivalent.
For my language I've been using a US layout with a similar alteration for years as well on Windows and Linux: AltGr+C = Č, and AltGr+V = Ć (the second one is much less common, basically only used for writing names). Similar for Š, Ž and Đ, I stopped bothering with stuff like á because I need them maybe once every couple of years.
My point being: wow, I've never thought about standardizing the layout, what a marvelous thought. Not for the general public perhaps, but for some programmers it would be a godsend. The whole terminal is basically non-ergonomic on other layouts. Stuff like ./ is right together on the US layout. Similar for coding. I preach to my fellow developers and they see my point but most won't go outside of what's provided by the OS for some reason.
I don't know enough about other European languages from my "region" to make a more general standard (though I suspect it wouldn't be as simple as creating a single "eastern" one, I doubt e.g. Hungarian and Polish have so much in common) but it's a good idea, something that could be collaborated on.
Well, no. I mean something I can stick in my actual code to ensure it matches the spec, be it through validation, strongly typed interfaces, unit tests or some other mechanism.
Also, while a nice API document is a godsend (and sadly often missing in practice), a way to generate the consuming side of the API (again via various mechanisms) is also a very useful thing.
Re-reading the page, perhaps I got it wrong and it works the other way around? Voiden uses e.g. OpenAPI files and verifies it's still compliant with them? That would work, although it's a bit of a double effort.. still, useful in many cases.
That is unfortunate, EU could well present itself as an example of how things can be done right. Unfortunately incompetence and/or indifference, plus lack of IT talent willing to work for the public sector is also a thing in politics. It's an opportunity lost for sure.
Functional cookies are fine. Even analytics is fine if you're using your own (though said own analytics must also company with GDPR personal data retention rules).
What is not fine is giving away your users' personal data to pay for your analytics bill.
That's not true. You can use those cookies, you just need to explain them somewhere on the site. No opt in required.
I talked with our then national information law official (funny fact, same person is currently president of our country), rule of thumb is if you're not using your users' personal data to pay for other people's services (e.g Google analytics) or putting actual personal data in them, you're generally fine without the banner.
Further, if you're a small shop or individual acting in good faith and somehow still violated the law, they will issue a warning first so you can fix the issue. Only the blatant violations by people who should've known better will get a fine instantly (that is the practice here, anyway, I assumed that was the agreement between EU information officers)
Guess they will have more work now
reply