• 0 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle







  • yes, the web itself is dying with the centralisation of services on top of the blazing dumpster fire that is the current browser ecosystem. So many aspects of the first generation internet have been lost, even the basic concept of it being a massively distributed, hyperlinked collection of pages is just FAANG serving occasional content to break up the adverts. All wrapped up in their own delivery apps that can punish non-compliance with obscurity.









  • “Whatever opinion you may have of advertising as an economic model, it’s a powerful industry that’s not going to pack up and go away,” Holley said." … “We’ve been collaborating with Meta on this, because any successful mechanism will need to be actually useful to advertisers, and designing something that Mozilla and Meta are simultaneously happy with is a good indicator we’ve hit the mark,” Holley believes.

    Even if this is true, for Mozilla to take a position of capitulating to the ad companies and working with likes of meta to find what works for them is a sad day in the history of Mozilla. They need a new CEO who believes in a better internet. Until then, Firefox users might as well take the same position and move to a chromium based browser, where at least we get the speed and compatibility with web standards dictated by Google, if data mining and tracking is the only future left. What a sad state of affairs this is.


  • ramblingsteve@lemmy.worldtoGeneral Programming Discussion@lemmy.ml***
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    7 months ago

    It’s very complex with hyper visors and virtualization technology. I don’t fully understand it myself in terms of how resources are allocated across something like aws or azure, but take a look at openshift vs openstack maybe. Openshift is for deploying containers and openstack is virtual machines. Openshift is kubernetes with some customizations for enterprise. Openstack is same for vm’s.

    Instances are virtual machines which tend to host an operating system, and a container is lighter and only hosts an application where the code and dependencies are isolated from the underlying operating system it runs on. k8 is kubernetes, which is container orchestration. I think of virtual machines for jobs that scale vertically, while containers are suited to jobs that scale horizontally. But this isn’t necessarily true as kubernetes is starting to get slurm functionality using tools like sunk.

    For integrating these things it depends on the application. You can run services in either by exposing ports and interact through API end points that point at them, eg for frontend web app serving data from a database hosted on a server or a container via fastapi. But I’m no dev ops engineer and the field is very complicated. There are many discussions around building micro services (containers) vs monolith (vm). Many decisions depend on the project. Hopefully some actual dev ops engineers will chime in and correct all of the above! xD



  • You know you’re old when games you still play quite regularly turn up in retro reviews! The community master server is still pretty well populated, as are UT '99 servers. These games are still the pinnacle of their genre. No micro transactions, no DRM, no pay to win. Just you, your shock rifle, and as much amphetamine as your nerve endings will take. As the reviewer says, the level design and game mechanics are legendary at this point, and players of any ability can quickly get into a flow state that modern games can only dream of. These are fine wines in a world of cheap lager. New gamers should drink deep from the pc games of the 2000’s.