There is also spyware running on them. They literally spy on what you're watching and send the info home, and the data gets sold to market to you. No thanks.
Edit.
They also connect to unprotected wifi networks to send data without your permission.
And in the case of Toshiba at least, use their own hardcoded DNS which doesn't honour the one handed up by local DHCP or even the one configured in the advanced settings where you can manually configure the DNS!
I was in the same boat, but I'm taking some time off work and I'm very happy with the Lua support. New link to my dotfiles to come. In the mean time, here are my current ones, in case they help anybody out: https://github.com/hoov/dotfiles. I use MacOS, WSL2, and Debian unstable.
I use VcXsrv in the multiwindow mode where it uses the Windows 10 window manager for each X app, instead of being fullscreen. Is that also slow on a 4k screen?
Or even nothing goes wrong suddenly. Once, I had a vacation planned for six months and had to spend the long weekend cooped up in my hotel room overseeing a complicated migration.
To play devil's advocate, why was a migration so complicated that your engineers couldn't do it without you if it failed, being done on a vacation that everyone knew about for six months?
I won’t say anything the planning, but I’ve learned that migrations are usually hard, in the sense that you have to deal with poorly understood, seldom documented and, almost always inconsistent data. And at the same time critical since you usually can’t afford much downtime between the shutting down the old system and start using the new.
Planning something over your vacation and expecting you to work on it is just your manager being a dick. If they can do it without you, they should. If they can't do it without you, guess it can wait 'till you get back. Not like you dropped it on them last minute.
> There's an asymmetry because Amazon can "afford" to double check everything? How?
Well, Amazon shows you the percent discount. I can't imagine that there are too many items over, let's say, $1000 that are at a 90% discount at any given time. Seems easy enough to flag those for manual review, especially if they are being sold by Amazon directly.
This is so great! While at Adobe, to solve some technical issues, I wrote a microservice that sat along HAProxy, providing a REST interface to manipulate the configuration, validate, and then do a graceful reload. The fact that this is now built-in is amazing, and a lot less clunky. I wish I had this in 2012; it would have saved me and my team a lot of work. And, I'm sure this solution is much better than the band-aid we built.
It's a little more complicated than that. Even with a riving knife, you can still get kickback if your blade isn't aligned properly -- and most cheaper saws need a tune-up before being used.
This is really nice, especially all the integrations. I've been using slides.com for a while, and I may switch to this. But, one feature that would be amazing would be the ability to upload to an S3 bucket. Bonus points for creating a public bucket configured correctly to view the slides. It's annoying to have to carry every possible type of dongle and fight with A/V issues at random places when you need to show a deck on hardware that you don't control. I always make sure that the content I need to show is available on any machine with an internet connection, but it takes a lot of effort sometimes.
A sync to S3 is a nice idea. And it is completely independent from the generator you use... so I would see that functionality as a utility command, called when everything else is finished.
btw: with markdeck, I tried the completely different approach: do not dependent on an uplink, neither when authoring, nor when presenting...
Difficult, but possible. We did this with Buzzword at Adobe. The hardest part was the UX, honestly. Most knowledge workers need some hand holding, to say nothing of teachers and students (we had success selling to high school teachers).
Then in setup.py just read these requirements.txt. I just find this easier to manage all the dependencies from a single point. During development and testing code, you'd assume base.txt is what is going to production. It takes some care to commit this file, nonetheless.
I could keep a freeze version if I really want to have a full view (for debugging purpose).
Not really. A package can be installed in both base and used in test, and vice versa, so you have no real confidence removing the package doesn't break anything. The best you get is explicit duplication.
Perhaps I didn't explain well. test.txt would only consist of packages such as "pytest". The name means a specific function. If you have a platform package that provides APIs for test classes, and APIs for other things like wrapper around AWS apis, then my recommendation is make them distinct package, even if they reside in the same repository. Just have a seperate setup.py. A package in simple terms is just a folder, module is a single file.
Edit.
They also connect to unprotected wifi networks to send data without your permission.