![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/10433bc7-e46d-46fa-810c-a5c246fc3a94.png)
Or there will be one/several episodes showing the backstory of the fire that she’s getting revenge for, where Carrie-Anne will be heavily featured?
Or there will be one/several episodes showing the backstory of the fire that she’s getting revenge for, where Carrie-Anne will be heavily featured?
Watch in 10 years, Filoni will introduce a Jedi who can see into the past and they’ll retcon this guy into the lore.
Although Obi Wan was pretty meh, I think that most of the recent stories set during the Rise of the Empire are the best because the heros are the underdogs and the Empire is such a formidable foe. I think a lot was missed by not exploring the The First Order’s rise, and just that we were introduced to them as the new badies who are just like the empire. I guess Disney is relying on Filoni to fix that after the damage has been done.
If you haven’t seen it, check out The Clone Wars. Quality from episode to episode varies, but overall, it’s highly rated and towards the end of the series it’s some of the best Star Wars content there is. You can find lists online of the best essential episodes to watch.
It feels like this needs to be managed on an instance by instance level and not post to post.
Seriously, now that this is more widely known, it’ll for sure be taken advantage of a lot, to the point AWS will begrudgingly protect their customers once the damage is done.
If your services are not stateless, work to make them such so you can learn about scaling in the cloud, which can even be done w/ VM-based services. how much more agility using cloud vs a DC gives you
This can’t be understated. Embracing elastic idology to remove single points of failure and decoupling stateful aspects of applications has been the biggest takeaway of being part of several migrations of services to AWS. Implementing these into your practices as you grow is a huge benefit that may is worth the cost.
Over time, if the scale you’re operating at grows, using experience/knowledge from AWS and applying it to running services in a datacenter could be beneficial. In my experience, if you have a large, consistent, asynchronous workload which you’ve maxed out on reserved instances or savings plans, it is likely cheaper to operate on your own hardware than in the cloud (or get credits from GCP or Azure to migrate services to reduce costs). This is where avoiding vendor lock-in is key.
have y’all factored in all the time/money spent on maintaining the server hardware, power, DC cooling, etc. too?
For sure, this isn’t 2007 where you need to purchase servers and network equipment to start a website. For most startups and small businesses, operating in the cloud will be less expensive upfront and likely over the first 3 years. This isn’t a one size fits all approach though, and it’d be prudent to evaluate the cloud spend periodically and compare with what’d it’d cost to manage it entirely. Obviously you’d need a team competent enough to manage this, without it going to shit.
This 100%. I hate getting added to a PR for review with testing commits in the history, and I’m expected to clean those up before merging into main.
Right, for junior devs or trivial changes, that’s fine. My take is if I’m going to make someone take the time to review my work, I take the time to make sure that it’s cleaned up and would be something I would merge if I were reviewing it. Most of this comes from working on some larger Open Source projects which still require patches be submitted via email which I know is a real “back in my day” moment, but it did instil good practices which I try to carry on.
If you’re using the CLI and cleaning up a branch for a PR, the interactive rebase is a godsend. Just run git rebase -i origin/main
(or whatever your target branch is) and you can reorder/squash/reword commits.
In my experience, I prefer to review or contribute commits which are logical changes that are compartmentalized enough that if needed, they could be reverted without impacting something completely differently. This doesn’t mean 1 commit is always the right number of commits in a PR.
For example, if you have a feature addition which requires you to update the version of a dependency in the project, and this dependency update breaks existing code, I would have two commits, being:
When stepping through the commits in the PR or looking at a git blame
, it’s clear which changes were needed because of the new dependency, and which were feature additions.
Obviously this isn’t a one size fits all, but if someone submitted a PR with 12 commits of trial and error, and the overall changes are like +2 lines -3 lines, I’d ask them to clean that up before it gets merged.
Is it normal to use white vinegar as ear drops?
That scene in the beginning was amazing. I never felt that Anakin and Obi Wan’s relationship was shown as brotherly in the prequels, but TCW changed that. Adding this scene makes the fight way more impactful than it was in the movie.
I’m not sure how a deny/allow list would work on a site by site basis, considering the post in this example was from The New York Times. Would you propose blocking all submissions from NYT?
Searching online points to the movie Drillbit Taylor maybe being where this came from, but I have not seen it to confirm.
Those temperatures are pretty cold. It’s literally illegal where I live for landlords to not provide at least 68 during the winter when the temperature is below 55 outside.
Thanks for nothing!
You posted this to a World News community, but would have rather waited for it to be verified? Why post it in the first place if you’re unsure of the credibility?
Also not a lawyer, but right to be forgotten applies to search engines to remove articles from the search index. Originally applied to news articles some guy in Spain didn’t want showing up when you google’d his name. The law doesn’t require the publisher to remove the content from their website, but instead requires search engines to remove the links in results.
So if someone’s comment was mirrored to Lemmy AND that comment was indexed by a search engine linking back to a Lemmy instance, then you still have the right to request Google or Bing or whatever to remove those links from search results via the same process.
I manage a stack like this, we have dedicated hardware running a steady state of backend processing, but scale into AWS if there’s a surge in realtime processing needed and we don’t have the hardware. We also had an outage in our on prem datacenter once which was expensive for us (I assume an insurance claim was made), but scaling to AWS was almost automatic, and the impact was minimal for a full datacenter outage.
If we wanted to optimize even more, I’m sure we could scale into Azure depending on server costs when spot pricing is higher in AWS. The moral of the story is to not get too locked into any one provider and utilize some of the abstraction layers so that AWS, Azure, etc are just targets that you can shop around for by default, without having to scramble.