prettyStandard

Is there a difference between .htm and .html? I never thought so, and noticing they chose .htm reenforces my belief.

Does this help prevent supply chain attacks... at all?

I agree that switching creates waste, not switching creates other waste. If they wanted to minimize waste, they should have released lighting and usb-c iphones years ago and slowly phased out the lighting. Maybe even just update lightning to support USBC speeds. But alas we are stuck with this local optimum when there was a better global optimum that we missed for profit.

I want the STL files for this so bad. Does anyone know if any are available?

You would think we're talking to ChatGPT astroturfing for Dell or Lenovo.

They seem to be doing everything they can to make it not proprietary. I'm not sure if there's more that they can do.

I love rebasing.

As for dealing with merge conflicts, it's called

  - keep up to date with the branch your tracking
  - merge frequently
  - get on a call when you do have merge conflicts
  - avoid having multiple people working in the same files simultaneously if possible

The problem with merge conflicts is you have two people changing the same lines of code at the same time. So I would imagine if you wanted to improve the situation you would need an AI powered version control system that understood the intent of the previous developers. But that's not going to fix bad habits.

While I agree, yes, you should opt to use physical buttons when possible, I'm not going to disparage solutions to any issues.

But also, to your suggested solution, having a button need to be interacted with in VR and a physical button is error prone and annoying. I know I use a button like that daily. I would rather just reach over and stab most of these buttons.

I assume you mean this in jest. I get it.

To be fair/serious if you add the "near past" with "near future" you might get enough time for things to change.

Was there something fundamentally impossible about blood analysis with a drop of blood?

I didn't say it wasn't true I was just trying to say it didn't make sense to me. If you're trying to build a giant supercomputer it seems like you would pick something where the software works. But maybe they are using ROCm. It seems like that only works for the higher end stuff. Maybe they're planning on running stuff that's already been built on OpenCL, and AMD is competing on the price for the publicity.

You might want to overlap the first pass of chunks, something could get lost at the chunk boundaries. Not any sort of expert on this sort of thing, it just seems like an obvious pitfall for the context length.

This isn't entirely make sense to me, I thought AMD was very far behind on GPGPU. Do these supercomputer and data center projects use things like ROCm and OpenCL, and solve the software issues on their side? Does AMD compete on price there?

I assume that other 5% is the internet?

I support posting the list.

> Hungarian notation but as a suffix

Yeah, but only when it adds to the readability. I avoid mentioning Hungarian notation because I don't like it either. I think many criticisms still apply, so I suggest the use case before, where you have the same data passing through multiple types. There may be other good use cases, but I am not sure what those are. This is why my general rule, is "most important words first", I think that technically covers this use case.

lol. I've got good news for you.

My rule of thumb is if you think the variable type may be useful to others reading your code, append it to the end. This is generally useful if you have the same data going through different forms.

Let's see if I can write something, that others understand with no context.

  //For this example let's ignore the nuances of names.
  function (nameUserinput) {
    if(isValidName(nameUserinput)) {
      return processName(nameUserinput))
    } else {
      return { first: '', middle: '', last: '' }
    }
  }

  function isValidName () {
    return (containsAtLeastOneSpace(nameUserinput) &&
            containsLessThanThreeSpaces(nameUserinput) &&
            hasThreeOrMoreCharacters(nameUserinput) &&
            noSpacesOnEnd(nameUserinput))
  }

  function processName (nameUserinput) {
    const nameObj = { middle: '' };
    const nameUserinputArray = nameUserinput.split(' ');
    if(nameUserinputArray.length = 2) {
      [nameObj.first, 
       nameObj.last] = nameUserinputArray;
    } else if(nameUserinputArray.length = 3) {
      [nameObj.first, 
       nameObj.middle, 
       nameObj.last] = nameUserinputArray;
    }
  }

nameObj and nameUserinput and nameUserinputArray are all the same data in different forms. I think it's helpful to start them with the same prefixes, but change the suffix with the type to communicate that.

You could imagine taking this a step further, with nameStatemachine. You might chart a person's course through life, do they go to law school, medical school, get married etc.

I've been meaning to write a blog post on this. But this does follow my most important words first rule. You'll see a lot of similarities there, just not on this exact topic.

https://soft-wa.re/naming-conventions/

lol thanks. At first I was warry about them mainly because I hadn't taken the time to think too critically about. A friend walked me through the simple idea that your stomach is going to tear most things to shreads, so, as long as you aren't taking poison basically, you should be fine.

Genetically Modified Organisms? I was under the impression these were very safe. Can you change my mind?

My thoughts exactly. This seems to be the killer app for openwrt/ddwrt.

Wow, there's no need to yell.

Does Apple warn you when you're setting up that pin that it is the most powerful way to access your account?

I would bet if I walked outside and asked 100 people if they thought the pin was for convenience or if it was the last resort to accessing their account, literally all 100 would think it's for convenience, and a birthday would be sufficient.

I disagree with you as well.

There's no reason losing something 100% of people keep on them 100% of the time should equal losing their online digital identity.

Agree but maybe only show labels for the largest modules and functions and also scale node size relative to function and module size.

Is Nvidia making good on its promise to Open Source it's drivers a d stuff? They may not give us everything but this must be the third or fourth announcement from Nvidia on some open source they are providing I have seen in the past year or so.

So we should expect some builds for Steam & Proton?

By AI?

I agree it does read like the punchline to a joke, that did not escape me when I wrote it, but the larger message is that comments explaining who really owns projects we're talking about are not "unhelpful and unproductive".

Many of the sibling comments were coming from the maintaining freedom perspective, which I personally appreciate as well. I wanted to chime in that this information is also helpful from a corporate/competitive perspective.

Agree with sibling comments. Not immediately relevant to me but at my current position we go out of our way to avoid anything and everything Amazon. Very hard to do. And if a project were backed by Amazon I would be very embarrassed to start building on it at work.

We are so serious about this that I almost got a contract canceled because it looked like they were running on AWS, and we got them to switch to Azure.

I'm glad you posted this. Sometimes I try to describe this gfactor to people, saying "the best indicator of intelligence is any other intelligence". Putting a name on things helps people understand I am not a total bullshiter.

Why do you say that this is a common belief that used to be true, but is now no longer true?