Yes we use proxmox qemu kvm with own own code for what doesn't come out of the box. qemu kvm is just as good as anything out there. Proxmox comes with a lot already included and you can run it for free and get updates for free if you enable the dev repository for proxmox packages while the bare metal host is mostly debian running with an optimized proxmox kernel.

As a UK Boomer, let me say "We already wanted Starmer out". Now the young ones have good reason to do the job.

You know that as orbits decay the satellites move to lower orbits, right?

Starlink operational orbits are (slightly) higher than the ISS orbit. If they stop being operational, they will move through successively decreasing orbital altitudes, including orbits that intersect the ISS orbit. (But note that "intersecting the ISS orbit" does not necessarily mean "intersecting the ISS".)

Deliberate antisatellite destruction is something we reasonably ought to worry about, but it is not the same thing as Kessler syndrome.

Wow, I've never heard anybody suggest this. Deflation is almost never discussed; it's hard to consider it "overhyped" when nobody thinks about it at all.

There's a reason nobody cares about it these days: deflation simply isn't a problem with government-issued fiat currency. If there's not enough currency in circulation, just print more, problem solved. There are many problems that you can't solve by simply printing more money (or, more accurately, problems of which if you try to solve them by printing more money you create worse difficulties), but deflation is the one case where it works, and as a result, deflation just doesn't happen any more.

I'm afraid the rest of your comments don't address money supply, so they're not really relevant to a discussion of inflation and deflation. Remember, currency is not value in and of itself. It is a medium of exchange. If there's too much currency, the currency loses value, and it becomes useless as a medium of exchange: that's inflation (and, in its worst form, hyperinflation. If there's too little currency, however, the currency becomes overvalued, and stops flowing because people hold it rather than spend it. That only happens in a system in which currency can't be added to the system, but if you have such a system, it fails.

In fact, the government has to print more money if there is economic growth. Ideally, the money supply would grow exactly as the economy grows.*

*Unless the velocity of money changes.

I agree with your points completely, but just as a pedantic note, when the value of a currency increases, this is deflation, not inflation. Inflation is when the price of goods, measured in currency, increases. So if the price of currency goes up, that's negative: deflation.

Deflation turns out to be actually very bad, because it means people would rather hold currency than spend it, and that kills the economy. Fortunately, the deflation of bitcoin doesn't kill the economy because people simply use other things as currency.

(William Jennings Bryan's famous "Cross of Gold" speech of 1896 was in some ways about deflation: the supply of gold, which underlaid the dollar back in 1896, couldn't keep up with the growth of the economy, and the fact that the currency was increasing in value was killing farmers.)

True but running anything with an http interface will almost always use the javax.http.servlet package for example.

Just for fun, here is a challenge, find me a java 8 enterprise application which doesn't use at least one of these package:

