@CoderSupreme The founder of StackOverflow went on to work on Discourse (https://discourse.org). There’s actually an ActivityPub plugin available nowadays, so apparently people can contribute from whatever fediverse server they’re coming from. For example see Go Bridge (https://forum.golangbridge.org) @programming
Perfect description. It also describes why I now love GoLang so much. “How has GoLang improved on this unholy tome or horrors?” “Well, it fits in my pocket now.”
The author’s primary gripe, IMHO, has legs: the question about the oven’s relationship to baking is buried as part of bake() and is weird. But the solution here is not the left-hand code, but rather to port some good, old-fashioned OOP patterns: dependency injection. Pass a reference to an Oven in createPizza() and the problem is solved. Doing so also addresses the other concern about whether an Oven should be a singleton (yes, that’s good for a reality-oriented contrived code sample) or manufactured new for each pizza (yes, that’s good for a cloud runtime where each shard/node/core will need to factory its own Oven). The logic for cloud-oven (maybe like ghost kitchens?) or singleton-oven is settled outside of the narrative frame of createPizza(). Again, the joy of dependency injection. To their other point, shouldn’t the internals of preheating be enclosed in the oven’s logic…why yes that’s probably the case as well. And so, for a second time, this code seems to recommend OOP. In Sandi Metz style OOP in Ruby (or pretty much any other OOP language) this would be beautiful and rational. Heck, if the question of to preheat or no is sufficiently complex, then that logic can itself be made a class. As I write, I thought: “How is golang so bad at abstraction?” I’m not sure that that is the case, but as a writer of engineering education, I think the examples chosen by the Google Testing Blog don’t serve well. Real-world examples work really well with OOP languages, fast execution and “systems thinking” examples work great with golang or C. Perhaps the real problem here is that the contrived example caters to showing off the strengths of OOP, but uses a procedural/imperative-style-loving language. Perhaps the Testing Blog folks assumed that everyone was on-board with the “small factored methods approach is best” as an article of faith and could accept the modeled domain as a hand wave to whatever idea it was they were presenting.
Golang is the defacto searchable term for the language. Even allowing for minimum length limitations in lemmy it makes sense to use the searchable name in any text you wish to be found. Consider how people search for answers to programming questions and how lemmy posts might be indexed.
I did the same! Wanted to learn golang, so I built a blog. Kept it simple and used other tech I knew already for the css and backend. Didn’t even enable uploads. This way, I learned go much faster than if I had learned it from scratch. The basics are good. But we’re not trying to be experts. We’re trying to have fun and build stuff.
Unquestionably Golang if those are the two options. It’ll give you a much better base to work with if you are still earlier in your career and is much more applicable to a lot of things. Elixir is niche, the syntax doesn’t share a lot of patterns with other languages, and no one is hiring for it. Also few people know it. I want to caveat my answer with that I personally really like elixir, and would prefer to work with it myself over golang for some types of problems. Actor patterns are really cool.
Comments
I think Golang had the potential to take over just because it’s so easy to pick up and start contributing. My last position was Golang focused and our hiring was never focused on experience with the language because we knew that if you understood programming concepts you would succeed in Golang. Today, I’m working on Rust and while I enjoy it for what I’m using it for (Systems level instead of Web Services) I’d be hesitant to suggest it for most backend application just due to the ramp up time for new developers. tl;Dr Golang will have an easier time hiring for because no language specific experience is required.
I get the sense that you might appreciate golang.
Lihat kiriman asli pada platform media sosial terkait.
Lihat kiriman asli pada platform media sosial terkait.
Comments
Lihat kiriman asli pada platform media sosial terkait.
Lihat kiriman asli pada platform media sosial terkait.
Lihat kiriman asli pada platform media sosial terkait.
Lihat kiriman asli pada platform media sosial terkait.
Comments
Lihat kiriman asli pada platform media sosial terkait.
Haskell (+5 years), Golang (1+ year), Elixir (1 year). A few hours after work. Yes. In all the languages I’ve listed before. Back end focused. 1 year, give or take. Stalin. Without question I don’t want to share it publicly to avoid crossing online entities.
Although why you would not like or want the latest stable or your app, for example, is beyond me. It’s a stable version, you should want the new features. Call me an old man. But I like when things are stable. I don’t like starting my computer, and the software was updated to a new version, and some features disappeared or changed in behavior. This is why I hate the web where people update software right under my nose! With no control from my side. These repo contains thousands of orphan packages which are not maintained and will never get any update ever again (proceed to show a list of obscure go modules) Have ever checked if you checked how maintained are the dependencies/libraries of your favorite software? It’s a nightmare as well. The distro is not making anything worse. You get the duplicated work of maintainers, packaging the same app, multiple times, for multiple supported version of the distro. First, the work is not often duplicated. The first maintainer to package will usually upstream patches which make packaging easy. Packagers will look how other distros packagers packaged the app they’re trying to package. Also the duplication only happen a few time. Ubuntu just pulled almost all of their packages from Debian Sid. Same with RHEL/CentOS and Fedora. And so on, and so on Also you’re overestimating how hard packaging is, most of the time, it’s scripted. (golang modules in debian, are imported in an almost fully automated way) You know what distros bring? Security. (My packages were vetted by packagers) Uniformity. (All my software works coherently) Stability. (My software doesn’t break at the will of some third party developer)