We use OPA for use cases ranging from kubernetes admission control, to microservice authorization and CI/CD pipeline policies. It's one of those tools you can't realize you could have lived without once you start using it.
From a Nordic country myself and have never experienced that effect, nor heard of anyone who would eat it for that. We just like it for the taste. Getting a little more cautious from reading all the comments here though!
So instead of we’ve got rampant racism, conspiracy theories, fake news and attempts to sway elections in that direction all over the world. If that’s the good experience, bring back the midis!
Pretty much any language running on the JVM will make it dead simple to import and use libraries written in Java - in fact one of the main reasons to choose the JVM is the huge amount of high quality libraries available. So while true that Java != JVM, it’s not as simple as that either.
From my friends in Poland I hear many of them are considering moving after the latest election and the direction the country seems to be heading. Good to know there are tech workers from Belarus to step into their positions.
Swede here. Like you say our isolation is pretty much volountary, with only larger groups gathering being banned - though I very much doubt that would happen anyway should it be allowed. Our neighboring countries who opted for total lockdown are slowly starting to open up too. I think the death toll in pretty much any country will be primarily depending on how well you’ve protected your elderly. We’ve done OK but could certainly have done better. Though still very far from the “devastatingly wrong” claim above.
> Releasing a product before it is done is can of worms in itself
Perhaps, but a programming language which is released when “done” is essentially dead on arrival. I’d guess the people who created amazing things with Odin helped the language move forward, right? Nothing wrong with keeping something to oneself, but promising for a long time to move something into an open source model with no set date.. I’ve rarely seen that end well. Hope I’m proved wrong though!
This implies that time not spent using their software is time wasted doing nothing. Not that reducing boot times would be a bad thing, but that sounds more like a marketing gimmick. As kids we would wait for forever for our Commodore 64 games to load - knowing this we planned accordingly.
So, no choice of language and no choice of the libraries used. What’s “everything else” exactly? Sounds like missing out on the more interesting parts of a micro service architecture.
Network latencies and round trips will almost certainly be the primary source of performance issues in any larger microservice environment. If you don’t need that level of scale, that’s great. But once you do, JWTs are perfect for carrying information across the network that may be verified without extra network calls involved.
JWTs and sessions are not in any way orthogonal in a system as a whole. We use JWTs primarily for scalable backends - if a session is setup or not in the front end is not a concern for the API backend services. In a microservice environment there could be many of these - that’s the whole point after all. And with JWTs being sent to these they can simply verify the integrity of the caller without asking a central authority. Coupled with OAuth2 and OIDC as protocols for delegation/federation and you have a system that scales extremely well. Of course, it might not be the first concern that needs to be addressed in a small startup but that doesn’t mean it doesn’t have a place.
Huh? GitHub’s company culture has been described as toxic way before they were acquired - not at least here. The problem seems to be exactly that they’ve managed to preserve that. Kudos to the employees speaking up though!
That’s a point, and I agile development would not be possible without the internet. But working incrementally based off of customer/user input is only possible after the first release. What was observed here was the huge number of projects that would previously fail without ever getting that point.
The difference is that of ivory tower planning and the following phases of development, testing and a “big bang” release (waterfall) vs working with an MVP with the purpose of releasing as soon as possible and then work in iterations based off of actual feedback and demand (agile). If you manage to nuke your budget or create a monster of a code base already at the MVP stage no methodology is going to save you.
But this is not an issue of Apple vs. OpenID Connect, but one between Apple’s flawed implementation of the OpenID Connect standard vs. the actual OpenID Connect standard. If they would have just gone with some proprietary implementation I very much doubt the OIDC people would have bothered. That happens pretty much daily after all.
The UI was what kept us from Zulip last time we evaluated chat at my employer. When maximizing the window not even half of it was covered by the actual chat but by meaningless white space on both sides. We could not figure out how to change this either. Is this addressed with the new release?
Definitely agree on how annoying that is, but as far as I know no one has really pulled off client side rendering in any way looking even close to equal on all browsers and platforms. I know I spent years on another project trying to do just that before resigning to render the final result (PDF in this case) server side - so at least _that_ was consistent, albeit unfortunately not with the expectations one has from having seen the client side rendering before.
The actor most likely to make mistakes is the one reporting the numbers in the first place, i.e. the employer. And yes they would be held accountable for that just as the government, could you show that the numbers your employer reported is not what shows up on your tax report. This is how it’s like in many European countries and it pretty much just works.
There’s a whole class of actions and values that you can’t parameterize, like anything resembling DDL queries. I have worked on several products where these types of queries (like creating tables dynamically) have been an absolute requirement. Sanitizing input is still very much a necessity there.
My personal favorite - the inability to store an empty string, instead converting it to NULL leading to null-checks in code even though the value is known to be non-null when inserted.
If your interest in my well being does not include listening to me talking about my illness for the next twenty minutes, your interest is feigned. This is what it’s all about in countries that don’t bother much with small talk, and your example with asking about someone owning a pen (while interesting in other aspects) isn’t really a serviceable metaphor to that.