I'm curious, did you actually verify that "it's listening all the time to what goes on"? The Echo devices are supposed to only turn on full power and start listening when they detect the activation word ("Alexa" by default).
It's not so easy to turn off the cognitive background processes that are generating the solutions you apply while doing "focused work". I mostly pay attention to the weekly level of total hours and achieved results. It seems a bit silly to think about individual minutes or hours here and there. I probably would not work long with a customer that was more concerned with distribution of minutes and hours than the overall delivered results and total time charged.
It's weird how many people confuse "storing" with "sharing" because it seems to support their pre-determined narrative. I.e., to my best knowledge, you an store the file in GDrive, but you can't use GDrive to share it to others.
I also use tmux beforehand, when I plan ahead. But I think this discussion is about those situations where you didn't plan ahead and still need to somehow keep a process running.
It's a nice tool (reptyr), but not particularly convenient to use, requiring several steps to move the process to the background and remembering the PID etc. I do wish this was a more streamlined, standard feature of Unix/Linux shells. Something like a simple integrated "pushproc"/"popproc" command.
Informational message: Increased API Error Rates and Latency
We are investigating increased API error rates and latency in the US-EAST-1 Region. This will impact customers ability to make calls to parameter store.
Blockchain based decentralized social networks offer the interesting option of charging a small fee for every transaction, potentially making spam unprofitable. E.g. having to pay $0.001 for every post and comment or something similar.
That seems like a terrible idea. You change the basic syntax of the entire Makefile, forcing anybody reading it to get used to your custom indentation, where almost every line starts with an unnecessary >.
This model has a large reservoir where you can pour the entire bottle and it'll autodose based on some settings. It's a nice convenience that you can just put the clothes in and hit start to wash with defaults.
I disagree with "stuff which nobody asked for" because I have asked for smart features in appliances and generally choose products that have them. However, I do agree that many times especially the smaller and cheaper manufacturers screw things up. Bigger brands seem to often have more reliable products and apps that generally work as intended. I've been pretty happy with apps from e.g. IKEA, Xiaomi, Bosch, Philips. They could all be better but they are serving their purpose.
In my view the level of home network security should be based on actual risk level, eg focusing on automated attacks rather than targeted attacks, and based on an evaluation of what data you may actually lose and could you back it up offline. Aiming for some kind of perceived 100% security will just make you give up a lot of convenience to mitigate risks that probably never realize or that don't actually matter that much.
I love WiFi on my home appliances. Washing machine sends notifications when it's finished or when it's running out of detergent, air purifier notifies when it's time to change the filter, A/C lets me turn it on remotely when I feel too hot, etc. I don't really get people who opt out of these convenience features.
There's no need to fight about it. Those who are not interested in Web3 can just ignore it, and those who are excited can keep developing the technologies. Future will show what comes of it.
Love the irony of this coming from a manager of a fiat currency bank: “My very humble assessment is that it is worth nothing, it is based on nothing, there is no underlying asset to act as an anchor of safety,” she said.
For Node.js there is a nice library called PDFKit (https://pdfkit.org/) which offers a canvas-like API for drawing graphics, text with ttf fonts, and other graphcal elements. I would say it's pretty good if you need exact control over the PDF output.
And in the future, they could be anything. Finland expanded the allowed characters in person identification numbers to support people born after 2000. Usually bad idea to be too strict in checking fields where people manually enter text.
Nope, those are guidelines for creating your own PHP runtime for Lambda. It doesn't support PHP natively. The difference is that you need to maintain and debug your own runtime instead of paying for AWS to do it.
At least I wrote a lot of Ruby on Rails and Django (Python) applications back in the day. They always run their own server. I.e. there is no isolation between the server and between the application code.
The best feature of PHP has always been that it's "serverless", or in more historical terms, stateless. The application itself doesn't have to worry about keeping a server running or making sure it doesn't leak memory or crash. Blast radius is limited to a single HTTP request, just like in AWS Lambda.
The downside is that the PHP service environment does't provide much of a runtime framework, so the PHP application itself needs to perform a huge amount of bootstrapping on every request (this builds up over time as you add stuff to the application). Comparing this to AWS Lambda with e.g. Node.js, Lambda can keep a lot of stuff pre-initialized in memory, and usually just directly execute a handler function. Also things like URL request mapping are externalized to a separate API Gateway. There used to be a lot of tweaking and running separate caching modules needed to make PHP bootstrap fast enough.
I've always been sad that AWS hasn't developed a fully supported PHP backend for Lambda. Combined with a lightweight HTTP gateway, it could be a nice way to keep running legacy apps like WordPress in modern serverless environments, without worrying about server costs and maintenance. You can do it yourself with Lambda layers, but there will be all kinds of small mystery timeouts and problems you have to deal with.
I was doing Yocto Linux development with an older computer, spending ages building OS images. Recently I upgraded to a Ryzen 5950X and now builds complete in a few minutes. They could complete in a few seconds or milliseconds, so it's still not "fast enough" for me. I think I can always come up with something useful to do with an even faster computer.
Are those statistics actually interesting to many users? I barely noticed the move to NYTimes because I'm mostly just interested in playing the game once a day, sometimes sharing the result.
AWS has always had a very clear region system which let's you decide the location where you store your data and run your services. Most popular region here in the EU being eu-west-1 (Ireland), which usually gets new features and updates first. Once you choose a region for your application, it takes some effort to store data outside of it.
1. People are afraid of their current skills and knowledge becoming obsolete. This is similar to people being hostile to the cloud 10 years ago and serverless 5 years ago.
2. People are bitter because they see others profiting from the current crypto boom/bubble, and they didn't buy into it early enough or at all.
3. People are genuinely worried about the darker aspects (non-renewable energy usage, scams, illegal activities) and for some reason they blame the technology rather than the actors actually engaging in those activities.
4. People are problem/solution-oriented rather than vision-oriented. If they don't see an immedate relationship between an existing problem and a technical solution to it, they don't consider the new technology to have merit.
These are just some theoretical reasons I think might explain people feeling so hostile.