Bolt EV is around $27K and believe Nissan Leaf is also in the same price range. So, with taxes you are look at max $30K. If you qualify for the federal tax credit, then you should be able to get that well within your price range.
Bolt is discontinued and dealerships in my area don’t sell them for under $31k. Leaf also isn’t long for this world, is based on an ancient platform, and starts at $30k in my area. I don’t qualify for the tax credit.
Can anyone explain or shed more light on how the "remote hands" part the support would work in bare metal server scenario? Would they run commands you give (or) will they follow your runbook (or) something else (or) all of the above?
There are two types of remote hands: dumb and smart (under various names)
Most colocation facilities include dumb hands for free. Push a button, tell me what lights are on, plug in a monitor and tell me what it says, move the network cable from port 14 to 15, replace the drive with the spare sitting in the rack, etc.
Smart hands are billed around $100-$300/hr or a flat rate per task from a menu. Write an image to a USB stick and reinstall the OS on a server. Unrack and replace a switch. Figure out which drive has failed in the server and replace it. etc.
I've ran computers in datacenters for 20+ years and maybe used smart hands 1 or 2 times.
I haven't been following what's happening in crypto and was generally aware it was bad, but the last 3 months (that is how far I scrolled down) seems bad than I anticipated. The number of security issues, money stolen, and number of fraudulent cases is unbelievable. How are people still invested in this?
It was even worse before. MtGox failed in 2014 and it had an even bigger market share than FTX. Almost all the issues are related to centralized services and projects, not issues with the blockchain technology itself.
I am well aware of ODBC. Critically you cannot edit the database itself, only copy from it. This makes sense so as not to let some sales guy tank an entire company becuase he misspelled a formula. What I mean is a spreadsheet that literally runs on a database. It could even be sqlite, _anything_ that allows two way communication between the slreadsheet and the application.
spreadsheet gui <--> database <--> application
The spreadsheet does simple data manipulation and acts as a GUI
The database can be mysql, postgres, sqlite (even JSON...)
The application does batch processing, generates documents, sends emails ect. everything excel can't or shouldn't do.
This stack could solve, in my opinion, >50% of all business software.
I have also considered some sort of general data storage but it's too slow. Drop box et al are not made for anything close to real time communication, which is critical for a spreadsheet that needs to talk to a program. Something like 100ms at most. This would also presumably require a perfect .xlsx implementation to read and edit the data which doesn't exist to my knowledge.
Google sheets, maybe excel, can make http post and get requests. It’s trivial to write an api that can read/write to a database on behalf of the spreadsheet.
