melissalobos

> In some versions of English it is mispronounced

This is more a misunderstanding of how dialects work. There is no "English" if you consider British, Welsh, Scottish, and Australian English all English which most people do. There are even more extreme forms of English which all can be mutually intelligible with English, but sound very different. There is no one way to pronounce anything, except in a particular dialect.

In Standard American English true. There are many many dialects and local versions. Listen to the Great British Bakeoff for one full episode and note if you ever disagree with any pronunciations. Now go to Indonesia, where I spent a great deal of time and tell me that Cleaver is never pronounced Clever.

Given that we have latex, pandoc, markdown, asciidoc, etc., I really don't see the need to learn it. At the time it was probably a great and transformative tool, but using TeXMaker or TeXStudio and latex gives a far more comfortable writing environment and the documents you can make are much better looking.

Yes! Thank you, I couldn't think of the terms to search for to find this.

> Groff+mom

Apparently mom and ms are some packages full of macros to use with Groff. I am not familiar with these tools and was a bit confused until I read some man pages.

Ever. In some versions of English(of which there are many many dialects) it is pronounced nearly the same as "clever" so "Ever Clever".

I think that is part of the issue with communicating bulk statistics like life expectancy. In reality the median or mean after 15 or after 30 is likely more useful as a measure.

> I suspect that this is way more common than we think

I can't really think of a mechanism that would allow a tree to get nutrients from extruded sap normally(most other plants don't tend to produce much sap in my recollection). In general I think other mechanisms are much more likely for nitrogen fixation.

> they had a life expectancy of like 20 years

This just meant that a LOT of kids died, not that most adults didn't live very long.

> Reference counting is garbage collecting

I am drawing a blank on google scholar at the moment, but I recall a very popular paper on exactly this topic of RC as the other side of Tracing GC.

This sounds very nice, but just to make sure I understand your meaning: If you have a properly designed "systems" programming language(even if manually managed) you would release resources exactly(or nearly so) at the time when a proper ARC/RAII implementation would. Is that correct for your meaning? If so I fully agree.

