• 0 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • Your goal as a company is not to sell as many, but to make the greatest profit. So let’s say that the new market price is $3 000.

    You’re the new company. Your supply is 20 000.

    Do you

    a) Sell fridges @ $2 950/each, undercutting competition while selling whole supply, because of demand being higher than your supply, making $59 000 000?

    or

    b) Sell fridges at a reasonable price of $400, selling the same amount, because your supply is limited anyway, making $8 000 000?

    The company still has no incentive to go B route. They only need to undercut the competition, not make prices reasonable.

    Free market self regulates, provided nothing artificially screws with supply and demand and there are competitors. Both scalping and price fixing screws with it. It is literally the cancer of free market, and people screwing with it call themselves “investors”, while actually destroying the economy.

    It is the government’s responsibility to prevent those situations before they happen, otherwise these changes may be irreversible.

    Btw. A situation like this was happening recently in the GPU market. Nvidia had a crazy high demand for their GPUs because companies invested in AI were going to buy these cards no matter the price. So they bumped the prices like crazy, and they were instantly sold out.

    Meanwhile Nvidia’s competitor - AMD - didn’t have nearly as strong GPUs for Ai as Nvidia. Do you think AMD’s prices stayed the same? Nope. They bumped it just like Nvidia, barely undercutting them, because there was still demand, in fact growing demand, for GPUs for gaming, while AMD’s supply was obviously limited.

    2 years later, lower demand, GPUs actually in stock, but prices are still fucked (though not as much) because people got used to it.


  • It’s free market exploitation. If you believe a free market can exist without regulations, you’re imbecile.

    Just imagine: People need fridges. All fridge manufacturers agree to raise prices of a fridge by 2000%. So what, people are going to stop buying fridges? No - because they need them.

    You would say: it’s a free market, some new manufacturer is going to offer fridges at regular prices. Well - no you dumb fuck. What’s the incentive for the new fridge manufacturer to sell at lower prices, when people are going to buy fridges anyway, because they need them? The answer is - none. It would be a dumb business decision, because your supply is limited, and you’re going to sell it at market price, because that item is essential.

    So how does the economy even work if that’s possible? That’s right idiot - because it’s price fixing and it’s fucking illegal.




  • gornius@lemmy.worldtoSelfhosted@lemmy.worldShould I move to Docker?
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    1
    ·
    7 months ago

    Learn it first.

    I almost exclusively use it with my own Dockerfiles, which gives me the same flexibility I would have by just using VM, with all the benefits of being containerized and reproducible. The exceptions are images of utility stuff, like databases, reverse proxy (I use caddy btw) etc.

    Without docker, hosting everything was a mess. After a month I would forget about important things I did, and if I had to do that again, I would need to basically relearn what I found out then.

    If you write a Dockerfile, every configuration you did is either reflected by the bash command or adding files from the project directory to the image. You can just look at the Dockerfile and see all the configurations made to base Debian image.

    Additionally with docker-compose you can use multiple containers per project with proper networking and DNS resolution between containers by their service names. Quite useful if your project sets up a few different services that communicate with each other.

    Thanks to that it’s trivial to host multiple projects using for example different PHP versions for each of them.

    And I haven’t even mentioned yet the best thing about docker - if you’re a developer, you can be sure that the app will run exactly the same on your machine and on the server. You can have development versions of images that extend the production image by using Dockerfile stages. You can develop a dev version with full debug/tooling support and then use a clean prod image on the server.




  • gornius@lemmy.worldtoProgrammer Humor@lemmy.ml***
    link
    fedilink
    arrow-up
    67
    arrow-down
    1
    ·
    7 months ago

    Framework has multiple config files, allowing you to customize almost every aspect of it.

    Nooo, this is too much config files, they take up too much space in my project tree.

    Framework is a monolith with a single file to configure it.

    Nooo, the file is unreadable and developing extensions for it is annoying.

    Framework is minimal

    Nooo, it doesn’t have any useful built-in features.

    Framework is a complete solution without too many things to configure.

    Nooo, it doesn’t allow me to do what I want.






  • gornius@lemmy.worldtoProgrammer Humor@lemmy.mlPHP is dead?
    link
    fedilink
    arrow-up
    11
    arrow-down
    1
    ·
    8 months ago

    The language itself is not that bad. Especially the newest releases are really great, thought out DX improvements. What stinks are its legacy parts and how it needs to be run.

    My biggest pain is that for it to actually behave like it should it requires some sort of an actual web server like apache or nginx.

    Also, servers written in are actually request handlers - every time a request comes, the whole app is reinitialized, because it just can’t hold its state in memory. In many apps every request means reinitializing connection with database. If you want to keep some state, you have to use some caching mechanism like redis or memcached.

    Also had one time when Symfony app was crashing, because someone forgot to close class braces, and everything was “working” until some part of code didn’t like it and was just dying without any error.

    And one time when someone put two endlines after php closing tag at the end of the file, confusing the entire php interpreter into skipping some lines of code - also without warning, and only in specific php version.


  • The main argument to use password managers to prevent password leaks to all of your services (that you use with the same login/email). You can’t trust any service to store your password securely, therefore you should use different ones everywhere.

    Using a password manager gives you the convenience of using one, strong password that’s being used very securely, and mitigating risk of password leaks spreading further.

    If you abstract it that way, it by no means eliminates the risk of someone breaking into your database, but makes it harder and from a single entry point, instead of any service that uses your password.

    Plus many of those password managers give you an option to use YubiKey for additional security.

    Oh and also you won’t ever need to press “forgot password” ever again due to the arbitrary requirements that your password doesn’t pass, so you modify it slightly so it would.




  • Lockfile contains exact state of the npm-managed code, making it reproducible exactly the same every time.

    For example without lockfile in your package.json you can have version 5.2.x. In your working directory, you use 5.2.1, however on repo, 5.2.2 has appeared, matching your criteria. Now let’s say a new bug appeared in 5.2.2.

    Now you have mismatched vendor code, that can make your code behave differently on your machine, and your coworker’s machine, making you hunt for bug that wasn’t even on your side.

    Lockfile prevents that by saving an actual state of vendor code.