Also my sympathies for having to support the so-called "S3 standard/protocol".
67 karma · joined July 13, 2016
Also my sympathies for having to support the so-called "S3 standard/protocol".
I didn't understand this. Who is the author referring to, and what is he implying?
Forcing users to a prebuilt Webkit, that they cannot change is definitely not the same.
I am not sure why they are making this move, what are their goals for doing so.
I'd still prefer the whiteboard interviews, over what are sometimes knowledge-based questions that are a search away. Not the common stuff that you should anyways, but something obscure that if you spent 5-10 mins on its man page, you will get it.
I tried using HTMX recently for mainly a CRUD app for personal use, with limited dynamic loading. Still felt the need to rely on JS(Jquery) for loading images and triggering refresh on list of items without full page reload[1].
Did a small A/B test from dev POV using Vue.js, as it is one of the more lighter frameworks. Ended up leaning more towards Vue.js, as had to do some non-conventional(from HTMX POV)[1] things for a simple CRUD app not relying on full page loads/refreshes. Hopefully there is another step in this evolution.
How do you define being addicted to it, what is your benchmark?
So in a moment like this, you can convert https://github.com/opencv/opencv/archive/4.5.3.zip to https://archive.github.com/opencv/opencv/archive/4.5.3.zip. Maybe an implicit agreement of somewhat stale data by add the sub-domain "archive.". They'll try to maintain low sync times on a "best effort basis".)
Drive alternative is simple enough with "cp -r" and your own bucket. For something like, Gmail and other services, it gets complicated.
This is eerily similar to what I have experienced. I seem to notice the color of flowers, movement of the leaves whilst wearing polarized sunglasses and some infusion of THC.
Anyone with having worked with both, care commenting ?