I strongly prefer my Linux machine but use Windows mostly so that I can run Quicken. I feel doubly trapped: can't get off Quicken and thus can't get off Windows.
I'm only very slightly less reluctant to get an Apple machine (though the M* chips tempt me) and there will probably be incompatibilities between the versions of Quicken.
I think I should probably rip off the band-aid and migrate to:
+ spreadsheets (more control/future proof)
+ gnucash or similar (and risk that going unmaintained)
+ Wine
+ something I've not considered
At my work we use quickbooks enterprise (which is a desktop app) for some clients and another (not Intuit) online/cloud app for other clients. I have extensive experience using both. The cloud apps are slow, buggy, lacking features, immature UI/UX, and not as open.
The principal limitation of qbe is lack of multi-location support. The main advantage of cloud is the ability to provide direct access (though the role/permission models I’ve experienced have other downsides).
It’s a mixed bag, but the advantages of qbe outweigh the aggravations of windows—for now.
IIUC the cloud solution provides cloud-based storage|copies of the quicken file and accessibility through a less-functional web-based tool and Simplifi isn't compatible.
So, thanks again for the suggestion but these solutions won't work for me.
Yeah, you're right. It is astonishing that Quicken's web app does not offer the same features and functionality as the desktop version. Having worked for many years as an SRE, I would have imagined that the opposite would be true - that Quicken would want to migrate its users to its online version, precisely so that customers could use the software from any client, be it Mac, Linux, WinBlows, or whatever.
I live in a community in the Pacific Northwest that was built in 2018 and (almost) every home (22/23) has (Carrier) heat pumps; for some unknown reason, the other has heated floors.
Many of us are proponents of heat pumps thanks to reduced costs and emissions *but* we've not had a generally good experience possibly (!) as a result of bad installation and definitely due to limited numbers of indoor heads (if I close my main bedroom door, the rest of my upper floor has no heating/cooling).
There's always someone in the community frustrated that their house is too cold/hot, that the condensation drains are blocked and water is running down an interior wall, that an indoor head or the condenser is having problems, or that there's unexplained coolant leak.
People moving into the community are inheriting issues with at least 2 homes having to augment/replace the system. To save breaking into the walls, this often necessitates putting the power, coolant and drainage lines on the outside of the house and then boxing the result.
We're saving money on monthly bills (probably; we don't have a comp) but many of us have spent quite some $$$ on maintenance and replacement equipment.
I've spent 1.5 years in a brand-new building with Mitsubishi heat pumps. It had some initial trouble with a faulty electronic component, but afterwards it worked quite fine, needing little if any attention.
Not only are my AI chats more personal than my Google searches but with these false friends reporting this information back to Google's (and others') advertising engines, suggests to me that this will become a more accurate, more difficult to avoid and thus bigger business for Google.
Each of those has tradeoffs compared to Dockerfiles (I have no need for bazel, but if I did, then adding `rules_oci` might be a win-win, rather than using a Dockerfile). If I used Nix, then the Nix dockerTools would be a huge win (I don't use Nix). If I were shipping Go programs, `ko` would likely be a good baseline.
Buildah is the only serious alternative in my opinion.
You lose automatic layer caching, but in exchange you can use the same tools (RUN, ADD, etc) within a much more powerful shell environment.
I wrote a Buildah wrapper that uses a shell script harness to polyfill the familiar Dockerfile syntax while adding several extra goodies - mainly the ability to bake runtime arguments (mounts, ports...) into the image. Very handy!
Buildah's ability to mount the container in an unshare environment is pretty magical for copying stuff in and out of it.
That said, in the end I'd still rather build containers with something other than an imperative sequence of commands, so my heart is going to be forever with nix2container and bazel's rules_oci.
Your insight is helpful almost as much as knowing that other people like me are out there too.
I think (!?) I've finally let go of a project that I've been working on for a couple of years.
A key tenet of the project (which I frequently forgot) was that it was a way for me to learn|refine technical skills and to keep me entertained|occupied.
The project certainly achieved those objectives for me and I'm a better person for doing it.
Good luck to you and I hope you continue to succeed!
I'm only very slightly less reluctant to get an Apple machine (though the M* chips tempt me) and there will probably be incompatibilities between the versions of Quicken.
I think I should probably rip off the band-aid and migrate to:
+ spreadsheets (more control/future proof) + gnucash or similar (and risk that going unmaintained) + Wine + something I've not considered