The MS Family stuff has all been broken through the app for me for the past 2-3 months - I get the notifications, get the buttons to approve, and click works, everything seems normal - but nothing ever happens on the Xbox end. I just gave up on it.
These takeovers are often just a case of finding stale DNS entries that are pointed at resources which can be re-allocated by third parties, i.e. elastic IP addresses on AWS. So it's very likely that the person had legit access to that IP, not their fault MS pointed a DNS entry at it when they did not control it.
You can use Svelte completely separate from SvelteKit - we've been using it for a while now and integrating with our pre-existing APIs with no issues, some of those are serverless, and some are just instances behind a load balancer.
Have you looked at Svelte? We've been migrating over to it from Redux/React, and it's so far been a great experience. It's greatly simplified a lot of our code, and eliminated a whole lot of redux/state boilerplate.
Not all portions of VS are maintained to the same degree - their BI tools were horrible for years, and there was not much in the way of alternatives. I'd often spend more time fixing/triaging the IDE issues than I would my own code/projects. And when you then start to add multiple versions of VS into the mix (this was required for the BI projects + newest SQL Server database projects) it gets even worse.
I personally am just looking for a stable tool to build and test images. I can appreciate that Docker is looking for a way to become sustainable, but the way they are going about doing it has become disruptive to how I use the tool, thus alternatives like podman are becoming much more attractive.
The license fee is really not an issue for me - but continuously having to adjust my workflows when Docker Inc decides to change how things work on the back-end is an issue, and it's much more expensive for me than the license.
EKS has actually come a long way in the last couple of years. They now have 'eksctl' that helps a lot with provisioning/de-provisioning the node pools. They're also pretty up to date with supporting new versions of k8s (1.21.2 now, I think). I definitely know what you mean about the 'minimum viable product' and their overall views on k8s though, as our account rep definitely tried to steer us away from EKS when we ran into problems with CronJob. They also don't seem to have any particular relationship with k8s development, so we ended up not able to use CronJob for more than six months while our issue (with k8s repo) just sat waiting for someone to look at it.
Most recentlyv they generate a token on startup, which you need to interact with anything. It's fairly seamless on a client computer as the browser that is launched will get that token added automatically.
Using pandas you can do a lot of that with a query and a connection, dumping to CSV/Excel/JSON etc is pretty trivial once you have your data in a dataframe. It also supports writing data back to tables via SQLAlchemy as well, and any kind of data manipulation you can imagine in between. I'm currently using it to migrate a Mongo database to PostgreSQL.
I've found that a lot of the time Coursera is just making it difficult to register for free for courses, but if you find the right page it's still an option. Go to the specific page for the course, not any collection that it may be in, and when you click 'enroll' look for the tiny 'audit' link.
Of course it works fine with XP, that was the target specs in 2001 when that OS was released. Maybe try a Linux distribution from 2001 and you'd have a fair comparison.
I personally just found the C# syntax more straightforward than VB.NET, C# was new and VB seemed to have a bit of baggage. I never had much in the way of problems, even as a beginner, translating from VB.NET to C# examples though.
I found that with the SC the aiming for games just isn't there. I miss the right analog stick too much, and despite trying I couldn't get anywhere near the accuracy with the SC as I could from a normal XBox 360, or XBox One controller. For games like FPS I just haven't found that the SC is workable.
It based on functionality that all exists in the traditional on-prem SQL Server as well - certainly not the e-mail and point a click creation, but you can definitely query SQL Server DMV's for missing index information[1].
As with any suggested indexes though, they have to be weighed against their effect on other workloads. Additional indexes can have a big impact on inserts / updates / deletes.
The SQL Server Database Tuning Adviser will happily create all the indexes, stats, and what not, for a given workload. And yeah, you can speed up your queries (the workload) as a result. The problem is that there's always a trade off - those queries may now be fast, but inserts and updates end up being slow due to the burden of index maintenance.
There's also maintenance views that can be queried to see if SQL Server is detecting any missing indexes, or if there's any indexes that are not being used - but again these have to be taken with a grain of salt, as the stats get reset each time those indexes are rebuilt.
> Did they build the right indexes? Well... the DB doesn't know.
The DB does in fact know - looking at the query plan for a given query will outline if there are any obvious missing indexes - but having the DB go ahead and build indexes by default for every given query is dangerous. When you go through 10 iterations of an ad-hoc query refining it down to what you actually want, how's the DB to know that the first 9 don't count? Etc..
> You should say "I want to run these queries, and I have this much memory for you" and it should know how to get your results as fast as possible.
That is in essence what the query optimizer attempts to do, though it has breaking points where it will settle for 'good enough' because optimization of the query itself becomes too expensive. Sometimes people just write bad queries.
I'm also a fan of Linux Mint, but prefer the KDE edition - I used to dislike KDE, but with plasma 5.6+ it's become quite polished and nice to use. I've also found LM to be much more stable than other KDE based desktop distro's, specifically KUbuntu and Neon (both of which were quite crashy).