The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Why Wales? I mean, as described by those without and within, it's not a proper place by any standards. Especially, watching Hinterland (Y Gwyll) I get to see the scenery and why it's not a tourist mecca. Fortunately, I'm prone to epiphanies.
The place was built and maintained as a safe and out-of-the-way place to store the Welsh.
Never mind — I got the fix, and understood the definition as I knew of it was correct. Good night!
I know either because of the fact that I am sleepy at the moment, or I am not a native English speaker, I am unable to understand the meaning of swap. (I did try Google.)
I am actually working on Azure App Services, I also happen to have an event on 14th January about ASP.NET Core deployment on Azure App Services. One thing that I came across was Deployment Slots. Concept seems to be really easy, you create an extra application — similar to your actual one, same environment, same everything, just not public — and then you swap it once you are happy with the recent deployment.
Until now I was "believing", by this swap functionality, Azure will actually move A → B and at the same time would make A ← B so that they are interchanged. After so much time, I came to know that it was merely a copy of B to A (A is the production environment). Meaning, data of B was copied to A and data of A (previous build) was lost. No backup.
Which makes me think, where does that roll back sh*t comes from? Where should I roll my data or application back to, if there is no previous state at all? That would either require me to keep swapping apps to each other and have that variable C as temp variable, we used to have in C++.
Anyways, my question still lives, is this what swapping means? — just copying.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
A slot is a location where you can deploy your application to meet different needs in the application lifecycle. For example a development slot, QA slot, Production slot etc. You deploy to the different slots as you move your code through the lifecycle.
To my knowledge, deploying to a slot only updates the contents of the target slot and doesn't have any affect on the source slot i.e. it is unaffected by the deployment.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
How can MS take their own Edge browser seriously when it forces you to use two hands to open a link in a new tab and switch to it (i.e., you must Ctrl-Shift while clicking on the link)? Even IE had a better approach!
Anyway, for anyone who plays with other browsers every once in a while, the new version of Vivaldi finally has tearable tabs. Not as good as Google's implementation, but good enough for use. That was the only thing keeping me away from it. Added to tab stacks, Vivaldi is finally becoming a little more powerful. (It also has a 'Right-click, down' mouse gesture that opens links in a new tab and goes right to it.)
I did like that they released edge with lots of deficiencies compared to IE. I have a bunch of issues
1) I liked having the favorites in a folder so that I could copy then, and reorganize them in the browser, Edge removed that.
2) No longer can prevent web addresses from opening, and not even availability to a lot of other preferences. I will have to say trying to find what you wanted in the IE preferences could be a challenge.
Just coming up to the end of the fourth series, and they still haven't found a damned thing worth more than fourpence.
It really is like watching a train wreck, where every tiny bit of ridiculous speculative BS is treated as absolute truth -- until it's completely disproven, by the end of the show.
But then there's more ridiculous speculative BS for the next episode, of course.
We've had multiple Ark of the Covenant theories, multiple pirate treasure theories, and even theories about original Shakespeare manuscripts. I don't think I've ever heard the phrase "Could it be...?" used so many times.
They're either all really great actors, or they all really believe that there's treasure buried there -- as if they hadn't found the real pirate treasure by airing four seasons of a TV show!
Fun to watch though? Hell, yeah!
I wanna be a eunuchs developer! Pass me a bread knife!