After they got rid of the oyster bar though, there's really no great restaurant on Schipol any longer :/ And the star alliance lounge is kinda meh too. But oh well, at least alcohol.
@parcifal there’s a ton of stuff I’m missing from VS Code. But it’s a young editor and I’m sure much will be added in time. I hope they stick with the simplicity though, so it’ll be a balancing act.
@nlovsund aha, sounds like that old trick from school where you’d break a pen in the lock to have class cancelled 😄 but no, I don’t think it was that. Just the teachers having some training.
Hey @pluralistic, this just came across my socials feed. Another enshittification of software happened, remarkable only in the speed in which it happened -- within hours or acquisition by another company, potentially violating licensing and copyright in process. Situation is bad enough that the original dev team forked the code.
If you’re ever thinking about posting “any updates on this?” in a GitHub issue that hasn’t seen any activity in years: there aren’t any updates on this.
@alphakomet suggesting that the issue is closed in that case is definitely welcome. But that’s certainly not common in comparison to the number of “any updates” posts.
@alphakomet I like using thumbs up on the original description to show that, as it’s also possible to sort issues by reactions.
But to answer your question, you’re MUCH more likely to have your issue addressed if you follow up that comment with a motivation why it’s important to your use case, and of course what your use case is. Also often turns out there’s already a way to solve that using existing options, but there’s no way to tell without that context.
@levlaz I spent half an hour the other day debugging an issue where none of the changes I did seemed to make any difference. Turned out that file was in a different directory than the one I was in.
If all the "you really don't need X" blogs (where X is commonly some technology like microservices, cloud, kubernetes...) changed their perspective to first person "I really don't need X", and wrote about their choices based on their own requirements, I'd enjoy reading that. But all too often, the "you really don't need X" posts just comes out as "you don't need a wheelchair, I've managed just fine without one"... and like yeah, me too, but perhaps people have different needs and requirements?
@raganwald Sure! Not saying it isn't useful to contemplate when a technology is too complex or demanding for the requirements at hand. Quite the opposite — I love to read about why and how someone made decisions about their tech stack based on their own requirements. It's the extrapolating "since I didn't need it, neither do you, probably" that I just can't stand.
Working on a language extension for the #zed editor, and it's a long time since I've been this underwhelmed by documentation. Like how each language extension is required to have a 'languages' directory, and this is literally the only documentation on that requirement.
@brookie Yeah, I've been very lucky with the fact that someone else wrote the syntax highlighting grammar for Rego. But just trying to fix some small fry in that project has proven to be extremely challenging, and even copy-pasting from other projects have most often just given me all kinds of errors 😅 But I finally got automatic indentation to work as I wanted, as that was the most crucial part not provided by the original grammar. It's mostly LSP from here on, which is sweet.