ThemalSpan

Make big changes now, or be forced to make them later. Stop supporting the meat industry. Take public transit or bicycle if possible. Avoid flying, driving by yourself. Avoid excessive consumption of disposable products.

There is no sustainable future where we get to keep our current lifestyles.

To your first point: iOS takes this idea to its logical conclusion and it seems to be an important aspect of iOS’s performance. https://iphonedevwiki.net/index.php/Dyld_shared_cache

I think its worth mentioning that rust has the gold standard argument parsing library now: https://clap.rs

That library is used by most(?) rust cli tools, so they all have a similar feel. In addition, there is a library built on top of clap called struct-opt that makes bringing up a new cli exceedingly easy: https://docs.rs/structopt/0.2.15/structopt/

Seriously, checkout struct-opts page even if you don't know any rust. I think their demonstration on the front page summarizes a lot of things I like about idiomatic rust.

I use SpaceVim for everything! In a nutshell, its a "shared" configuration for vim (neovim really imho), as well as an extensable framework for adding new functionality.

For example, its nice to have to have plugins offer similiar functionality on similiar key combos. Have a shared configuration allows for once idealogy to take hold. The Spacebad + mnemonics approach of Spacemacs + Spacevim is a really good base to build on.

I could not agree more.

It seems that Radar queues can only grow.

Anecdotally, I didn't find the situation internally to be much better. Many bugs internally go unanswered because there is not enough time allocated to fixing core systems and designing better replacements. The truth is, I know personally of several teams that aren't able to get through the queue of internally filed and scheduled bugs.

To me, it feels like Apple hasn't resourced core pieces of infrastructure and engineering teams in line with upper management's plans for growth. While many teams are relatively sequestered, once you start talking to folks elsewhere in the company it becomes clear that many teams are struggling to stay above water. More still, everyone shrugs about it because it's not clear exactly what is wrong. The best description I've heard is in many cases engineers are willing to offer hacks as a solution to meet management's demands, and management is either willing to accept those hacks or doesn't know better. That is far from a full picture, and its an example drawn from a small slice of an enormous company. But it seems telling to me. I find it completely reasonable to imagine that most teams in a place to deal with customer facing bugs don't have adequate time to do so. Not to their satisfaction, never mind customers.

At the same time, I think it can be hard to appreciate the ways in which Apple is ahead of the curve as far as the categories of software projects it tackles. So I don't mean to imply that anyone is really to blame per se. And it's also a shame because Radar was the greatest bug tracker I have ever used. It is unclear to me if Apple doesn't prioritize menial things like handling external bug reports, or if problems like that are not visible to / perceived by those in the company who could do something about it.

I found the premise to be compelling. I was also previously unaware of research surrounding the notion of bigotry. I would be curious what is known ("or found"?) about the relationship between bigotry and various economic factors.

I found the author's proposed "public health campaign" to be interesting, but in a world where we could implement such a thing, how much bigotry would be left anyway?

I think you're confused by what "child-rearing" means: it is the process of raising children, which includes education and specialized medical care. That is very different than "child-having" or "child-bearing."

They called Splunk out at the top of their SAAS list.

That “smart kids say no to DSLs” meme is funny but also a garbage take if taken at face value. DSLs are important because specializing will generally make you / your tool more effective. Splunk has a special query language that reflects the product’s architecture. If you want to become productive with a piece of software you need to learn its language.

Edit: To clarify my position, Domain specific languages mean domain specific ideas. As soon as a product is no longer meant for general queries, but for queries over specific ki day of information in a specific kind of system, we can use that knowledge to make a powerful language in that domain.

Do you believe that? All that kind of investment does is keep the war machine spinning, and the U.S. will continue to keep the world a violent place.

Investing in healthcare, education, and infrastructure on a global scale would a) be possible with that kind of budget and b) do a lot more to prevent war, since there would be a whole lot less to fight about.

First, let me clearly state that I agree that the "science" surrounding Koko was not great, and that her language abilities are consistently overstated.

However, as someone who has met Koko I can also tell you that there is something there. She did not have a human mastery of sign language, but was capable of communicating new and unique ideas. It was remarkable to witness. She was a genuine friend to those who knew her well. As with most things the truth is somewhere in the middle, right?

I find this issue much more pressing in the defense industry. I (thankfully) have the freedom to choose where I work. I will never willingly work on weapon systems. There are those that do though. Engineers who design things to kill other people. What the actual fuck.

I don't agree with this. As was pointed out here too, software changes in production all the time. This happens with Buildings too, but on a different time scale. Buildings that were made with forward layouts for HVAC and electrical systems will be easier to upgrade in the future. If you look at old buildings that had networking and such retrofitted in a visible and ugly fashion, I think its fair to say that you're looking at technical debt.

I miss DromEd so much... that was the only phase of my life where I was into map editing.

I worked at a company that made CAD/CAM software and had to make extensive use of calculus / linear algebra / computational geometry. Depending on what kind of math you like doing / using, that might be an industry worth looking into. Though it was a software development job, so I'm not sure if that aligns with your interests either.

1.) It's not so simple. There are social mechanisms at play that will lead to a segregated workforce if we do not combat them. In today's world it takes effort to maintain a diverse workforce. As as to whether its a good thing, I think that a) diversity of people means diversity of ideas and solutions, and b) diversity in workers helps combat some of the social mechanisms that would keep the workforce segregated. It is also of the uptmost importance to note that raising diversity in the workforce is orthogonal to compromising on the quality of workers.

2.) Yonatan Zunger's response to the manifesto has been highly shared, but I think his essay "Tolerance is not a moral precept" is an important framework when talking about this issue. The basic premise is that by adopting tolerance as a social norm, we are not agreeing to also tolerate intolerance. Companies like Google have set out the edict that all their workers should be treated with respect. By questioning the inate abilities of a large portion of the workforce, the manifesto's author is doing great damage to the attitude of tolerance that allows Google to operate. He isn't be prosecuted by the government, but he is necessarily being expunged from an enviromenent that he is incompatible with.