I know people that worked on golang and chromium outside of google and then tell me how difficult it is working on it because Google has final decision making power on those projects even though they’re open source.
Especially this hate towards those corporate bots who ignore robots.txt and try to burn my house by putting my computer on fire because it exposes code to the internet. How dare I do that. Just be happy that 8 cores are 100% utilized on golang hosted website and it’s only /13 ip range ddos not /8
Pong. @[email protected] , in sublinks, the federation services are entirely separate from the API of the instance. So much separate, the federation services are written in a programming language called Golang. The API service is written in a programming language called Java. One aspect does not require or preclude the other with Sublinks.
I’ve heard this exact same bullshit spun defending choosing golang too, and it’s just as bullshit there as it is here and that’s not even touching on the aspect of this being based on the extremely toxic “oh yeah just burn them up and find the next one” mentality that has become far more prevalent in the world under the umbrella of zirp-funded bayfuckery gaining international traction I beg you to go consider whether this is your actual position, or some shit you picked up from someone else. to consider what the effects of this stance are, not just today but in 5/10/15y+. it should be quite easy to see both how it helped us get into the collective pile of shit we now do have, as well as why it won’t ever be good
Thank you for your question! There are some benefits, among them: syncspirit is faster. According to my measurements it is able to sync linux sources tree folder for 2 mins vs 15 mins of syncing when using syncthing (that’s over a localhost, of course) syncspirit has a different UI. That’s matter of personal taste, of course, but I like to see the exact picture what is synchronized and what is not. syncspirit is able to run on more older software (i.e. from windows xp and up). Syncthing uses golang, and its software support is indirectly controlled by google (i.e. “artificial aging”); recent builds are running only on windows 10 and windows 11. Microsoft already dropped windows 10 support, so, I expect that in near future google will do the same. the long-term goal of syncspirit is to allow “selective sync” feature, which unlikely to be implemented by syncthing. wbr, basiliscos
Golang, javascript, typescript. 5 yrs Not much. Just my favorite food/socialist subreddits Yes, I build web applications for my day job. 4 yrs Lenin Obviously Same as on here: aldentesempre
I would love to use golang for this but it’s standard library alone is bigger than the amount of available RAM.
on the other hand, and other side of the so-called “proxy” service, it’s a shame that the golang community has so far mostly acquiesced to the situation where the language’s tooling by default relies on making numerous connections to google’s servers.
I tried Homebrew once in a VM and didn’t like it, I felt it was too invasive. https://github.com/Homebrew/install/blob/85c5f4b57452dbd1c7ebc01a021548d2ceaf2b64/install.sh#L173 Why does it create another user and put files under /home/linuxbrew/? Answer: The script installs Homebrew to its default, supported, best prefix (/opt/homebrew for Apple Silicon, /usr/local for macOS Intel and /home/linuxbrew/.linuxbrew for Linux) so that you don’t need sudo after Homebrew’s initial installation when you brew install. Where’s the logic in that? Why not just install to the user’s home directory so that you don’t even need root access in the first place? https://github.com/Homebrew/install/blob/85c5f4b57452dbd1c7ebc01a021548d2ceaf2b64/install.sh#L222 Why is sudo hard-coded? Answer: it’s to prevent people from using doas and other sudo alternatives. https://docs.brew.sh/Installation#untar-anywhere-unsupported Why is installing from the tarball unsupported and so frowned upon? FFS isn’t this just supposed to be a package manager? Why is everything so complicated and opinionated when compared to pip, cargo, Flatpak, etc? Compare this mess to Golang’s install and uninstall process where you literally just need to tar -xzf a file or rm -rf a directory.
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.
And Pike wrote this passage in the very article you mentioned: (For those who object that dot files serve a purpose, I don’t dispute that but counter that it’s the files that serve the purpose, not the convention for their names. They could just as easily be in $HOME/cfg or $HOME/lib, which is what we did in Plan 9, which had no dot files. Lessons can be learned.) And guess what, there is actually such a directory on most Unix-derived OS nowadays - $XDG_DATA_HOME/$XDG_CACHE_HOME, which Go could just honour if the environment variable was set and fallback to cluttering $HOME. But no, they insist on their insular solution…
Lihat kiriman asli pada platform media sosial terkait.