crznp

As someone who lives in a fairly spread-out city, I still prefer bikes and public transit. Or skip the commute entirely and work from home.

I know that isn't true for everyone, but for me the edge cases are the only case for having a car at all.

For me, it really depends on the type of video. For fixing cars, I'm usually looking for something specific enough that there isn't a lot of chaff. It was probably recorded and edited on a phone just to splice the clips together. Probably the default thumbnail that youtube extracted from the video.

For product videos, if Project Farm did it, look there first. Otherwise, I look for someone has a lot of videos for competing products with basically the same format, not over 10 minutes.

Tech videos are the hardest, I often still prefer text. Maybe look for links to the docs in the description? I still get duds though.

If you follow rfc4648, those are "base 64" but not "base64":

> This encoding [using '-' and '_'] may be referred to as "base64url"... Unless clarified otherwise, "base64" refers to the base 64 in the previous section ['+' and '/'].

I cannot downvote here anyway, which is fine.

On other platforms, I have come to believe that it is healthier for me to reply to content that I feel good about upvoting, and just moving on if I am tempted to downvote.

You could say that the Netherlands is more suited to trains because it is flat and easy to build tracks on. Or because it is dense.

Or maybe the Netherlands is poorly suited to trains because it is dense and difficult to get suitable land. And because it has ports and is close to north sea oil, so why not use cars?

Switzerland and the Netherlands have trains because they made a decision to develop that strength, not because of their (polar opposite) geographies.

Do you want it preheated? It might improve ignition, but isn't it a heat engine that gains efficiency from a large temperature gradient?

Lots of TLAs:

ATT: Apple's App Tracking Transparency, not AT&T

FBA: Fulfillment by Amazon, not related to FB

DTC: Direct To Consumer, not Depository Trust Company

For (1), anything outside of the code is going to be missed in the next code review. Eg:

// ACME-1275 Acme uses desc field to identify references

Perhaps you can use the reference to point to wherever you documented it. I'd rather just keep the ticket reference, which won't change. Who wants to read docs that get into that kind of minutia anyway?

But without any comment, I'm wasting time looking for it, if I even realize that there is something to be looked up.

Finland and Iceland also have some of the highest suicide rates in Europe. It seems that the correlation between happiness (or well-being) and suicide is complex.

Which makes sense: it can be isolating if everyone around you seems to be thriving and you aren't.

That's interesting. How relevant is energy transport in comparison to the optical effects?

Eg: my understanding is that hurricanes are net cooling because they transport heat from the ocean surface to the upper atmosphere. Presumably the same can be said for cumulonimbus/thunderheads? Or perhaps it is more relevant when they form in the day and when they dissipate at night?

I don't think it is a strange point of view: Fedora is a good outcome, so don't question how the sausage is made.

Maybe it is shortsighted in the long run? We'll see. I'm glad that we have choices -- AUR on one hand, Fedora on the other (and Debian, Alpine, etc)

It was always "permissionless publish", but it is worth remembering that it wasn't a free speech system (until alt.*) Each group had a manifest of rules.

I think that the issue was that the enforcement mechanisms were largely social, so they broke down when it grew too large, especially when ISPs and others started running servers without engaging in the community.

> NO_PERL=YesPlease

git showing off its inner INTERCAL

I agree with your main point, but Arizona is $13.85, Colorado is $13.65 and Illinois is $13.00.

I think you misread: GP claimed that PTFE is a type of PFAS, and separately: PFOA is also a type of PFAS. And if PFAS is the problem, it wouldn't be useful to ban specific classes like PFOA if they are just replaced by different classes of PFAS.

I'm not sure about the last claim: it isn't clear that all PFAS are equally bad, so replacing PFOA with a different PFAS might be worthwhile. It seems hard to study, but with Europe banning PFOA, perhaps we'll get some more insight.

If we imagine that excess water from Wyoming is used to grow crops in California, it seems reasonable to assume that it would be less moisture/precipitation for Nebraska.

But if it is used to grow wheat in Colorado (because the obligations to lower-basin states need to be met regardless and the increased moisture allows more diversions across the continental divide), then it probably ends up evaporating anyway or else in the Platte River. It wouldn't be stealing moisture from Nebraska, they might actually benefit from it.

Geo-engineering might not have a free lunch, but it also isn't a zero-sum game.

Reddit's main asset is its community, so it is odd to cast the community as their opposition.

Do cities have redundant water sources though? Not all of NYC's water goes through Hillview Reservoir, but it seems like a pretty serious vulnerability to me. It doesn't seem like a terrible analogy.

But cities are worth the risk, can you say the same about nuclear plants? Most established designs can't operate as peaker plants, or even seasonal plants (eg: covering for solar in the winter when there is less sun and more load for heating). They are expensive because they are mired in political issues and red tape. I don't think it has to be like that, and I wish it weren't. But is fixing nuclear an easier problem to solve than to invest in grid storage and more dynamic pricing?

They both made claims. Spy agencies claim that they're not spying on their collective citizens. But it seems that they do, eg:

