1,068 karma · joined June 21, 2011
It seems no matter what Germany does, it only promotes fossil fuel usage. Quite opposite of what they wanted...
It is solely US thing that medical procedures have astronomical cost.
Nice experiment, anyway.
> Increased energy efficiency on component level
> Increased energy efficiency on data center level
Why no “Increased efficiency on software level”? Is it simpler to throw hardware (and money, energy, carbon emissions) at the problem than find better solutions?
this happens when you add JSON version for old XML-based APIs (seen this multiple times)
And a fee is just a small bump in the way of bad actors that would like to monetize their misdeeds.
Today most commodity servers (which you can buy out of pocket without lengthy preorder) can accomodate from 1.5 to 3 TiB of memory.
As another poster linked ag-grid this is how API surface should look like: https://www.ag-grid.com/javascript-grid-server-side-model/
Size of data can be:
1. Small, so you can display it all at once and the user will have luxury to ctrl+f what he/she wants;
2. Big to display, but small enough to push to client: then you will need to create pagination or virtualized view. Ctrl+F will not work (at least without some tricks), but you can easily filter/search it yourself in JS;
3. Too big to transfer: the only way to search/filter is on the server and separate controls (of course Ctrl+F won't work).
Throughout my web-dev career, I did table or detailed-list views many times, but each time with different requirements. Aside from sheer size of code to implement all the features, you will have contradicting requirements and there is no one-size-fits-all solution.
Top concerns are: 1. is your data homogeneous (all columns in a row are presented equally) 2. can this data change? 3. is there a lot of data? (so you have to implement virtual list) 4. is data dynamically loaded? 5. do you need actions on data, and how to display them (inline / overlay / menu?) 6. some features are really simple on surface (resizing, drag-drop reorder of rows, auto-sizing on dbl-click is a hell of itself) but are pain in the ass to implement. 7. is filtering/sorting done on a client or you have a server to help you? 8. and many many more...
There are multiple implementations, but you have to investigate which one fits you need.
When I gave the first version to our testers, each and every one of them came with non-overlapping set of features. Some of these features are listed in this article and even more.
If you look into details, you will be amazed how many features there are in such common and simply-looking interface element. It took me (and the testing team) more than a couple of weeks to "kind-a finish" this work.
Of course well-thought release policy will help immensely (how to test, when to release, staged rollouts, etc...)
In most of contemporary books and university courses "combinational" is used and with a note that you should not confuse it with "combinatorics" and "combinatory logic"
it's "combinational circuits", not "combinatorial" (that's whole another part of math)
looks like over-engineering of (bits + 7) >> 3
Speaking of "smartlocks": here’s one that doesn’t even need a drill: https://www.youtube.com/watch?v=WeCGTosv-_c
Edit: and another one https://www.youtube.com/watch?v=mGpMaShltbc