Myself I already pre-provisioned a kubernetes cluster and it just makes new manifests and deploys there. Less dangerous, less things for it to fail at. The networking is already setup. The costs are known/fixed (unless you autoscale in the cloud). It's much faster to deploy.
Same same... i have prepared a sample config file with most of most common k8s object types as examples and just use that as a skill. I have given it access to my test cluster. I have configured my own container registry as well. Claude generates perfect deployment artifacts every single time. Works superbly well. I use k3s btw.
Im running like upwards of 30 difference services(mixed types) on a single 6$/m contabo instance lol ... such a pleasant ci/cd experience.. no messy webhooks or complicated scripts on integrations... just 2-3 hardcoded commands and plain old k8s config files.. love it.
both. local k8s (Rancher desktop) for devloop integration tests, remote k8s for running services. Helm chart to bootstrap cluster services like CRDs and Cloudflare tunnel.
Even if it's the same (faster horse?) I would rather use Rust for the fact it's development is not tied to a big tech company which could abandon it if they liked. Yes it could continue on as a fork but it's development velocity would suffer.
If we're going to be concerned about any language languishing due to a lack of support... like, I don't think people are going to put "Apple dropping support" as anywhere near their shortlist. Rust has a higher risk of losing support.
Apple was the primary and only major sponsor of Objective-C, used it as the core foundation of their entire platform, and dropped it like a stone with little warning or ceremony. Yes, being tied so closely to Apple is an existential risk for Swift. One need only look at the quality and trajectory of MacOS to see that Apple isn't a software company, let alone a company that cares about developer experience (Xcode, anyone?). As far as modern Apple is concerned, the primary benefit of Swift is that it produces a tiny bit extra lock-in for iOS apps, by making cross-platform development more difficult.
People still write applications in Objective-C (e.g., see Transmission [1]), and the language is still maintained to support the latest OS. If anything, Apple being the largest sponsor of Objective-C would suggest that you get greater vendor lock-in out of it than Swift, since you can at least use the latter outside of Apple platforms (e.g., on a server).
Although the only framework that was developed in Objective-C after Swift got introduced was Metal, anything else is mostly maintenance and incremental improvements.
"and dropped it like a stone with little warning or ceremony"
What?! This is complete nonsense. Swift was introduced 11 (!) years ago and it was clear from day one that it was going to be the future. Every single year since the introduction there were clear messages and hints in documentation and WWDC that Swift is in and Objective-C will _eventually_ be out.
Little warning? Maybe if you kept your eyes closed the past 11 years.
And do not forget that today you can still write apps in Objective-C.
Whether or not Apple still has legacy pieces in Objective-C or still allows you to write apps in it is not the issue. The point here is that Apple shadow-dropped Swift and shifted essentially all of its development priority away from Objective-C in a matter of months.
I'm old enough to remember when Objective-C was a real and thriving (if niche) language. I remember all the buzz when automatic reference counting was the next big thing, pushed heavily by Apple and taking center stage at WWDC. And since the year Swift came out, Objective-C has joined Cobol in the category of zombie languages: the living dead with plenty of entrenced codebases but with nothing to look forward to but a continued slide into technological irrelevance.
Rust of all languages, now that it's been majorly adopted by many companies big and small, has a higher risk of losing support over a language developed exclusively by one corporation? I sincerely doubt that.
> Swift is a high-level general-purpose, multi-paradigm, compiled programming language created by Chris Lattner in 2010 for Apple Inc. and maintained by the open-source community.
Swift being maintained by the open source community is an illusion. The community was very against function builders. Apple went ahead and did it anyway because they needed it for SwiftUI. The open source community just provides discussion, and Apple gets its way either way.
> The community was very against function builders.
Scanning the multiple review threads, that doesn't appear to be the case. According to the acceptance post, the community was overall positive about the feature but expressed concerns over the attribute naming, which was renamed in response.
I know Swift is technically not Apple specific, but it says right there in your quote that it was created for Apple and Apple is the giant weight behind it.
I doubt Apple is in danger of dropping Swift, but if they did it would create a devastating vacuum in the Swift ecosystem.
> I would rather use Rust for the fact it's development is not tied to a big tech company which could abandon it if they liked.
Go's development is tied to Google Inc. and is widely used at Google. Same with Microsoft's C# with .NET and Swift isn't very different to this as long as it is open source.
Go has a critical mass that Swift clearly doesn't (i.e. there are many, many companies who have net profits of >$1bn and write most of their server software in Go).
Additionally Google isn't selling Go as a product in the same way as Apple does Swift (and where Google does publish public Go APIs it also tends to use them in the same way as their users do, so the interests are more aligned)...
> Additionally Google isn't selling Go as a product in the same way as Apple does Swift
Hmm, Apple isn't selling Swift as a product either; it's literally what they needed for their own platform, much like how GOOG needed Go for their server works.
I have similar concerns about c# as I do about swift.
I'm less concerned about go, because unlike swift and c# it was designed from the beginning to be cross-platform and if anything Linux is the best supported OS. But barely so. Also, if Google were to discontinue support, or change the license, or do something else disruptive, I have more faith that the ecosystem would create a fork to continue the language.
FWIW, my biggest concern isn't that the language would be completely abandoned, it is that the company would diminish or drop support for tooling on OSes and editors and IDEs that compete with the company's products (Mac OS and Xcode for apple, Windows and Visual Studio for MS).
> I'm less concerned about go, because unlike swift and c# it was designed from the beginning to be cross-platform and if anything Linux is the best supported OS
No it wasn’t. There were so many foot guns for windows and in fact to this day you cant use CGO with MSVC (insane to me).
I can’t even say with a straight face today that Windows is the best supported OS for C#, because it’s not true
Microsoft’s market position is reliant on Linux and access to Linux development to keep Azure competitive. Cross-platform capabilities on the .Net VM are critical to compete with the JVM and associated databases. C# has been windows-first for a while, but the core cross-platform capabilities are not going to disappear, the tooling is all CLI based/capable now, the entanglements tend to be platform and service based.
That said, F# was years ahead of C# in features C# is still chasing, and is driven mostly by the open source community. That community is more in academic and finance areas where Linux-first is common. The language is standardized and plugged into VM improvements over time.
Frankly, I see the lesser degree of entanglement with MS corporate interests as a boon for the language and its ecosystems long-term utility.
From what I understand, LSP support for c# isn't very good, and is from third parties, not MS themselves, because they want you to us Visual Studio on Windows.
The problem is that it's closed source, and its license specifically prohibits its use with anything other than VSCode. Unfortunately, this is becoming the usual modus operandi for first-party Microsoft extensions for VSCode for all the talk about how they "love open source".
Objective-C had its own open source source implementations, along with a better cross-platform story than Swift has ever had, and yet Apple's abandonment still managed to reduce it to irrelevance.
IMHO your case for a moot point would be stronger if you also mentioned which company you feel is tied to Rust in the same way as the other languages you've mentioned.
It's not overlooked, it's highly discussed in the community. From which materials are best to avoid VOCs, to filtering, to how to position it in the house or outside.
it's overlooked precisely because the community is well aware of it yet classrooms routinely include many printers without taking any kind of precautions towards it. [0]
On the materials to avoid notion : none of them avoid going airborne. It shouldn't be a discussion of what to avoid, it should be a discussion of needed precautions and infrastructure.
You could not possibly compare Sydney and London, they are very different. London is a bustling diverse city, Sydney is a nice (big) town. Sydney is a great place, and London is far from perfect but they are not in the same conversation. They are different.
The Global Liveability Index is, essentially, highlighting the most middle of the road cities. London (as with New York) has huge disparities and that guarantees it will never rank well on the Global Liveability Index. The people who choose to live in London and love London (as with the people who choose to live in New York and love New York) do not choose it because it is average.
I have lived in London and Sydney and many other cities. I have fallen out of love with London. I would rather live in Sydney than London. I still cannot imagine ever describing Sydney as a better city than London. Just as I can't imagine describing Copenhagen better than London.
Healthcare in London is world class. A city is crowded. The weather is very average for Europe.
People from Sydney who move to London come to hate it, once the novelty wears off, just as they would with New York, because the Australian way of life is very different. Sydney is closer to island life than city life.
Even with London's ongoing decline due to the U.K's inexplicable self sabotage, it still has something to offer.
> People from Sydney who move to London come to hate it, once the novelty wears off, just as they would with New York
Just sharing a different perspective, I'm from Sydney and have lived in all 3 and don't agree with this generalisation. I know plenty of Sydney-raised people who've lived in London or New York for decades, love those places, and don't plan to move back to Sydney any time soon if at all.
> London has a special microclimate and pleasant weather
It is hard to reconcile this with having actually lived there. The only benefit to the weather in London is it rarely gets very cold. Other than that, it gets very dark winters, it’s rarely sunny, when it gets too hot it’s unbearable because nowhere has aircon, and it’s usually drizzling.
Yes I really wish people saying "X is the best place to live in the world" would add where else they have lived, otherwise their opinion is not very useful to me.
I'm fairly well travelled. Lived in Tokyo for a bit. There's no perfect city. London has the best combination of all attributes, for me.
Have you lived in London and Sydney both, or are you just reading numbers off of Google and "best city" lists? Sydney is boring and in the middle of nowhere.
I'm from Sydney and yes lived in London, Melb, Auckland and Hong Kong. My main recollection of London was narrow streets. I think we like being in the middle of nowhere (geography, nuke missile target, conflict), surrounded by ocean. It is true, it's the one downside, it takes a long time to fly anywhere else.
Fair enough. I think if you like to travel, go away for the weekend etc then Sydney is not on the list. London has cheap euro flights, hub airports etc. I'm sure the QOL is good in all of those places of course, nice place to raise a family etc.
What if you're already flying when they enter your vicinity. It's pretty easy to do in a city. Also they may not announce themselves until you're already violating or even after when they charge you
One more line of bullshit they can shamelessly trot out after they summarily execute someone. "The suspect approached the members of our protected class with a gun and a phone. Our brave and heroic gravy seals had a reasonable belief that the phone was being used to control a drone that had been following them all day, obstructing federal law enforcement from being able to operate in secret. The subject didn't obey the lawful order to shoot himself with his own gun, so our brave agents were forced to shoot him ten times in the back and send his family a bill for the bullets. We fully stand behind their actions helping keep us all safe from the woke"
(who am I kidding, even my fake statement is too coherent for this clown car of fascists)
Do not attribute to fascists/tin pot governments any concern over law/rulemaking with judicious consideration for minimizing blast radius or logistical/legal concerns for the populace. At this point, they are hardcore speed running the delegitinazation of the U.S. state in just about every practical sense.
reply