Even so, github does have a ton of very very popular C libraries(like https://github.com/nothings/stb). I was bringing up the OS provided ones since they claimed not to be able to find any. My main point is that it is patently absurd to claim that they could not find C libraries.

Further: https://github.com/oz123/awesome-c as another example of the many many C libraries you could find.

> The most difficult thing I find about C is the (apparent) lack of libraries and packages

I really am not sure if this is a joke or not, but almost every major library has a C interface. Almost all packages in your distro if you use linux have development versions that ship libraries that usually are linkable by C. In fact the wealth of libraries usable from C is usually noted as its main strength.

What exactly are you missing, and have you tried googling? The GNU organization and similar all produce libraries(like https://www.gnu.org/software/gsl/) that are mostly usable from C.

One big issue with that notation is that the log of the exponential is not the exponential of the log, so the order really does matter(for any complex valued expressions).

https://www.wolframalpha.com/input?i=log%28exp%28x%2Biy%29%2...

So just having over and underbars loses some information.

> Obama: 'We tortured some folks'

https://www.politico.com/story/2014/08/john-brennan-torture-...

I think the GP is trying to make the point that, a scalar in most numerical physics contexts is either a real or complex double precision floating point number(like a double), but they don't see how someone would represent a vector in this geometric algebra(a matrix in Eigen? or a vector in Eigen? myself I would just use a vector, but the GP was interested in the oriented part and seeemed confused). I believe they were looking for an example of someone using this in practice to solve a real problem and have some explanation of the choices made.

> Why? 50k years ago the average person lived with a small group of people and barely ever interacted with anyone else in the world.

I think at least some of the people in this thread would argue against that, seeing as how it is about the idea of advanced or at least extant cities in the distant past. That would be exactly one of the points being argued on.

> By using the LR parsing algorithm

In case anyone else was wondering, this is a LR parser-generator that is supposed to be error-insensitive. Here is a java grammar written in it: https://github.com/lezer-parser/java/blob/main/src/java.gram... which doesn't look terrible.

> deamon

Is that a typo? If not then I see how those would be pronounced the same, but daemon in American English would usually be pronounced "Day-mon". This also helps to distinguish between the long running process and an evil entity, which is good when talking to less technically minded folks.

Indeed, that particular implementation is very fast. One of the goals of the C++ language is to leave no space for a lower level language than C++. A motivated person could just re-implement those algorithms in C++, in the absolute worst case using inline Assembly and at the very worst exactly match their performance. One of the nice things about Julia is you get good performance without going through a huge amount of effort. However you could always do as good or better in C++(with maybe more effort).

One thing is that this library has built in support for H-matrices(last I checked Matlab did not), so it can be arbitrarily more efficient if your problem decomposes in a nice way(most matrices in practice have large low rank sections, so this may be a very large class of problems).

> It's diffeq solvers will almost certainly be worse than Julia (Julia is SOTA there)

Worse in what sense? Speed? Almost certainly not, since you would be implementing the solution directly in C++, so it will be as fast as you need(since you can use inline ASM). In Julia the really good diffeq libraries are not built in and this is not a diffeq solving library, so you would have to implement them yourself if you were just using this(so you can use almost exactly the same algorithms, and with more control over memory management in C++ you can maybe have it be a bit faster).

> Why do you think Rust took longer to change than Python?

Potentially the issues we ran into were due to the inexperience of the team, Rust despite being ~12 years old, most of the programmers we were working with had less than 2 years of experience with it. So if you have a more experienced team, your mileage may vary.

Given that, I think it has to do with the typing system, it is a lot faster to change your structs in python and propagate the changes as needed than in Rust. Asking for another field to be displayed on a web dashboard could take ~1 hour for a team we had working in Django, and ~2 days for a team working in Rust. Of course the projects in question were wildly different and a lot of other caveats, but still in general we found that Python was just much much faster to make changes with. I was not directly involved in any of the programming, but did review the changes, so my perspective may not be the correct one.

> I just came back after months

I am sure this works if you don't upgrade your OS and have more stability in your browser. Running Fedora, we tend to upgrade every ~6 months and due to somewhat bizarre security policy have all browser data wiped every week.

>People should stop freaking out about this. The "more inefficient code" you might get by adding a few .clone() or Rc<RefCell<…>> when the borrow checker complains about something is still way more efficient than anything written in alternative "safe" languages.

But you don't have to use a "safe language". C++ can avoid a lot of copies and be just as safe from an absolute point of view. The borrow checker isn't god and Rust isn't perfect. In an absolute sense the C++ code you can write could be more correct and efficient(it just doesn't tend to be).

> ability to use C libraries directly - and thus original C API docs. I've got battlescars from NPMs deep dependency trees, and cargo is a similar story.

This is something Rust is relatively good at, you just may need some unsafe blocks, but assuming you can compile using clang for the C code everything tends to work well. I am saying this as a Rust skeptic.

> but the iteration... is far better in Rust

That is something I would find hard to believe, if you mean iteration of changes. I have coordinated a few rust rewrites, and at least seeing engineers live programming, it takes far far longer to change and compile Rust code than python.

Could you talk more about your company's process or how you mean?

I like the idea, but needs a better way to save state. I have started this game twice when it was posted, and each time got so far before I had to do real work and forgot about it. If it were a local application I could have just loaded a saved state, but it being a browser app, there is no good long term storage mechanism. Which is a shame since it is fun, but doing a bunch of EE101 problems for the 7th time in my life isn't. I am sure the later parts of the game are even better.

They can, but they usually control the desktop, so if you want a consistent experience it is somewhat ill-advised.

Even if they are getting a bad headache everyday that would be super bizarre. How bad was your office environment if almost everyone is getting headaches every day?