For me it has been the same except replace java with c#, I can argue that golang might soon be admitted into the “serious backend language club”. For how much crap people give java and c# they are languages you can get shit done in, fast , efficiently and stable.
I just found out some softwares around infrastructures also uses CLA, including: Kubernetes (hosted by CNCF) Istio (hosted by CNCF) Grafana All projects under Apache Software Foundation (e.g. HTTP server) OpenStack (hosted by OpenInfra) To my surprise, even Golang core uses CLA too. EDIT: Add more to the list EDIT 2: Envoy Proxy also hosted by CNCF uses DCO instead of CLA. Interesting. It looks like very difficult to bulid an infra without some components uses CLA.
r/homeassistant r/houseplants r/ebikes r/surfing r/golang
Microsoft has done some pretty shitty things before, like buying and extinguishing many competitors. But it’s pretty telling that you are NOT an experienced dev if you are criticizing the one thing MS has done really well. .NET is a rather mature framework with multiple seasoned languages under its umbrella. Having used C# and .NET for many years, it’s easily one of Microsofts best decisions they have made. C# is arguably one of the most dev-friendly languages on the market right now. With each iteration offering many quality-of-life improvements, I can’t think of many languages that offer the amount of improvements that C# has had over the last 10 years. Compare that to seasoned languages like PHP, Golang or even Java and I think C# is still the easiest to use in terms of terse (but still understandable) syntax, generics, data structure improvements, general iterators syntax and can’t forget LINQ improvements. I’ve often felt left behind when using Java, as it plays keep-up with some of the changes in C#.
Almost everything is easier than rust, except stuff like Elixir or Assembly and stuff… But rust is just better than the others. Golang is also decent, it’s fast (half the speed of rust is still very fast) and much easier to learn.
An interesting idea but it’s not possible with all languages. E.g. golang. But probably not the case with worlds adrift. I’m guessing it’s more of an incentive problem for the other company. No more revenue = why bother?
Hey, I’m learning Golang too! I’m gonna check this out. Really cool idea.
Go as a backend language isn’t super unusual, there’s at least one other project (https://borgo-lang.github.io) which chosen it. And there are many languages which compile to JavaScript or C, but Go strikes a balance between being faster than JavaScript but having memory management vs. C. I don’t think panics revealing the Go backend are much of an issue, because true “panics” that aren’t handled by the language itself are always bad. If you compile to LLVM, you must implement your own debug symbols to get nice-looking stack traces and line-by-line debugging like C and Rust, otherwise debugging is impossible and crashes show you raw assembly. Even in Java or JavaScript, core dumps are hard to debug, ugly, and leak internal details; the reason these languages have nice exceptions, is because they implement exceptions and detect errors on their own before they become “panics”, so that when a program crashes in java (like tries to dereference null) it doesn’t crash the JVM. Golang’s backtrace will probably be much nicer than the default of C or LLVM, and you may be able to implement a system like Java which catches most errors and gives your own stacktrace beforehand. Elm’s kernel controversy is also something completely different. The problem with Elm is that the language maintainers explicitly prevented people from writing FFI to/from JavaScript except in the maintainers’ own packages, after allowing this feature for a while, so many old packages broke and were unfixable. And there were more issues: the language itself was very limited (meaning JS FFI was essential) and the maintainers’ responses were concerning (see “Why I’m leaving Elm”). Even Rust has features that are only accessible to the standard library and compiler (“nightly”), but they have a mechanism to let you use them if you really want, and none of them are essential like Elm-to-JS FFI, so most people don’t care. Basically, as long as you don’t become very popular and make a massively inconvenient, backwards-incompatible change for purely design reasons, you won’t have this issue: it’s not even “you have to implement Go FFI”, not even “if you do implement Go FFI, don’t restrict it to your own code”, it’s “don’t implement Go FFI and allow it everywhere, become very popular, then suddenly restrict it to your own code with no decent alternatives”.
is the fact that people can with effort and error figure out how to do something a reason not to make it easier for them to do? I mean you can in theory write multi-threaded bug-free C code – just read the docs and the specs and the source of your libs and never ever do something that seems to work but is subtly fatally incorrect and yet we still have golang and rust and many other options to do things more safely and easily if someone wants to use Linux but doesn’t want to memorize the Hundred Mandatory Commands and Thousand Flags lest they accidentally cat > /dev/sda, why shouldn’t there be a system for them?
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.
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.
Lihat kiriman asli pada platform media sosial terkait.
It’s a lot of work. I’m in a similar boat. I’ve been self teaching myself how to program in various languages and working as a Fullstack developer at a very small startup. While I’ve learned alot, there’s always more to learn and finding direction is a challenge you’ll hit many times over if you stick with it. Right now I’m reviewing various Open Source Projects I could contribute to as I know ultimately this will make me a much better developer. There are so many CLI and web development tools I use that I’d like to expand on but will require a marginal jump in my skills. Here are a few examples: Add a feature to the rTorrent client that would allow it to torrent over i2p Expand the amount of tools available within the SolidJS framework ecosystem to be competitive with React’s ecosystem. Create a HTTP server in Rust that has feature parity with Golang’s Caddy Add a feature to AntennaPod akin to YouTube Sponsor block that would allow for user contributed timestamps to facilitate auto skipping of ad mentions in podcast episodes. I also am slowly working out plans to learn enough about Rust and browsers to recreate the terminal based browser Links in Rust. But these are all just me spitballing. In truth, my skills aren’t quite there yet and the amount of time to get there for each one of these is a lot. So I have to choose wisely and dive in deep on the project’s codebase, probably for at least a year or more to make headway. But this is the mindset I think might help you. Look into the software you use a lot or like the concept of. Figure out how you’d like to improve it or add to it. Reach out to the developers of said software however you can, either make your case for the improvements you want to make or just help out on something they want to do with the software. Learn, listen. Rinse and repeat. Hope this helps a bit.
Lihat kiriman asli pada platform media sosial terkait.