My LG has something like that, OLED motion pro. I believe it displays blank frames given the panel runs at higher than 24fps. Medium is noticeably darker but oleds have plenty of brightness for my viewing space and it makes slow pans look much nicer. High is even darker but adds noticeable flicker to my eyes
I think they mean when using the in-browser editor for lambdas in the AWS console. This will let them get actual vim usability instead of an included vim-mode thats not up to snuff.
Even without sarcasm the wording here reads as a presumption that this person will do work (blog post) for your benefit. Their post not indicating any plans to do that is why it reads so sarcastically, a sort of “pull requests welcome” reply in a more rude way.
Part of the reason I settled on beancount over h/ledger was the ease of writing python plugins to handle mutations and rules, and reuse the official parse/output as a library.
Plaintext is nice for git but I only feel that when fixup-ing a single or small number of transactions. It does feel nice to be have all the details of a transaction in one place in a visually useful way. For one-off hacking and such it definitely feels easier to write O(n^4) python looping over trying to describe things with SQL and working at a scale where it doesn’t matter.
Plaintext as a UI into a SQL store seems an interesting project. I would love a git integration for committing changes after diff review and being able to stage individual txns or parts. Many years ago I was frustrated with ledger’s more loosey goosey syntax and trying these things and eventually gave up whatever the idea was at the time. I like the idea of a constant bidrectional sql<->plaintext that provides a requirement for reproducible parsing and serializing
Portland has also been working on the “next steps” pointed out in this article. Street bioswales provide absorption and holding capacity. Downspout disconnection programs and new build codes drain rooftop rain locally on the property or out to the street instead of directly in to the sewers.
I think we have an easier time due to our lower density. Most lots have decent amount of exposed ground for rain infiltration, and the area has well draining soil. Tougher for cities more tight and built up. I think Seattle codified water management before the latest building boom so hopefully they will do alright too!
I do wish discussions like the linked blog were more clear on specific use cases features would enable. Async summation shows off the syntax sure, but I don’t know any real world problems that are currently hard that this would make easy. Not to say there aren’t, just I don’t know them and would love to understand!
I like trying different beers and having novel experiences. Trying a local beer isn’t always amazing, but sometimes it’s unique and great, worth the risk to me.
The unit under testing could be the API interaction. If I wrap an external API in a client library I would test it’s behavior before then mocking that out when testing other code that uses the library.
I think situations like external API hit a fuzzy line between unit/integration. For testing an API unit I would reach for some way to save, re-play, and re-record those interactions just for sanity sake.
To me an integration test would be multi-step behavior, not just testing a specific request does a specific thing but a chain of requests, or verifying side-effects.
Encryption is a useful tool (and a fun research area), but like all tools, it's only useful if properly employed. If used in inappropriate situations, it won't provide protection and will create operational headaches and perhaps data loss from mismanaged keys.
PCI is a useful tool (and a fun research area), but like all tools, it's only useful if properly employed. If used in inappropriate situations, it won't provide protection and will create operational headaches and perhaps data loss from check lists.
Concurrency is a useful tool (and a fun research area), but like all tools, it's only useful if properly employed. If used in inappropriate situations, it won't provide protection and will create operational headaches and perhaps data loss from lock contention.
AI is a useful tool (and a fun research area), but like all tools, it's only useful if properly employed. If used in inappropriate situations, it won't provide protection and will create operational headaches and perhaps data loss from Skynet.
Computers is a useful tool (and a fun research area), but like all tools, it's only useful if properly employed. If used in inappropriate situations, it won't provide protection and will create operational headaches and perhaps data loss from solar flares.