Semua Gambar Berita Video Belanja Maps Sosial Media Files Science
Sekitar 20 hasil (1.91 detik)
Komunitas lemmy.world

Elixir vs Go: what to learn in 2024

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.

Komunitas lemmy.world

The beginner of tutorial hell

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.

Komunitas mlem.a-smol-cat.fr

The LINUX DISTRO model is BROKEN

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)

Komunitas beehaw.org

The future of back-end development

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.

Komunitas programming.dev

Is Golang the name we want to use for the official Go community here?

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.

Komunitas lemmygrad.ml

The GenZedong cause needs programmers!

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.

Komunitas sh.itjust.works

Let's talk CLI/TUI and Developer Workflows!

@RareBird15 @programming @linux @selfhosted Ones I haven’t seen mentioned (unless it came in while I was typing this). https://github.com/kainctl/isd - Interactive systemd. https://github.com/zellij-org/zellij - tmux alternative. Built in which-key functionality. I initially switched to it because I like large scrollback buffers and tmux was super slow at resizing window panes. Can open buffers in nvim for better search. Nicer TUI if you don’t mind a little bloat / bling. https://github.com/arxanas/git-branchless - Work on stacked commits. Instead of opening PRs linerally you work on several commits at once with the expectation each commit will be a PR. Promotes smaller PRs that are easier to review to complete a feature. Often when doing that linerally you may discover a bad choice made earlier and have to reverse course and refactor. With a branchless workflow you go back and forth on commits so the final stack of PRs doesn’t include those reverse course refactors. git sl has some nice TUI graphs of your stack. https://github.com/mystor/git-revise - Split, rearrange commits. Works nicely with git-branchless. https://github.com/tummychow/git-absorb - Reflect changes from a commit backwards. Also works well with a branchless workflow. If I’m honest I just develop linerally and use an AI agent/skill to restack using the 3 programs above to erase pivot / refactor points and to group logical blocks into an easy to review PR. https://github.com/ymtdzzz/otel-tui - Open Telemetry viewer. https://github.com/brocode/fblog - JSON Lines viewer. https://github.com/aristocratos/btop - Better top. https://github.com/jandedobbeleer/oh-my-posh - Terminal prompt. My daily driver. https://starship.rs/ - Another terminal prompt. Played with a little but never got around to giving it my full attention to match my oh-my-posh setup. https://rclone.org/ - Remote backups using my own encryption key. Supports many cloud providers. https://github.com/Mic92/nix-fast-build - Not sure its really faster but has a nicer TUI. https://dircolors.com/ - Directory listing colors in terminal output to better distinguish file types. At a glance I can distinguish read-only, executables, symlinks, directories, etc. https://github.com/jesseduffield/lazygit - Git TUI. I only use in neovim though, don’t think I’ve ever run it directly. https://github.com/sindrets/diffview.nvim - Better merge conflict handling in neovim. https://www.lazyvim.org/ - Base neovim config with lots of TUI sugar. https://github.com/stevearc/oil.nvim - File tree explorer in neovim with editing capabilities. Hands down the most efficient way I’ve found to normallize torrent file names. Fixing 5+ seasons of a show takes a few minutes if you know the right vim keybinds. https://github.com/getsops/sops / https://github.com/mic92/sops-nix - Encrypt secrets in git repos. https://github.com/zdharma-continuum/fast-syntax-highlighting - Syntax highlighting as you type shell commands. https://github.com/luccahuguet/yazelix - Opinionated Yazi, Helix, Zellij setup with custom patches to integrate. Looks interesting but could never get to work with nix as it keeps trying to write to store paths. They even have a flake.nix in the repo… less - Less shitty more (terminal pager) with the options below. export LESS="-aRix2 --use-color --mouse --wheel-lines=3" export SYSTEMD_LESS="$LESS" # a = search from current position # i = case insensitive # x2 = tabstop # R = color control chars show color https://pnpm.io/ - Better monorepo support than npm. Faster too. Easy to patch dependencies. https://bun.sh/ / https://deno.com/ - Alternate node runtimes. Only have used bun, but its a faster cold start and uses less memory. https://oxc.rs/docs/guide/usage/linter.html - eslint clone in rust. Seconds versus minutes. Uses the golang TypeScript 7 preview version of typescript-eslint for type checking. https://rolldown.rs/ - Rust clone of the rollup JS/TS bundler. https://ast-grep.github.io/ - Grep AST patterns. Written in rust. https://dprint.dev/ - Formatter that unifies other formatters. Lots of fast rust plugins. https://biomejs.dev/ - Rust based node formatter. dprint support. https://github.com/astral-sh/ruff - Rust based python linter and formatter. dprint support. https://github.com/numtide/treefmt - Like dprint, forwards to other formatters, but intended for nix declarative setups (for use with devshell or devenv). https://direnv.net/ / https://github.com/nix-community/nix-direnv - Activate a virtual environment when you enter a directory. Common with nix devshell/devenv but can run any command. Auto reload based on certain files via watch patterns. https://github.com/mikesart/inotify-info - Debug why you’ve maxed out file watchers. https://github.com/lyonel/lshw / https://github.com/pciutils/pciutils - Detailed hardware info. https://github.com/wagoodman/dive - TUI to explore docker layers. https://github.com/containers/skopeo - Bunch of utilities for working with docker images and registries.

Komunitas piefed.social

Copilot is now injecting ads into GitHub pull requests. It's a disaster.

You do have to ask for permission. https://docs.codeberg.org/ci/ Asking permission involves creating an issue on the Codeberg-e.V./requests repo: https://codeberg.org/Codeberg-e.V./requests/issues/new?template=ISSUE_TEMPLATE%2FWoodpecker-CI.yaml Here’s an example issue asking permission for CI: https://codeberg.org/Codeberg-e.V./requests/issues/1663 They get back to you fairly quickly. I think the main thing they check for is if your project is FOSS. They don’t seem very strict otherwise. After you get permission, you can go to https://ci.codeberg.org/login to access CI. You’ll also need to create a .woodpecker folder in your repo. Woodpecker docs are here: https://woodpecker-ci.org/docs/usage/intro # .woodpecker/my-first-workflow.yaml when: - event: push branch: main steps: - name: build image: debian commands: - echo "This is the build step" - echo "binary-data-123" > executable - name: a-test-step image: golang:1.16 commands: - echo "Testing ..." - ./executable

Komunitas lemmyrs.org

Consolidating on one Lemmy instance

A few things: Instances are like their own self-hosted Reddits with communities being the sub-reddits. We have (had?) r/python, r/rust, r/golang along with r/programming; we can do the same here with topic-focused instance (like this one). I can imagine there being instances like lemmygo.org, lemmypy.org etc if the Reddit exodus continues. You don’t need multiple accounts to access communities (sub-reddits) from other instances (reddit). A single account on any instance allows you to access communities from any other instance. The UX/UI is a bit wonky, but it works. As @[email protected] pointed out, micro-communities like cli, wasm, networking etc can potentially become big enough and/or have specifics that are more suitable to exist on a topic-based instance. Personally, I don’t have any preference. I will simply subscribe to the community which is the most active on whichever instance.