• 1 Post
  • 97 Comments
Joined 1 year ago
cake
Cake day: August 3rd, 2023

help-circle







  • I got something stupid like a 96 on the ASVAB and I just told the first air force guy I smoked a lot of weed and I never heard from any military again lmao

    It was tempting when they offered me to go right into a program to become a satellite operator starting off making $125k/year immediately after boot camp… but I don’t regret not taking that offer. Who knows what would have actually materialized, anyways. Probably would have been 6 years deep dreaming of hopefully seeing 6 figures one day while I end up managing logistics or something.



  • I never said this was a bad value, but I think we all know that these prices will not remain. They will increase because people will pay it once they are locked in. And if someone buys a used car, they have to pay that subscription to get these features, ensuring the manufacturer gets a slice from used sales. I can understand the cost, but it sets a dangerous precedent. It should be one time fee that grants the VIN access to the severs permanently. What would be really nice is if we had legislation that requires companies with a certain amount of revenue to maintain services for older products so they can’t just pull the plug later anyways.







  • Kind of. With hoisting, the compiler/interpreter will find variable declarations and execute them before executing the rest of the code. Hoisting leaves the variables as undefined until the code assigning the value to the variable is executed. Hoisting does not initialize the variables.

    For example:

    console.log(foo);
    var foo;
    //Expected output: console logs ‘null’

    foo = ‘bar’;
    console.log(foo);
    var foo;
    //Expected output: console logs ‘bar’

    console.log(foo === undefined);
    var foo;
    //Expected output: console logs ‘true’

    This means you can essentially write your code with variable declarations at the end, but it will still be executed as though the declarations were at the beginning. Your initializations and value assignments will still be executed as normal.

    This is a feature that you should probably avoid because I honestly cannot think of any good use case for it that won’t end up causing confusion, but it is important to understand that every variable within your scope will be declared at the beginning of execution regardless of where it is written within your code.



  • You may know the difference between a DAC and Amp, but you clearly don’t understand what I’m trying to say. I’m saying that a DAC doesn’t have its own power output. It literally takes a digital signal, and converts it to analog. In order for it to add any power to the signal, it needs to include an amplifier. Otherwise, the signal will always be a little bit weaker due to the power loss from traveling through the DAC. Most DAC units have at least a weak amplifier for this reason, but there are some units that are just a DAC. And the Amp part isn’t going to be controlling the digital volume, i.e. changing the system volume on your device. It will operate on its own volume control, so regardless of how limited the output is from your phone, it will still be made louder as it amplifies the volume independently of the phone. A unit that is just a DAC doesn’t have any way to amplify the signal it receives, so it will never be able to make it louder.

    You said explicitly that the android system will limit the output of any DAC, but that is wrong on multiple counts. The android system will not limit the output of a DAC because a DAC itself just 1:1 outputs an analog signal converted from a digital source so there is nothing to limit. The android system will also not limit the output from an Amplifier because it literally is not capable of that. That’s like saying your water faucet can limit how hot your water can get when you boil it on the stove. An Amp increases the power of the signal after it has already left the phone.