javax.accessibility
Defines a contract between user-interface components and an assistive technology that provides access to those components.
javax.activation
javax.activity
Contains Activity service related exceptions thrown by the ORB machinery during unmarshalling.
javax.annotation
javax.annotation.processing
Facilities for declaring annotation processors and for allowing annotation processors to communicate with an annotation processing tool environment.
javax.crypto
Provides the classes and interfaces for cryptographic operations.
javax.crypto.interfaces
Provides interfaces for Diffie-Hellman keys as defined in RSA Laboratories' PKCS #3.
javax.crypto.spec
Provides classes and interfaces for key specifications and algorithm parameter specifications.
javax.imageio
The main package of the Java Image I/O API.
javax.imageio.event
A package of the Java Image I/O API dealing with synchronous notification of events during the reading and writing of images.
javax.imageio.metadata
A package of the Java Image I/O API dealing with reading and writing metadata.
javax.imageio.plugins.bmp
Package containing the public classes used by the built-in BMP plug-in.
javax.imageio.plugins.jpeg
Classes supporting the built-in JPEG plug-in.
javax.imageio.spi
A package of the Java Image I/O API containing the plug-in interfaces for readers, writers, transcoders, and streams, and a runtime registry.
javax.imageio.stream
A package of the Java Image I/O API dealing with low-level I/O from files and streams.
javax.jws
javax.jws.soap
javax.lang.model
Classes and hierarchies of packages used to model the Java programming language.
javax.lang.model.element
Interfaces used to model elements of the Java programming language.
javax.lang.model.type
Interfaces used to model Java programming language types.
javax.lang.model.util
Utilities to assist in the processing of program elements and types.
javax.management
Provides the core classes for the Java Management Extensions.
javax.management.loading
Provides the classes which implement advanced dynamic loading.
javax.management.modelmbean
Provides the definition of the ModelMBean classes.
javax.management.monitor
Provides the definition of the monitor classes.
javax.management.openmbean
Provides the open data types and Open MBean descriptor classes.
javax.management.relation
Provides the definition of the Relation Service.
javax.management.remote
Interfaces for remote access to JMX MBean servers.
javax.management.remote.rmi
The RMI connector is a connector for the JMX Remote API that uses RMI to transmit client requests to a remote MBean server.
javax.management.timer
Provides the definition of the Timer MBean.
javax.naming
Provides the classes and interfaces for accessing naming services.
javax.naming.directory
Extends the javax.naming package to provide functionality for accessing directory services.
javax.naming.event
Provides support for event notification when accessing naming and directory services.
javax.naming.ldap
Provides support for LDAPv3 extended operations and controls.
javax.naming.spi
javax.net
Provides classes for networking applications.
javax.net.ssl
Provides classes for the secure socket package.
javax.print
Provides the principal classes and interfaces for the JavaTM Print Service API.
javax.print.attribute
Provides classes and interfaces that describe the types of JavaTM Print Service attributes and how they can be collected into attribute sets.
javax.print.attribute.standard
Package javax.print.attribute.standard contains classes for specific printing attributes.
javax.print.event
Package javax.print.event contains event classes and listener interfaces.
javax.rmi
Contains user APIs for RMI-IIOP.
javax.rmi.CORBA
Contains portability APIs for RMI-IIOP.
javax.rmi.ssl
Provides implementations of RMIClientSocketFactory and RMIServerSocketFactory over the Secure Sockets Layer (SSL) or Transport Layer Security (TLS) protocols.
javax.script
The scripting API consists of interfaces and classes that define Java TM Scripting Engines and provides a framework for their use in Java applications.
javax.security.auth
This package provides a framework for authentication and authorization.
javax.security.auth.callback
This package provides the classes necessary for services to interact with applications in order to retrieve information (authentication data including usernames or passwords, for example) or to display information (error and warning messages, for example).
javax.security.auth.kerberos
This package contains utility classes related to the Kerberos network authentication protocol.
javax.security.auth.login
This package provides a pluggable authentication framework.
javax.security.auth.spi
This package provides the interface to be used for implementing pluggable authentication modules.
javax.security.auth.x500
This package contains the classes that should be used to store X500 Principal and X500 Private Credentials in a Subject.
javax.security.cert
Provides classes for public key certificates.
javax.security.sasl
Contains class and interfaces for supporting SASL.
javax.sound.midi
Provides interfaces and classes for I/O, sequencing, and synthesis of MIDI (Musical Instrument Digital Interface) data.
javax.sound.midi.spi
Supplies interfaces for service providers to implement when offering new MIDI devices, MIDI file readers and writers, or sound bank readers.
javax.sound.sampled
Provides interfaces and classes for capture, processing, and playback of sampled audio data.
javax.sound.sampled.spi
Supplies abstract classes for service providers to subclass when offering new audio devices, sound file readers and writers, or audio format converters.
javax.sql
Provides the API for server side data source access and processing from the JavaTM programming language.
javax.sql.rowset
Standard interfaces and base classes for JDBC RowSet implementations.
javax.sql.rowset.serial
Provides utility classes to allow serializable mappings between SQL types and data types in the Java programming language.
javax.sql.rowset.spi
The standard classes and interfaces that a third party vendor has to use in its implementation of a synchronization provider.
javax.swing
Provides a set of "lightweight" (all-Java language) components that, to the maximum degree possible, work the same on all platforms.
javax.swing.border
Provides classes and interface for drawing specialized borders around a Swing component.
javax.swing.colorchooser
Contains classes and interfaces used by the JColorChooser component.
javax.swing.event
Provides for events fired by Swing components.
javax.swing.filechooser
Contains classes and interfaces used by the JFileChooser component.
javax.swing.plaf
Provides one interface and many abstract classes that Swing uses to provide its pluggable look-and-feel capabilities.
javax.swing.plaf.basic
Provides user interface objects built according to the Basic look and feel.
javax.swing.plaf.metal
Provides user interface objects built according to the Java look and feel (once codenamed Metal), which is the default look and feel.
javax.swing.plaf.multi
Provides user interface objects that combine two or more look and feels.
javax.swing.plaf.nimbus
Provides user interface objects built according to the cross-platform Nimbus look and feel.
javax.swing.plaf.synth
Synth is a skinnable look and feel in which all painting is delegated.
javax.swing.table
Provides classes and interfaces for dealing with javax.swing.JTable.
javax.swing.text
Provides classes and interfaces that deal with editable and noneditable text components.
javax.swing.text.html
Provides the class HTMLEditorKit and supporting classes for creating HTML text editors.
javax.swing.text.html.parser
Provides the default HTML parser, along with support classes.
javax.swing.text.rtf
Provides a class (RTFEditorKit) for creating Rich-Text-Format text editors.
javax.swing.tree
Provides classes and interfaces for dealing with javax.swing.JTree.
javax.swing.undo
Allows developers to provide support for undo/redo in applications such as text editors.
javax.tools
Provides interfaces for tools which can be invoked from a program, for example, compilers.
javax.transaction
Contains three exceptions thrown by the ORB machinery during unmarshalling.
javax.transaction.xa
Provides the API that defines the contract between the transaction manager and the resource manager, which allows the transaction manager to enlist and delist resource objects (supplied by the resource manager driver) in JTA transactions.
javax.xml
javax.xml.bind
Provides a runtime binding framework for client applications including unmarshalling, marshalling, and validation capabilities.
javax.xml.bind.annotation
Defines annotations for customizing Java program elements to XML Schema mapping.
javax.xml.bind.annotation.adapters
XmlAdapter and its spec-defined sub-classes to allow arbitrary Java classes to be used with JAXB.
javax.xml.bind.attachment
This package is implemented by a MIME-based package processor that enables the interpretation and creation of optimized binary data within an MIME-based package format.
javax.xml.bind.helpers
JAXB Provider Use Only: Provides partial default implementations for some of the javax.xml.bind interfaces.
javax.xml.bind.util
Useful client utility classes.
javax.xml.crypto
Common classes for XML cryptography.
javax.xml.crypto.dom
DOM-specific classes for the javax.xml.crypto package.
javax.xml.crypto.dsig
Classes for generating and validating XML digital signatures.
javax.xml.crypto.dsig.dom
DOM-specific classes for the javax.xml.crypto.dsig package.
javax.xml.crypto.dsig.keyinfo
Classes for parsing and processing KeyInfo elements and structures.
javax.xml.crypto.dsig.spec
Parameter classes for XML digital signatures.
javax.xml.datatype
XML/Java Type Mappings.
javax.xml.namespace
XML Namespace processing.
javax.xml.parsers
Provides classes allowing the processing of XML documents.
javax.xml.soap
Provides the API for creating and building SOAP messages.
javax.xml.stream
javax.xml.stream.events
javax.xml.stream.util
javax.xml.transform
This package defines the generic APIs for processing transformation instructions, and performing a transformation from source to result.
javax.xml.transform.dom
This package implements DOM-specific transformation APIs.
javax.xml.transform.sax
This package implements SAX2-specific transformation APIs.
javax.xml.transform.stax
Provides for StAX-specific transformation APIs.
javax.xml.transform.stream
This package implements stream- and URI- specific transformation APIs.
javax.xml.validation
This package provides an API for validation of XML documents.
javax.xml.ws
This package contains the core JAX-WS APIs.
javax.xml.ws.handler
This package defines APIs for message handlers.
javax.xml.ws.handler.soap
This package defines APIs for SOAP message handlers.
javax.xml.ws.http
This package defines APIs specific to the HTTP binding.
javax.xml.ws.soap
This package defines APIs specific to the SOAP binding.
javax.xml.ws.spi
This package defines SPIs for JAX-WS.
javax.xml.ws.spi.http
Provides HTTP SPI that is used for portable deployment of JAX-WS web services in containers(for e.g.
javax.xml.ws.wsaddressing
This package defines APIs related to WS-Addressing.
javax.xml.xpath
This package provides an object-model neutral API for the evaluation of XPath expressions and access to the evaluation environment.

Not true anymore, this was very through from java 1 to java 8 although.

No, you will almost need refactoring in 95% of cases. I spent quite a bit of time on that.

Sun stopped supporting and providing the javax.* packages and they've been replaced by the jakarta.* packages. Java finally started to remove deprecated packages, classes and methods after java 8 so refactoring is not only a matter of renaming the imports. You will also need to upgrade most of the external libraries you use for that reason and they have their own specific changes too.

The key sentence in the summary: ""Neither campaign appears to have gained much authentic engagement."

So, the reason so many people hate AI data centers is not because of this AI influence campaign.

I love the idea of p-11B fusion, but do keep in mind that a Boron nucleus has five times the charge of a hydrogen (including tritium) nucleus, and hence five times the ignition barrier.

D-T fusion is hard. p-11B fusion is harder.

Also radioactive everything else, since fusion produces copious amounts of neutrons, and the neutrons will activate pretty much everything the reactor vessel is made of.

The EM drive was the wish-fulfilment gadget of the moment a decade ago. Martin Tajmar's meticulous testing pretty well showed the purported thrust as being false positives, and I don't see people talking about them anymore (although there are always some impossible-to-convince holdouts, I guess), but mostly the people pushing such things have moved on to other magical gadgets.

Not sure what you're referring to here; Jimmy Carter most definitely did push for and invest in solar. Pretty much all of the solar array technology we see today is the outgrowth of the Energy Research and Development Administration (ERDA)'s research program of the late '70s and '80s. Most particularly the Large Silicon Solar Array (LSSA; later Low Cost Solar Array, LSA, and then changed to the Flat Plate Solar Array, FPSA) initiative pushed the movement of research from single cell development to production lines to actual large fields of arrays.

Spin up a LIVE based VM, with one of the more secure browsers. Then when you're done, all the cookies are poof ... gone.

This bypasses almost all forms of tracking/fingerprinting browsing systems.

Also, why can't hackers figure out how to poison cookies?