mcluck

I've asked this before but I'll ask it again. Usually when people say they don't like vim plugins for other editors, they say that the plugin doesn't do everything they need. What features of vim are people missing in the plugins?

I've been using vim and vim bindings for like 3 years now. I've occasionally ran in to something that the plugin doesn't handle well but I can work around it with a custom binding. This has only happened a handful of times. I'm genuinely curious about what features of vim I've been missing out on!

Getting into a federated space brings a lot of questions for normal people. Why this instance? Why not this instance? Can I only join one? What if my friends join a different one? This one only has 100 people, is it weird if I join? This one has 1,000,000 million, isn't that basically Reddit/Twitter/whatever?

These are the sorts of questions that come to mind for normal people. By the time they've asked this pile of questions they've already decided it's not worth the hassle of finding the answers

When your boss said "deliver more", I don't think that's what they had in mind

(congratulations!)

Because I don't want to debug your clever code when we have an outage and you're on vacation

Nice! Maybe this will help convert some of my friends to the dark side

I have the exact opposite experience when I get to play a game again with better graphics. It's like I get to experience it all over again, which is great

Agreed. To me, browser support for modules is great for debugging but is not a suitable replacement for producing an optimized set of bundles

You're mixing a couple of ideas. There is a proposal[1] to allow for type annotations in the browser but it's only a subset of what's possible in TS. As for barreling/bundling, that's never been a goal for TypeScript. That's handled by tools like Webpack and ESBuild. In fact, there's an effort going the opposite direction. As browsers support ES style modules, we don't need to bundle anymore as the browser will load the relevant files as needed

[1] https://github.com/tc39/proposal-type-annotations

[2] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guid...

You seem to be in a very particular bubble if you think most developers can trivially afford high end GPUs and are already investing in SOTA GPUs. I know a lot of devs from a wide spectrum of industries and regions and I can think of only one person who might be in your suggested demographic

I setup my website and email at a dot-tech because, surprise, I work in tech and the equivalent com and io were taken and/or prohibitively expensive

Of course you'll always have different ways of building UIs depending on circumstances but eventually some consensus will be reached for a default approach.

WinForms used to be the default for Windows, Tk was the default for Linux (or at least that was my impression, I was all in on Windows back then), etc.

For many people, using web tech has become the default if you want to build cross platform UIs. You have the option of building with imgui, Qt, Gtk, etc. but I don't think it's controversial to say that your average dev who wants to make a cross-platform GUI will probably use Electron or an Electron-like.

I really want to have a default for the Rust space. I've even done some work here myself which is why it's surprising to me that we aren't there yet

> GUI in Rust progresses with unprecedented speed – 3 months in Rust GUI-land is like 3 years in the mortal world.

areweguiyet.rs was started almost exactly 5 years ago. That means it's been about 60 mortal years and we still don't have a definitive solution to GUIs.

Just picked this up the other day! So far it's been awesome. I've assembled a basic pair of bars with the usual suspects and it's been smooth sailing

If Reddit would stop making the site and app unusable we wouldn't need alternative clients. I can feel my phone heat up if I try to browse Reddit with any of the official options other than old Reddit

Nice! I'll be taking it for a spin after work. One question: I'm interested in trying to use this as a way of querying my Zettlekasten-like note system

C# is over 20 years old now. In the land of language design, it's not a young language

There was absolutely zero technobabble in that persons comment. Perhaps you need to ask yourself how well you understand the space

This literally sounds like something out of a cyberpunk dystopia novel

Seconded for SQL. Don't sell yourself as a SQL person unless that's what you love and want to work on data-heavy systems. For everyone else, being fluent in at least one dialect of SQL and being comfortable jumping between dialects will do wonders for you. I spend far less than 10% of my time on SQL but the time that I do spend on it is incredibly valuable

That could help and I have experimented with relative line numbers but have decided against it. I want to see absolute line numbers for matching up error messages and I find it's easier to communicate in absolute line numbers when doing code reviews or pair programming

I'm definitely not a vim master but I've made an active choice to avoid 4j style movement. The main benefit of vim, for me, is the mind-body connection. Commands are either muscle memory or like saying a short phrase in my head so it flows out naturally. Counting lines before executing breaks that natural flow

You can write CSS-in-JS style without a runtime https://vanilla-extract.style/

In my opinion, this gives you all of the supposed benefits of Tailwind without all of the noise and annoying opinions that come with Tailwind

Perfect, thanks!

Great project!

I'm curious about the set of available parser annotations. I went through the list but I didn't see anything which allows for optional elements. One example would be dangling commas. Did I miss it or are there plans to support such constructs?

I wish I could scream this at the top of my lungs at some of the places I worked. In one place, we spent more time adjusting and refactoring Terraform files than actually writing application code despite having about a thousand users, most of whom used the app once for a few minutes in the morning.

Seems to be working now

You've shot yourself in the foot with your dark mode comment. It's not scientifically proven that dark mode is better than light mode or vice versa. It has been proven, as you mentioned, that contrast ratio is important. Contrast ratio is not dependent on if the background is dark or light. It's dependent on the comparison between the dark and light shades.

One of the major reasons (other than the fact that it isn't finalized) is the lack of a way to interact with the DOM or other external memory models. There is work currently being done here but for now, anything you write with Wasm needs to have hooks out in to the real world and the serialization in and out of Wasm world is expensive

I don't understand what that paragraph is on about. I use this approach extensively and the whole point is that you don't need exceptions anymore. LogRocket is a service that kind of counts on errors being thrown so maybe there's something there haha

Or maybe people just like to improve on the tools that they use every single day?