Hacker Newsnew | past | comments | ask | show | jobs | submit | grandchild's commentslogin

SAP runs its own cloud/IaaS in addition to running its workloads on the hyperscalers. It's been doing that for years internally, and that SAP cloud is now being extended to be open for direct consumption by other companies:

https://learning.sap.com/learning-journeys/exploring-sap-con...


As a kid I actually used the theme on my first hand-me-down. As the regular theme. And I remember chosing it because it was fun! It made my computer more fun.

At the end of the day, usability shouldn't trump fun. If I find it's less usable, I can switch back.


Also, I'm working on AVS still, from time to time: https://github.com/grandchild/vis_avs/tree/dev


Once you know that _usually_ people use white cotton gloves when handling museum artifacts, I find it a bit distressing that the person halfway down the article is not wearing any while holding the priceless 700-year-old pages.


“According to the Library of Congress, wearing gloves while handling antiquarian books may do more harm than good. Portland State University Library Special Collections follows their advice to handle most rare and valuable books with clean, dry hands.”

https://library.pdx.edu/news/the-proper-handling-of-rare-boo...

    "Hands in gloves lack the tactility and manual dexterity of bare hands. Handling a book with gloved hands could lead to accidentally torn pages when the gloves catch on fragile edges, or a dropped book if the gloves prove to be loose or slippery.
    Cotton gloves in particular have a tendency to lift fragments from pages, including pigments. Their fibers can catch in cracks that are invisible to the naked eye, further damaging friable pigments and inks.
    This also means that cotton gloves retain a lot of dirt, making them not so clean after all! In this same vein, gloves cause the hands to sweat, and this moisture can penetrate the gloves to wind up on the books. Ew!"
https://blog.library.si.edu/blog/2019/11/21/no-love-for-whit...


Apparently archivists had a realization that clean and dry hands are the most precise for handling delicate objects and that actually mistakes are made with any sort of glove. It's only dealers using white gloves at this point to give a sense of mystique to what they're selling and to give the buyer the sense that only the owner can really touch the object.


To clarify, the use of gloves depends a lot on the item. Books are made to be handled by people and are usually resilient to contact with clean human hands. However there are other museum pieces that are far more sensitive to oil which still merit the use of gloves. For example, here is a video [0] of Adam Savage discussing a piece from the Met Museum which is handled using gloves because they want to preserve it.

[0] https://youtu.be/u_-oUvv28dE


I believe this is no longer encouraged.


From what I understand the gloves are only used on case-by-case basis. For some items they are more damaging than the oils from our (washed and dried) hands.


I feel like you should give the presumption of confidence to the archivist at one of the most prestigious universities in the world.


Yeah bro I'm sure you know more about handling precious manuscripts than a Cambridge University archivist.


Funky! Round trip through Signal worked. But you can tell, because a regular single emoji gets "jumbo sized", these ones don't.


There is also `ts` from moreutils[0]. One of a few gems there. And moreutils is (probably) already in "your" distro.

[0] https://joeyh.name/code/moreutils/


Looks like the `ets` readme has a direct comparison:

> The purpose of ets is similar to that of moreutils ts(1), but ets differentiates itself from similar offerings by running commands directly within ptys, hence solving thorny issues like pipe buffering and commands disabling color and interactive features when detecting a pipe as output. (ets does provide a reading-from-stdin mode if you insist.) ets also recognizes carriage return as a line seperator, so it doesn't choke if your command prints a progress bar. A more detailed comparison of ets and ts can be found below.


Yet another fantastic joeyh project in my toolkit, thanks! (git-annex is awesome)


I think you're misunderstanding what SGX is used for in the Signal context: It's only used server-side. The clients have no real use for it, because they don't have to attest the software they're running, only the keys they possess.

The server however is inherently untrusted, and the users of the server can benefit from some form of attestation of the software it's running. SGX tries to provide this, as the siblings in this thread explain.


It's a bit like the radio version of http://astronaut.io :)


If nothing else, do adopt f-strings. It really makes the code cleaner!


They are on average great, but don't you agree that it's not always better? If the expressions get too long, it gets less readable than splitting the placeholders from those expressions.


This is a tool, for use in certain circumstances. Screwdrivers are great, but you don't always use them.


Some of the linters don't know that and enforce f-strings. I know, we can't let the tools decide but sometimes that's just what happens at a workplace..


I think it's not answered in the slides. Instead they offer two hypotheses for the _characteristic_ of the observation of the declining length-of-day in the last 20 years, with all known effects removed such as the Metonic Cycle: Random walk & Linear.

They present the consequences of adopting one or the other prediction model, but only because one has to be adopted for practical decisions. Not because we necessarily know what's going on.

We can't know now which is the correct model. As always, only time and observation will tell.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: