I click through every formatter-related post because I am looking for something better than what I have. My team at work wanted to use Prettier, but lack of configurability (and also heinous bugs!) made me switch to dprint[1].<p>But even dprint doesn't do a couple of the things I want, #1 of which is "For the love of science, please stop deleting the intentionally placed blank line after a hugely long class declaration!" E.g.:<p><pre><code> @Directive()
export abstract class AutocompleteComponentBase<T> implements ControlValueAccessor, AfterContentInit, OnDestroy {
@ViewChild(DsAutocompleteContainerDirective, { static: true }) autocomplete: DsAutocompleteContainerDirective<T>;
// class definition continues...
</code></pre>
I mean, I know I am a bad person because of those long names, but that is how life goes sometimes! And the blank line there at the top is just very important to like, catch one's breath, while reading this code.<p>(I'm really just posting this in the hopes that somebody will throw me a "Bro, just use hpstrlnt, it totally lets you configure that!" -- I have not actually tried Rome to see if it does (it's Monday morning and I'm not quite ready to be disappointed again...))<p>[1]: dprint is good, and I recommend it as the best code formatter I currently know of: <a href="https://dprint.dev/" rel="nofollow">https://dprint.dev/</a>
I look at tools like Rome and they might have been relevant 5 years ago.<p>I think Bun has a better shot than Deno because it has a very fast built in node_modules installer. But I think Bun's goals are too ambitious - trying to be all things to all projects from a single binary. No one cares if you have to use a separate binary, esbuild, for all your bundling needs, for example.<p>It's amusing how the entire JS ecosystem put up with such slow build times for a decade. If these JS tools teach us anything it's that JavaScript doesn't cut it for performance and a compiled language is the way to go.
I don't see how they are going to compete with tons of ESLint plugins. There's just no way a small team can do such a large amount of maintenance.
I've got mixed feelings about Rome. There's so much room to cover with ridiculously slow tools today. But I'm sick and tired of these people in the industry dropping their toys because they're tired of working on stuff people actually use instead of just improving what they currently have.<p>Would it have been impossible to nudge Node.js in the direction of where Deno is today?<p>Would it have been impossible to replace Babel with a Go implementation?<p>I also don't want tools that want to be literally everything.<p>Imagine if Daniel Stenberg was like, "You know what I'm tired of cURL, let me rebuild literally the same thing in another language and give it a new name, and entirely different opts."
Is there a JSON formatter out there that can be configured specifically for numeric arrays ? I'm specifically looking for something that formats 1D arrays in one line and 2D as one line per row.<p>fracturedJSON gets close but not exactly what I want.
Half-OT:<p>What do you think of pnpm?<p>I saw it off and on since 2015 and read some projects switched to it and then back again, when it didn't work out.
Eslint can get VERY slow on large apps. Rome seems to be the perfect answer to that, but I can't seem to find a way to port/import Eslint rules into Rome.
Why write something like this in Rust since it presumably doesn't have anything memory intensive or real time going on? Rust's manual memory management is a necessary thing sometimes, but it is a pain, right?