Better to book directly from whatever hotel / airline / whatever you want to use. Whatever savings you might get is not worth it and a lot of times hotels appreciate direct bookings and they're cheaper anyway.
In South East Asia hotels are cheaper on Agoda and even contacting the hosts directly wouldn't get you a better price most of the time. It's a waste of time to try so I stopped doing that.
Likewise, we wanted to stay in a resort for a few days afterwards and relax, so she sent us some ideas, but they were so lacklustre that we almost gave up on the idea of that part of our holiday altogether. Then we found something ourselves that was much nicer, and have been enjoying lovely beaches and incredible food for the last few days.
Even her flights were weird choices that involved a lot of waiting around at airports and would have brought us back a day earlier - booking them ourselves got us cheaper and more convenient options.
I always assumed that a travel agent would be more convenient than looking for something yourself, but I was amazed at how poor our experience was using one. Less choice and flexibility, and as you say, less self-service, and for us self-service gave us exactly what we wanted.
I think the best "cheap" travel agents nowadays would just do the job of searching for you for an explicit fee, and then just send you the links. This is generally useful when you have specific requests and not much time to find them.
> With Continuity Camera, Mac users can leverage the powerful camera system on iPhone to unleash a groundbreaking webcam experience
I don't have the energy to parse a lot of text like this...
1. Using the https module directly was more work than I expected, especially with error handling. This made me really look forward to the new Fetch API coming out.
2. No CLI parser. Its not like parsing args is a LOT of work - but its also something that is already solved and having to write support for that directly was a bummer
3. No logging library. This one was pretty easy. Create a little class with logging levels. Again this is something that is very common that would have been nice to use a package for.
As for point 2, Node 18.1 I think just introduced a native argument parser.
It’s good to keep seeing alternatives though since the lifespan of such services isn’t very long.
I myself ended up making my own version on AWS Lambda and SES and that worked well for 7 years without a change. This pattern is so common I think an example lives on AWS’ own help site.
I do agree that it could be better. They have been adding print-related features though, at least I remember some in CSS3. CSS Colors Level 4 includes cmyk functions.
dialog was so problematic that the same people that are now promoting it were in favor of removing it entirely. Literally none of the issues were solved, but now it's a great new element that we all should use.
https://web.dev/usb/#get-access-to-usb-devices
However I suppose that the mere existence of this API means that there could be a way to bypass the request; The browser already does have full access to every device.