I remember using it as a kid.
You could really select anything (or seemingly anything) and have its inner-workings explained in a nice set of animations!
I still have fresh in my mind of how a car speed-o-meter used to work.
212 karma · joined September 14, 2018
I remember using it as a kid.
You could really select anything (or seemingly anything) and have its inner-workings explained in a nice set of animations!
I still have fresh in my mind of how a car speed-o-meter used to work.
This is like mentioning in your rule-book that metal toothpicks are forbidden because I don't know, people can short your batteries or whatever. But also banning wooden toothpicks without mentioning this in your rule-book.
Their ToS are not always vague but the way their terms are executed is definitely arbitrary.
I use it for steaks because they are hard to sear in other cookware. The cleanup and seasoning processes make cast iron hard to use for anything else. I plan to get a ceramic one (with iron core) but even if it solves the seasoning process and the cleanup process, it isn't the best to sear steaks in it.
My point is that each tool has its use and in this specific case, cast iron is not the tool for everything.
The choices for RAM configuration come down to 8GB, 2x8GB, 8GB + 16GB and 8GB + 32GB.
That makes the second option the only dual channel configuration. Going past 2x8GB is not a real upgrade but more like a side-grade.
proof:
{"proof":{"A":["1867600411780067514172598894560508538153359060380045576693586005748057954966","2169620374930453391614857867828473542574014121006630399026967709955925850380","1"],"B":["19528498564528468902521634480986489044663227437233934360035138487189177722814","706337827303094147746432169922700503982765234262612631196531687654713865722","1"],"C":["3726874825357289054925101646028211344121805780590499285615367952100310015198","16413790865300145964228939489264611981079279422219583850941964454619012987205","1"],"Z":["13348398295372116628737687800239385003236584392082957129655537090979023752552","21858938086065692615790404191021275401630119897894808135127612791495958708375","1"],"T1":["14360876145883521049062480571414414707162979629186454824314165195068098843755","7690383252743723537382002605037505508108694574090623371839489928167967159302","1"],"T2":["171526585437306849736171820938322340084660417215376900416315101905819784325","14860073408830920977059163351151904508851804307761461334115941048614121404124","1"],"T3":["1545121168750639889943334802450434695241204658831402130294781806168831416544","3552441256981354095031652913768122490293154222496855043326406989226641931070","1"],"eval_a":"11024792588659243456083103589833329966520500410691012025757085783760664829419","eval_b":"8139322387519291544452196793779464185899888022676212695935483571119961089263","eval_c":"2759381562617869781993539883850313928775692869004537050116210023174425255732","eval_s1":"3982161546082334136949334514760679925162813832987926352276128359736663202279","eval_s2":"13722404104721347388598646963457682656505421852782227871567200092865223175205","eval_zw":"11818614898752314321908019464035292475883958508517334670201070690246297959919","eval_r":"351033371214975959271810948327526637663211703371176137228232410629160426468","Wxi":["2849642276594154825911327435597652863159285743523681959629445273984338402763","17443880865908727420293433216572018364053739032965083704472720153118177741102","1"],"Wxiw":["10956474329499098723358633860519149253944380573151016916071333176886419683119","10706455989148992485159392381934694626464450509616938982009682610544795496695","1"],"protocol":"plonk","curve":"bn128"},"publicSignals":["14870881943777737729426810002848629979047457360865816386884132744016829330171","5"]}For a few hackathons now my team tries to push a client-side frontend + smart-contracts on a blockchain as a backend solution. This has a UX hit (some downsides of it could be mitigated though) but it made our business logic easier to implement. Depending on the project it has additional benefits to go with this stack. This cannot be applied to every project though and usually the UX hit or the lack of private transactions is enough to favor more traditional stacks.
I would also like to see YAML converted to NT and back to YAML just to see if there is any information loss.
This doesn't involve digging a deep hole in the ground and hope that the earth keeps it level.
A drawback would be the hazards that heavy tension/forces bring with them.
Am I expected to believe that friction caused by pressing your finger on paper can supply enough power to make a successful bluetooth transmission?
This falls a bit under dev-ops and sysadmin but it would unlock your brain to think in different ways.