the body of a practitioner in tukdam does not decompose uh in the same way that a body of a normal person who is not in tukdam does and so uh we've had cases up to 38 days uh inam where the body remains quite preserved uh fresh uh without any smell uh and um with the skin still very pliable and no um Rigamortis

his Holiness um uh his Holiness uh made the request that we investigate tokam and I believe that one of uh his interests his Holiness his interest in studying took down is because this represents a real challenge to Western science because uh uh the suggestion in the traditional Tibetan texts is that there is a subtle quality of awareness that is still present even after the conventional Western definition of death after the heart has stopped beating after the breathing has stopped there they're said to be uh this subtle quality of awareness uh this clear light stage that is still present

As for publishing this as an actual gem on rubygems.org...I have enough open source I'm involved in all ready (or too much, as my wife would probably say) and I'm not really interested in maintaining another gem.

But I take comfort in knowing the past is there, if I want it.

The Great Basin Bristlecone pines are an extremely rare species found only in California, Nevada and Utah. The dispersion of this species is perhaps thanks to the wind, or the Clark’s nutcracker, or maybe some other bird that is now extinct, as they may have traveled with the seeds to other remote areas of high elevation.

The ticket which tracks issues using Gmail with Thunderbird (Bug 402793)

I've worked with people at companies where this was their only responsibility. Setting up emails for clients, making sure they pass a battery of tests and look great in all browsers and clients. It's an incredible PITA and it's not a set it and forget it thing. Clients can change month to month; spam filters change, etc...

Before a bug can be fixed, it has to be understood and reproduced. For every issue, a maintainer gets, they have to decipher what was supposed to happen and then spend minutes or hours piecing together their reproduction. Usually, they can’t get it right, so they have to ask for clarification. This back-and-forth process takes lots of energy and wastes everyone’s time. Instead, it’s better to provide an example app from the beginning. At the end of the day, would you rather maintainers spend their time making example apps or fixing issues?

At work, I cannot maintain this project. At home, I'd rather spend time with my children and on projects that I'm currently passionate about.

In Rust, we use the "No New Rationale" rule, which says that the decision to merge (or not merge) an RFC is based only on rationale that was presented and debated in public. This avoids accidents where the community feels blindsided by a decision.

I'd like to go with an RFC-based governance model (similar to Rust, Ember or Swift) that looks something like this: new features go through a public RFC that describes the motivation for the change, a detailed implementation description, a description on how to document or teach the change (for kpm, that would roughly be focused around how it affected the usual workflows), any drawbacks or alternatives, and any open questions that should be addressed before merging. the change is discussed until all of the relevant arguments have been debated and the arguments are starting to become repetitive (they "reach a steady state") the RFC goes into "final comment period", allowing people who weren't paying close attention to every proposal to have a chance to weigh in with new arguments. assuming no new arguments are presented, the RFC is merged by consensus of the core team and the feature is implemented. All changes, regardless of their source, go through this process, giving active community members who aren't on the core team an opportunity to participate directly in the future direction of the project. (both because of proposals they submit and ones from the core team that they contribute to)

The only "issue" it has is that its unfamiliar. People have been working with HTML for years and are comfortable with it. That's basically the only reason that people find it more readable. If you make an effort to spend sometime with hyperscript, it becomes as familiar and readable as jsx.

So, which is better? t.inspect # => "2007-11-01 15:25:00 8483885939586761/68719476736000000 UTC" t.inspect # => "2007-11-01 15:25:00.123456789000000004307366907596588134765625 UTC"

Someone who took the afternoon off shouldn't feel like they did something wrong. You don't have to defend how you spend your day. We trust team members to do the right thing instead of having rigid rules. Do not incite competition by proclaiming how many hours you worked yesterday. If you are working too many hours talk to your manager to discuss solutions.

I do develop Open-Source Software during leisure time, for free and whenever I have enough time, energy and motivation for it.

Warehousing and storage revenue in the United Kingdom from 2010 to 2022

Activities such as time spent on task and discussion board interactions are at the forefront of research.