lpil.uk
"the maintainer is a legitimate communist. i will not be supporting this language"
- some yt guy, 2024
I made @gleam.run and I do gymnastics (badly)
they/them or he/him. end fossil fuels. genocide is bad. ride a bike.
607 posts
2,510 followers
215 following
Regular Contributor
Active Commenter
comment in response to
post
Oh lovely!!
comment in response to
post
It goes on - there's a list of key insights (each of which gets expanded on):
1. Architecture Trumps Raw Performance
2. Memory Management Is the Ultimate Bottleneck
3. Concurrency Models Matter More Than We Thought
4. Recovery Capabilities Are Undervalued
Very validating article!
comment in response to
post
Oh that sounds great!
comment in response to
post
Oh yes, I should work on some proposals
comment in response to
post
I wish this wasn't behind some sign up wall thingy!
comment in response to
post
I am soooooooo excited
comment in response to
post
boooooo
comment in response to
post
do ittttt
comment in response to
post
Have been to Stronghold Tottenham a few times lately, really like it
comment in response to
post
Love that
comment in response to
post
Related: I finally turned the scattered bits of audio equipment in my possession into a hi-fi setup in the living room and I am loving it so much. Intentional music listening brings so much joy 🥰
comment in response to
post
We've supported this for a very long time!
comment in response to
post
all of the above please, thank you
comment in response to
post
yessss yessssssssssss
comment in response to
post
ooooo!
comment in response to
post
Elixir's livebook attempts to offer that DX without the difficult mutable bits. I'm not qualified to talk about it but the users I've met rave about it
comment in response to
post
LSP doesn't seem offer any way to communicate this process to the user, or to indicate what state the server is in for operations like these. This would make natural discoverability near impossible, and the UX overall quite poor. :(
We really want something as slick as rename or single-step actions
comment in response to
post
Yes exactly! Move the more pressing one for us and we can’t work out how to implement it.
comment in response to
post
Unfortunately this only works if you’re looking to rename things. We want to take input generally!
comment in response to
post
So a custom plugin for each editor?
comment in response to
post
sorry, I was a bit unclear: We’re not looking to implement that refactoring, we’re looking to take input generally to use for things other than renaming. For example: “move to other module”
comment in response to
post
We’re not looking to implement that specific refactoring that is move and then rename, we’re looking to take input generally. Renaming doesn’t enable much of anything unfortunately.
comment in response to
post
Thank you!!
comment in response to
post
Oh hype!!
comment in response to
post
Excuse me for the unprovoked tag @danroth27.bsky.social, but someone just DM'd me to say you may be able to give me some pointers with Gleam's LSP pickle here. Any pointers? Thank you! 🙏
comment in response to
post
Unfortunately this doesn't seem to work :(
comment in response to
post
I don't really want to have to recreate the automation :(
comment in response to
post
If anyone has any ideas or experiences I would really appreciate hearing from you.
Please share to help us reach IDE magicians 🙏
comment in response to
post
There's some really amazing refactorings we want to give y'all, but the language server protocol itself is the main blocker for us.
I think that other languages bless a single editor with a custom integration with that. We don't want that! We want to support everyone!
comment in response to
post
It splits the patterns into checks, reorders them, and turns it into a if-else tree
comment in response to
post
Flow control is now compiled into an logic optimised tree to do the smallest number of checks, to group expressions to prevent repeated checks, and to remove redundant ones entirely.
comment in response to
post
I am in awe of these improvements, which is why I'm sponsoring @giacomocavalieri.me's work!
github.com/sponsors/gia...