Yeah, it’s rare that 1P fails to recognise the website, I always get suspicious. Most of the time when it fails it’s on random crappily made niche websites anyway, for which I wouldn’t care if my credentials were stolen!
Actually, when I do get worried is when I have to login in an app with a credential I saved for the website. 1P doesn’t match the app automatically (understandably) and I’m always a little uncomfortable
I don’t think it’s obvious at all, not even in retrospect. People have historically been wildly underestimating how computing usage would evolve (“640KB of memory ought to be enough for anybody”), interfaces connected to the internet have indeed multiplied exponentially and it’s showing no sign of slowing down.
Interesting! I assumed it was one of these loaned-but-misspelled words from French (geôle, pronounced johl with a soft j). I wonder if there’s a common etymology between the French and Gaelic
I think the PP was mistaken when they attributed it to Gaelic. It does indeed come from an antecedent of geôle; probably the spelling comes from the Norman form whereas the pronunciation comes from more widespread French forms. In any case, it isn't a case of "loaned-but-misspelled"; English got most of these words from times before French had standard spellings or - as in this case - pronunciations. And once they became part of English, they were subject to the future developments of English as English words, no longer French. It's like saying "geôle" is just misspelt Latin "caveola".
> he took pictures of things that other photographers thought were uninteresting.
[…] who takes random street scene photos?
I could be wrong but I feel photographing the mundane is very common, something that’s discussed a whole lot in photography and probably one of the main things discussed and taught in photography courses.
Doesn’t mean it’s the majority of photos taken of course, and a lot of it probably stays uninteresting as art and as documentation, but it’s hardly a niche thing!
Even in painting, representing the mundane has been a big subject for hundreds of years (eg Lowry in modern times)
The missing piece, is that film was expensive, and few carried cameras around with them.
Unless you were on vacation, or going to a memorable event, it was rare for a person to have a camera on them in the 60s. They didn't easily fit in pocket. And rarer still for someone to spend a few bucks taking photos of unimportant things.
(Film and development costs both were not cheap in the 60s)
Most people only had 15 or 20 shots in their cheap camera, and wanted to save them for the party or event.
It's not like there were endless professional photographers wandering around.
This is literally the first time that I hear someone making any difference between “programmer” and “developer”. Hell I don’t even think I’ve ever heard a difference with “software engineer”, apart from countries where engineer is a protected title
I work in government and my position has been reclassified from computer programmer to software developer and software engineer over the past 20 years. Same workload and skillset. We're even supporting some of that same software written 20 years ago.
If you wanted to turn the cathedral of cologne into a mall you’d get a pretty strong reaction from _me_, who’s neither religious nor has ever been to Cologne!
Many companies run k8s for compute and use rds/sqs/redis outside of it. For example RDS is not just hosted PG, it has a whole bunch of features that don’t come out of the box (you do pay for it, I’m not giving an opinion as to whether it’s worth the price)
Anything stateful is not allowed inside the cluster. PVs are annoying enough without having to manage a DB bolted onto what was originally designed for stateless web services.
My db is my cluster. It's been stable for years but I'm afraid to touch it. There's a long outstanding issue in k8s that makes PVs harder to resize than it should be. And they're just more complicated.
Trying to move to managed MySQL now. It'll cost me a bunch more but at least I get a fail over node which I don't know how to set up myself... Still no master-master though, apparently that's not an option.
Actually resizing PVC depends on the CSI drive. Some support easy resizing, some require the volume to be detached. You can double check your CSI driver and might just need to patch your storage class.
Agreed running databases without operators that can handle replication, master promotion backups and PIT restore is super scary. Most of the modern operators support all of these operations.
Yea RDS makes your life easy, notifications and easy application of security patches both OS and DB level (minor version upgrades). Easy upgrade of major versions, easy upgrade of storage, RAM and compute (but not so easy to downgrade), easy options for replication, Blue/Green deployments etc to name a few.
> It allows for things like e.g. multiple image libraries to implement your interface without knowing it
That virtually never happens. Seriously, what would be the odds? It’s so much more usual to purposefully implement an interface (eg a small wrapper the writer thingy that has the expected interface) than to use something that happens to fit the expected interface by pure chance.
It’s not a structural vs nominal problem but other, typescript is structural but has the implements keyword so that the interface compliance is checked at declaration, not at the point of use. You don’t have to use it and it will work just like Go, but I found that in 99% of cases it’s what I want: the whole point of me writing this class is because I need an interface implementation, might as well enforce it at this point.
It happens all the time because e.g. third party developers follow the same patterns in the standard lib. And it was designed that way. Another example: logging libs are frequently quite similar. Even though the stdlib didn’t define that interface, you can still make your own that works for lots of libs. But even if you don’t use that part of it, it’s still great to limit the scope of your dependency. Less to mock, more flexible code. You obviously don’t like this and I’m not going to convince you, I think. But this is really one of the best features of Go.
This library (and some 3rd parties) have a lot of implementations of image types. But without any inheritence or interface declaration on their part I can make something that will do image size calculations by defining an interface that only contains
Bounds() Rectangle
Now, any of those types can be passed into my function to do checking.
Another example. The stdlib log package didn't define an interface (they should have) and the stdlib logger looks like this: https://pkg.go.dev/log
However, lots of people have made drop in replacements that implement the same method signature. By defining an interface you can swap in the stdlib logger or a 3rd party without the stdlib implementing that interface.
So yeah, the stdlib implemented the interface I defined in my code "by accident" and that's a great thing.
reply