Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

299
active users

veganism.social: AboutStatusPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.0-alpha.5+vegan

#elixir

37 posts20 participants4 posts today
Public
hukl

Side Project Update: Switched the production env to the new backend and infrastructure last night. What was running on 4 hosts because of performance issues could now run on a single host. Even though the live traffic is approaching the daily peak, the db host is chilling at 0.02% load and the app servers register between 0.01 and 0.1% load.

I don't know … this might be one of my proudest engineering achievements - unless Murphy comes in with a delayed strike :D

#FreeBSD#elixir#postgresql
Public
Jason Axelson :elixir:

So Elixir 1.19 is slated to remove the Struct Update Syntax and after reading through the issue I am NOT a fan of this deprecation.

The Struct Update Syntax looks like: `%Point{p | x: 3}`

The proposed alternative is to pattern match where `p` is defined but that could be quite far from where you are updating the struct.

Here is the discussion: github.com/elixir-lang/elixir/

I'm curious what other developers think of this impending change. Are you in favor?

· 13 people ·
Instead, we should prefer pattern matching. With the type system, we already get the benefits of checking if fields exist or not, in a more reliable and extensible way. Here is an example from Live...
GitHubDeprecate struct update syntax, such as `%URI{x | ...}` · Issue #13974 · elixir-lang/elixirBy josevalim
#Elixir#MyElixirStatus
Public *
Adam Millerchip

I switched from asdf to kiex, and in the process broke node which I'd forgotten I'd also installed with asdf, which in turn broke coc.nvim which in turn broke my #elixir language server 🙄

Anyway, combined with just finding out #neovim have apparently made nvim-lspconfig simpler, maybe it's time to give it another shot - would be nice to remove node from the stack.

gpanders.com/blog/whats-new-in

gpanders.comWhat's New in Neovim 0.11 | g.p. andersNeovim 0.11 was just released. As in previous installments in this series, let’s talk a bit about some of the big highlights! As always, the full list of changes can be found in the release notes (use :h news to read inside of Neovim). Table of Contents Breaking Changes LSP Simpler LSP setup and configuration Builtin auto-completion Improved hover documentation Putting it all together Diagnostics Virtual text handler changed from opt-out to opt-in Virtual lines Defaults More default mappings Terminal Miscellaneous Breaking Changes We make a concerted effort to avoid breaking changes.
VegansExploreLive feeds
About