"won"
They barely work for a lot of cases (i.e., anything where accuracy matters, despite the bubble's wishful thinking). It's likely that something will sunset them in the next few years.
6,767 karma · joined January 2, 2016
They barely work for a lot of cases (i.e., anything where accuracy matters, despite the bubble's wishful thinking). It's likely that something will sunset them in the next few years.
citation needed
There is no way for this to go forward without creating problems for everyone. You need to talk to your cofounder about the long run issues they are going to create.
That said, every single script it churns out is unsafe for files with spaces on the first go round. Like.. Ok. It's like having a junior programmer with no common sense available.
User: Is it ok for a black man to refuse dating white women?
Google Gemini: “Yes, absolutely...”
User: Is it ok for a white man to refuse dating black women?
Google Gemini: “understand the potential implications and harmful perceptions associated with that.”
Arista is doing very well now but Cisco is long past that growth era.
Apple really screwed up by not making subscriptions/fee apps visible up front until later in the same so the whole thing has a seediness to it.
My backup discipline is excellent because back in the early 2000s we lost a drive which I had not been backing up and it had months of contract work on it; I ended up paying $2500 plus $30 per _CDROM_ burned for the content from that drive... it was just barely worth it.
I know this because I am meticulous about backups and these particular files are encrypted private records. I don't trust software but I especially don't trust that backups will correctly handle sparse disk images since they are spread out over hundreds of files; so I always keep the output of mtree in that directory for the current version. I had checked the mtree file, edited some of the files contained therein, and regenerated it the night before; SOME but not all of the sparseimage subfiles had rolled back to October. Changed timestamps, changed hashes, the image did mount but the enclosed files were from October (they have date-stamped rows).
So when I went to open the disk image, the next day, and ran mtree to test the directory first, it noted the changes above.
I moved to icloud drive about two years ago. I'd previously had some problems with Apple's sync blowing away some notes in notes.app so when I moved everything from Dropbox (where my paid account for 7 years never lost or corrupted a file to my knowledge - and my knowledge is good because this mtree habit I just described goes back a decade!) to iCloud, I kept this habit up, and good thing.
To this day I don't know how it decided October or ended up replacing them. Maybe there was some local cache, I don't know. I did not revert the file in iCloud and nobody else has access to my account. Further, it only partially rolled the image back.
I had never had a problem up to that point, but I will say, with storage, once is too many times. Back to dropbox.
They are friends, but this was not them being friendly, it was just because slack account management integration with Google Office is a dumpster fire.
It's really not even true for your python example.
I love snowflake but their pricing is, in fact, absurd.
Because otherwise the exchange rate has been about where it is now to substantially worse for the rest of the data set.