Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)C
Posts
0
Comments
518
Joined
3 yr. ago

  • Lithium is literally named after stone. No one ever claimed it is rare.

    When an X deposit is found, it means that a place has been found where an unusual concentration of a material in an easy/cheap-to-extract form has been found.

    There are thousands of tons of gold in the ocean water. But no one would call the ocean a gold deposit. Because it would require a ton of effort/money to extract a tiny amount of gold from the ocean.

  • I can get to my house, and I can value it at 5 trillion €. That doesn't make it worth 5 trillion €.

    If an actual person/company that values things for a living, does an analysis on the value of my house, and it is valued by X€, then it is probably valued at X€. If someone says "pff just because they say so? I'll buy your house for 5€". Then a lot of people will come and say "5€? That's a steal, if you're gonna give it for such a low price, I'll get it for 6€", and it will probably go on until it reaches an amount very close to X€. If it ends up way below X€, the ones that did the analysis would probably want to buy it themselves, because they actually think they can make a lot of profit on that.

    I don't know why I have to explain this. This is very basic economics.

  • Not saying that named parameters are bad, but the builder pattern serves the same purpose and imo it's more ergonomic.

     
        
    TrainBuilder::new()
      .with_electric_motor(true)
      .with_width(1.0)
      .build()
    
      

    I don't care about the color of the train or the amount of wheels, I just want the default train with a few changed parameters.

    If you do named parameters in rust, you would need to set every parameter. The only way to not set every parameter is to give a special meaning to the Default trait. But that is uncommon to happen in rust. And many structs that could easily derive Default don't.

  • Again, those 2 are smaller than half the size of the random steel skyscraper I'm comparing it against. I could make a 1m tall sandcastle and claim sand is great at building castles. IDK if skyscraper has a formal definition, but I think you're missing the point.

    Something being cool does not make it objectively better. Of course, we don't have to do everything the same way. Maybe the builders of the buildings had unique constraints that made wood better than steel in their case. Or maybe they did so for artistic reasons, which they deemed worth the cost or not using steel. Or maybe they just put an arbitrary constraint of themselves of "we must use wood because we want to".

    Tall buildings made out of wood existing does not mean that it is a good default choice for building skyscrapers.

    Sure, you claim that there are actual skyscrapers planned/being developed. But I wonder what sacrifices, if any, they had to make.

    Maybe we have been using steel all this time because nobody ever thought of wood. But I find that unlikely.

  • I searched for "tallest wooden building" there actually is a list in wikipedia of the tallest buildings.

    The tallest of the list is not even a building, it's a radio tower. At ~110m.

    The closest city to me that has a skyscraper has a single skyscraper, and it is >150m tall.

    I would not build a skyscraper out of wood.

  • Easy, just say it is an emergency and continue anyway. That's how it works in the US

  • Wood is cheaper than steel. Which apparently is the most important way to be better in. But I wouldn't build a skyscraper out of it.

    Saying that energy density is not important in energy storage technology is as stupid as saying that material strength is not important in building materials.

  • I already quoted you. I don't need your permission to do it.

    If you're not gonna even try to defend your position you're just spreading misinformation.

  • In only a few years, most batteries will be made without lithium anyway.

    Citation needed.

  • I've considered this many times. But I just can't see a fair way to do this.

    You either compensate with money or with time. I would gladly pay 3x my commute monetary cost to just teleport there, so at least in my case time compensation would be much better. So how to do it?

    Option 1: Clock in when leaving the house, but that is incredibly easy to cheat.

    Option 2: Calculate once per employee the time it should take them to get there based on their transportation method. They can just claim to commute in a time-inefficient method (such as walking or cycling) when they go in car instead. What happens to people that don't always use the same method?

    Option 3: Reduce the work hours for everyone by the same amount. This is amazing, but you can do this without claiming it's for commute compensation. If you only do this reduction when not WFH, then you are basically punishing those who WFH and would have a short commute time. The ones on the top would just WFH 99% of the time from very far away and get massive commute compensations otherwise. Even then, the times they go to the office would be massively beneficial.

    For money, it's basically the same.

    I just don't think it can be done fairly.

  • Where's the research though?

  • I like to think that there are exactly as many clones as that one copy-paste that lists every one of them. That way it truly lists all of them.

  • Have you tried approaching men instead? That way you choose who to approach.

  • Depending on what you do, it will probably only be a few lines of rust. Most of the complexity would be in the DB setup and SQL queries. Since you'll probably use an HTTP server crate that will handle all of that for you.

    So, yes, it should be possible.

    Even if you don't intend to make it a UI project. You should still do a shitty UI. Otherwise you will spend more time testing it than actually developing it.

  • Lots of talk about the problems of implicit conversions. Which is known, and is the reason that rust does not have implicit conversions. But when it came to the heart of the article, the explanation of why unsigned is bad for sizes, it's just:

    • One example about wrapping in ring buffers.
    • Saying "in the 90s there were a lot of problems".
    • The lower boundary "0" being near "normal" numbers.

    I can see how you can think the 3rd one is an issue. But then the answer should be the java one of just removing unsigned. Since that issue is not exclusive to sizes, every unsigned use case has it.

    It seems like the real problem here is having implicit conversions.

  • If you fear both, and curl | sh is a red flag. Binary blob is also a red flag, if you fear them both equally.

    Has every software that runs in your computer been compiled by you?

  • If it's not open source or you are not compiling it:

    Why so much fear about the shell script but no fear from the executable?

    If it's open source and you are compiling it:

    If you don't fear the project because you (presumably) have read the source code and determined that it's fine, why fear a shell script that is most certainly simpler, and you can read it like the rest of the code?

  • No. That is because of the simplistic definition.

    If people have "too much" money, the demand of products will go up. Specially "luxury" products. As that is what people buy when they have "too much" money. Increasing demand increases prices, therefore, inflation.

    The same is true if the supply of "luxury" products decrease. For the same reasons.

    However, if inflation is due to an increase of "essential" goods' prices, it's trickier. That is because increasing essential prices won't result in a decline of their demand. They are essential, people will stop buying the things they don't need, not the ones they do. Therefore, the demand of "luxury" goods will fall.

    Only when people can't afford the essential goods will they stop buying them. Which probably would mean death/emigration. Only then will demand fall, because there's literally less people.

    When you tax, it's the same case. People have less money, so demand for "luxury" items will fall.

    So technically yes, it would reduce inflation, since there's probably some "luxury" goods in the basket you are using to measure inflation. But it won't actually reduce the price of essential goods, which is what most people would expect from a fall of inflation.

    Of course, some fall of demand for "luxury" goods could mean a fall in "essential" goods. For example, a fall in water-gun fights or golf-course watering would mean a fall in demand for water, which is an essential good. Economics is not a simple subject

  • Wtf is this?

    The most foreseeable event of the last 20 years.

    Massive out of this world investment + no demand = prices so cheap they were operating at a huge loss

    Operating at a huge loss + time = huge enshittification

    Raising prices is the easiest form of enshittification. Ads are coming too. Lastly it will be degrading features. Incorporating more features that no one wants, and bundling with other services that no one wants.