search for: intimid

On Mon, Nov 18, 2019 at 2:49 PM Robinson, Paul via llvm-dev < llvm-dev at lists.llvm.org> wrote: > | mailing lists for longer-form discussions are unfamiliar, difficult, > and often intimidating for newcomers > > > > Um… what? While I know (via my own children) that folks nowadays use > multiple avenues of communication, it’s **really** hard to imagine email > as a **mechanism** being unfamiliar/difficult/intimidating. Moving to a > new mechanism wouldn’t alter...

On Mon, Nov 18, 2019 at 8:49 AM Robinson, Paul via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > | mailing lists for longer-form discussions are unfamiliar, difficult, and often intimidating for newcomers > > > > Um… what? While I know (via my own children) that folks nowadays use multiple avenues of communication, it’s *really* hard to imagine email as a *mechanism* being unfamiliar/difficult/intimidating. Moving to a new mechanism wouldn’t alter the fact of the ver...

> > | mailing lists for longer-form discussions are unfamiliar, difficult, > and often intimidating for newcomers > > Um… what? While I know (via my own children) that folks nowadays use > multiple avenues of communication, it’s **really** hard to imagine email > as a **mechanism** being unfamiliar/difficult/intimidating. Moving to a > new mechanism wouldn’t alter the fact o...

...RSessionDA package (Greg Warnes). More information is available here for those interested: http://zope.org/Members/aho/Open_Infrastructure_for_Outcomes/LiveOIO/liveoio/LiveOIO_1_0_8 There is one statement pertaining to R on the above page that I might challenge: "Unfortunately, it is a bit intimidating to use except by expert statisticians." If I can use it, anybody can... ;-) Regards, Marc Schwartz

...om it[2] due to performance issues. This issue is not unique to llvm-mode, but affects a bunch of projects with very large git repositories[3]. Will it be possible to split this into a new separate git repo? This should make it easier for the emacs community to work with this code and make it less intimidating for new users to contribute to. Current melpa maintainers and previous llvm-mode commitors are in CC. [1] https://melpa.org [2] https://github.com/melpa/melpa/commit/aa2d7a88731ecd9410ab7dc887a7a5f837d8a93b [3] https://github.com/melpa/melpa/issues/5361#issuecomment-387710812 -- Regards,...

...uman readable guide for setting up the lm_sensors for hardware monitoring. I've dorked around with the stuff in the system here, but after looking at the /etc/sensors.conf, I don't think I want to delve into that and try to pull out the right group of settings. It is definately a bit intimidating. So, is there any other software already written or in use for hardware monitoring that does not require a PhD to set up? The current sensors displays both the ISA and smbus readings, but none are even remotely close. The board uses thermistors for temp, which is mainly what I want to m...

...y a strong reason for inherits(), because often in such code, you don't know in advance what objects will be passed to your function. On Twitter, others have asked "the same", arguing that "<someclass>" %in% class(.) > uses usual syntax, and thus looks less intimidating than > inherit() and less cryptic than is() I think you should all use -- and *teach* -- inherits(.) more often, and it would no longer be intimidating. Also, for the speed fetishists: inherits() will typically be slightly (but significantly) faster than ` %in% class(.) ` Martin

...This is my first message sent to the list so bare with me on this one :) I've started learning C++ of September of last year in school. I think I'm fairly competent(I Hope :) at it and we were recently discussing bloatware in class. Vorbis seems so large and complex that I offen get intimidated, so I was wondering if anyone else would like to possible work with me on reducing the memory footprint down from 500K? From what its described, that seems to be fairly large. I have a copy of Visual Studio, so I'm all set with tools. However I'm a newbie when it comes to working on...

On Fri, 30 Nov 2018, Kees Cook wrote: >On Fri, Nov 30, 2018 at 11:27 AM Jarkko Sakkinen ><jarkko.sakkinen at linux.intel.com> wrote: >> >> In order to comply with the CoC, replace **** with a hug. I hope this is some kind of joke. How would anyone get offended by reading technical comments? This is all beyond me... Thanks, Davidlohr

...s pointed out > that we > can probably synthesize that in AsmPrinter with just a little bit of > work. > The above information can't be inferred from stack layouts or > anything else. > > Thoughts? I'm ok with this, in abstract. It would be good to put up some intimidating comments to scare people away from using these flags for anything except for the AsmPrinter, because semantics are tricky enough as they are right now without new subtle bits to worry about. It even occurs to me to suggest putting the bits in a private member in a class and making AsmPrinter...

