tom9729

It's a neat feature, but I'd be worried about it getting stuck and being unable to retract.

Later model years removed the ability to retract the screen on demand, due to backup-camera laws, and the 2021-ish refresh ditched the retractable display for an in-dash display similar to the 10th-gen Honda Civic (which amusingly, ditched the in-dash display in its 11th-gen for the previous A3 style).

This might be cheating but if you want a mostly screen-free recent Audi your best bet is probably the TT (or its big brother the R8 :-), the only screen is the entire gauge cluster and it's certainly not a touch screen.

Just do _not_ get a modern VW with its touch sensitive steering wheel controls...

Anything that depends on Safedisc is also screwed because Microsoft pulled the driver for security reasons. This includes a lot of first-party stuff like Mechwarrior 4 and Freelancer. Really wish they would put those up on GOG!

The data stores are pluggable. Postgres (with PostGIS) is one option.

The space wasn't necessary previously, and pasting code DID work, and then an update silently broke it and it's been like that ever since. Now you're supposed to use the formatting toolbar to insert a snippet. What a joke!

Teiid can also be deployed as a standalone server (see the Wildfly route). There is a JDBC driver to connect to it, and they emulate the Postgres wire protocol so you can even use psql to connect to it and run queries.

It's possible with all of the languages. Perhaps static analysis is just difficult with Python?

Or just write down the latest commit (or use git reflog to find it post facto) and if you mess up, do "git reset --hard <commit>" to get back to it.

It wouldn't have to be a new DVCS. It could be a Rust implementation of Git. e.g. Java Git implementation (JGit) used by Eclipse, Gerrit, etc.

It's unfortunate that people are down-voting instead of responding to you. I'm far from an expert but it would be interesting to see what other people think here...

Basic auth is insecure (i.e. sending credentials in plaintext) and poorly supported by browsers. For example how would you handle these scenarios:

  - Force users to reauthenticate after a certain period of time.
  - Allow user to logout without closing their browser.

I think Basic auth is more reasonable for server-server communications, combined with HTTPS and client-certs.

The best setup IMO is to have an HTTPS login page (form auth, hopefully with MFA) and use a session cookie. You can do server-side settings with this setup, you minimize the time when credentials are being sent (basically just once on login), and you can force your users to occasionally reauthenticate (either session timeout or manual logout) just in case they forgot to logout of a public computer.

For testing you could allow basic auth (make it configurable, or use user-agent sniffing to force browsers to use form auth).

Edit: formatting

Managers find a way. They will just use (or invent) another tool that lets them do it how they want. Now you have two tools, and some poor schmuck (or the developers) will get stuck with the job of keeping them in sync.