https://www.theguardian.com/world/2013/nov/20/us-uk-secret-d...

On the other hand, I'm not sure that the USA has enough protections in place that they feel the need for an intermediary.

I have the same issue, but with the opposite conclusion: if this were integrated with cp/mv/dd, I wouldn't be able to rely on getting the new versions.

But since it is separate, I can install it where and when I need it, perhaps with the transfer already in progress. That might be hard for IoT/containers, but do I really need to see file copy progress in those kinds of places?

He does: 75.9km on the map, 77.0km when accounting for elevation. With the caveat: "Well, it's never as much as I'd think and it depends upon the accuracy of your terrain model"

It might not be worth the delay to investigate, but it is certainly worth the time and money. If it is an easy win in one case, how do you identify the hard wins?

Perhaps more importantly, you learn the biggest hurdles so that you can address them. For instance, the UK doesn't want its power to be at risk from political instability (more than it is already). That risk can be addressed in part by working with the local population: perhaps you allow for co-located grazing so you're not displacing herders. Perhaps encourage joint projects that also provide local power so that Moroccans benefit from the project (beyond just the ones in power).

What about security? It seems a bit concerning if 8% of UK's power can be knocked out in a single attack. How would you address that?

Mr President, we must not allow a grow light gap!

I don't think that your points are actually in conflict.

If this is my source code, I want the whole history. I want that 10-year old commit that isn't used in any current branch. A build machine may not need any history: it just wants to check out a particular branch as it is right now, and that works too.

But there is an intermediate case: Let's say that I have an issue with a dependency. I might check out that code and want some history to know what has changed recently, but I don't need that huge zip file that was accidentally checked in and then removed 4 years ago. If it were a consistent problem, perhaps you'd invent some sort of 'shallow' or 'partial' clone, something like this:

https://github.blog/2020-12-21-get-up-to-speed-with-partial-...

As you said: a Peltier heat pump is a purely electrical device, so if you're using a broader definition of the term, it could be a variety of different types of devices.

But that is the introductory paragraph, the author is defining what they mean by "heat pump": a device for heating a house which is powered by electricity. You could power it with something else, but the point is to replace natural gas furnaces.

I need a test runner, so I install "karma" and therefore "braces" and "fill-range" and "to-regex-range" and "is-number" and 100 other things.

Dependencies come with risk and cognitive load: deleted like left-pad or loaded with malware like ua-parser-js. Sometimes that is worth it. But if you need 10 lines to pad a string or validate a number, copy some code off of stack overflow like a real developer. Nobody has to know.

Amazon had a net income of $33b in 2021 with ~1600000 employees: ~$20k/employee. Exxon had $23b with 63000 employees: ~$360k/employee. I'm just using numbers from a quick search, and it won't be great because they both have a lot of subcontractors, temporary workers, etc.

The point is that this metric is dominated by the most numerous workers, which probably isn't IT outside of big tech (or even in big tech). The real metric is impact that a particular hire has on the bottom line, which is hard to measure. Really, I think it is more about their separate job markets: Exxon posts positions in Dallas and pays what they have to to fill their positions, Amazon does the same in Seattle and gets a very different set of candidates.

Corollary: if you think that everyone is incompetent, perhaps you're missing something.

For instance, you fly with AAL because of price, food, service. What sort of entertainment system would change your mind? It is hard to create something that works for everyone, is integrated with a plane that doesn't have a lot of downtime, etc. I'd rather just use my own device, so the best entertainment system in the world is unlikely to change who I fly with. So why invest in that?

Or on the original topic: the problem is not that they can't develop a similar app -- if nothing else, they could license this one or just turn a blind eye. It seems like they don't want it to exist.

To me, Scala's issue is identity crisis, not complexity. Some of the community wanted to pretend it is Haskell, and others wanted a better version of Java. But if you want a JVM functional language, why not Clojure? If you want a better Java, why not Kotlin (or update Java). Scala is squeezed by more consistent alternatives on all sides.

I don't think that Rust has the same issue: it has a clear (albeit potentially complex) vision of what it is trying to do, which is distinct from C and more consistent than C++.

Consider this version: there is someone on the track and if I don't act, they will almost certainly die. Or I can act and almost certainly save them, but it sends the trolley somewhere unexpected.

If I were a professional rail operator, I could take action. I know how to operate the switch, I know where both of the lines go, I can contact the trolley operator to let them know what happened. As a bystander, I would not take action. Maybe it would save that person, but dooms all the passengers on the trolley. Maybe someone had it under control and I'm throwing a wrench in their plans. In general, we probably don't want random bystanders to be messing with the operation of heavy machinery.

Sometimes there is a duty to act: if I am babysitting a child and they are suffering in the cold, I better bring them somewhere warm. I may have some responsibility if I see someone suffering in the cold and I have an extra blanket that I could give them. But I am not responsible for buying blankets to give out every time it is cold, nor am I responsible for throwing railroad switches. In those cases, I am more culpable for my actions than my failure to act.