...ilers and Tools meeting, folks expressed very clearly that our communication systems cause a non-trivial amount of friction for new people trying to find out about, learn, or contribute to LLVM. Both IRC for chatting and mailing lists for longer-form discussions are unfamiliar, difficult, and often intimidating for newcomers. While I have long been a fan and resistant to change in these areas, the feedback from folks at WiCT was compelling and important for us as a community to address. Even if it means I have to let go of my precious IRC. ;] We talked to a bunch of people and looked at the options...

...ften > in such code, you don't know in advance what objects will be > passed to your function. > > > On Twitter, others have asked "the same", arguing that > > "<someclass>" %in% class(.) > >> uses usual syntax, and thus looks less intimidating than >> inherit() and less cryptic than is() %-/ (<- ASCII version of the rolling eyes emoji) <ranting mode> The most cryptic of the 3 forms being by far: "<someclass>" %in% class(x) You need to be able to read thru this to understand that the intend is...

i''ve got several methods in my models i use to find based on certain criteria...i''ve done this so the controller code is less cluttered, plus the DRY factor. example: class Foo < ActiveRecord::Base def find_by_something(something) find :all, :joins => ..., :conditions => ... end def find_by_something_else(something_else) find :all, :joins => ...,

Dear R community, I wrote and someone else helped me type a 5-page R-info in Chinese, covering the most basic information on how to get and install and start using R on Wintel PC. This could serve those not fluent in/intimidated by English but want to start using R. (I met a lot of those in China) <http://www.ms.uky.edu/~mai/ZhongWen.htm> also a MSword version of the same (may print better). <http://www.ms.uky.edu/~mai/ZhongWen.doc> Now I have a question: I am packaging several functions doing empir...

>> And of course, the important related question: Keep it an NT4 domain, or >> upgrade to AD? > Reading this list and the wiki and looking at the seemingly endless number > of options for smb.conf makes the upgrade to AD seem pretty intimidating, > and like you, I don't see any real benefit for our organization. One > concern though, is that future Windows workstations will pretty much expect > to be part of AD domains, so problems will begin to appear on NT domains. > Already I see hints of issues with Windows 10, but...

I'm getting to the point where I want to contribute some more MachineInstr comment support for things like spills. As we've discussed before, we don't have all of the information available in AsmPrinter to synthesize the kind of comments that can be helpful for debugging performance issues with register allocators (our primary use for these kinds of comments). In order to get this

Back in December, there was some discussion here about the Ultra 20''s bios being confused by the EFI labels ZFS uses. After seeing a report about the X2100 exhibiting the same behavior as the Ultra 20, I reproduced the problem and filed: 6407133 X2100 bios intimidated by ZFS-created EFI labels hopefully that bios will get fixed, too. - Bill

...n Rails in your community. There will be plenty of opportunity to discuss projects you''re involved with, recruit talent, and even find out what all of the fuss is about! Unspace wants to support the growing Rails community here, but we felt that a user group was too formal, stuffy, and intimidating to those that are new to Ruby and Rails. Instead, the best opportunity for advocacy is something where people can make friends and have fun in an informal setting. We also welcome people who are working with other, similar technologies. If you are open minded and like to discuss how we can...

...). We're eventually planning to move to git as the primary source of truth, but there will always be svn fallbacks in place. > Will it be possible to split this into a new separate git repo? This should > make it easier for the emacs community to work with this code and make it > less intimidating for new users to contribute to. That's a separate issue, of course. I'm not entirely convinced there are hordes of Emacs developers just itching to help out with tablegen-mode but deterred by the big repository. But maybe I'm wrong. Cheers. Tim.

...ere were 50 or more warnings (use warnings() to see the first 50)" In addition to this, I saw errors such as this one: "ERROR: lazy loading failed for package 'PerformanceAnalytics' What is this lazy loading? More importantly, do I have to worry about all these warnings? I am intimidated by the idea that I have to go back and fix each and every one in order to have a clean R update. Shouldn't the update with CRAN "just work?" Or is there something really important that I am missing? Thanks all for your help. A Lenzo [[alternative HTML version deleted]]