Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
conaclos
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
16 ms
·
151.
▲
by
conaclos
3y ago
Hey! Just wondering: how did you prevent Discord bans because of using their API without the Discord app?
152.
▲
by
conaclos
3y ago
Hey! Have you had time to test?
153.
▲
by
conaclos
3y ago
Bun do not plan to implement a formatter or a linter. This makes Rome and others still relevant.
154.
▲
by
conaclos
3y ago
Rome is less opinionated than it used to be. However, I admit it is still more opinionated than ESLint. It is part of its ADN. However, Rome is also trying to provide a smooth experience. And we are open to relax some rules if it makes sens
155.
▲
by
conaclos
3y ago
For now, Rome implements most of the ESLint recommended rules (including TypeScript ESLint) and some additional rules that are enabled by default. In the future, you can expect a recommended preset that is a superset of the ESLint recommend
156.
▲
by
conaclos
3y ago
It is quite stable at the moment. I would still recommend taking a close look at the changes that Rome suggests, especially for large codebases: I think that some bugs are still expected. The LSP (VSCode extension) is less stable at the mom
157.
▲
by
conaclos
3y ago
> 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. I have sometimes the same feeling. I
158.
▲
Rome v12.1: a linter formatter for TypeScript, JSX and JSON
(rome.tools)
133 points
by
conaclos
3y ago
|
130 comments
159.
▲
by
conaclos
3y ago
This new version adds the support for Stage 3 decorators. It also stabilizes more than 30 linter rules.
160.
▲
by
conaclos
3y ago
> I think for Nintendo, the more prudent solution would be to release an updated Switch with some more powerful hardware that's fully backwards compatible with the existing Switch library. It would be very par for the course for the
161.
▲
by
conaclos
3y ago
My main aliases are: a more human-friendly ls and an alias of rm which attempts to detect mistakes: alias l='command ls -Av1h --color=always --time-style=long-iso --group-directories-first' # -A: show all, including dot
162.
▲
by
conaclos
3y ago
I did not say that. I think it is a good thing to do thing properly. File resolution is pretty complex (too complex) in Node/TSC. I would like others tools to support native .ts imports and translate automatically to .js on code emitti
163.
▲
by
conaclos
3y ago
Literally most of other tools: TSC, esbuild, bun, swc, babeljs, ... It is even the recommended way in TSC, esbuild and others to import a .ts file in order to emit esm-valid code. I understand the point of Deno. However, it is just too hard
164.
▲
by
conaclos
3y ago
Something that still stop me from using Deno is the incompatibility between Deno and other tooling regarding the import of TypeScript files. Namely, it is not possible to import a `.ts` file via a `.js` import [0]. [0] https://gi
165.
▲
by
conaclos
3y ago
For the ones that love a more lightweight setup I recommend yash [0]. It is more lightweight than zsh, fish, or bash and comes with a decent auto-completion and line prediction a-la fish. For my prompt, I am using polygot [1]. However, I am
166.
▲
by
conaclos
3y ago
Is someone using the node:test runner? Some reviews could be appreciated :)
167.
▲
by
conaclos
3y ago
Rust could introduce a new trait similar to Default: let's say ElseDefault. Every type implementing this new trait could return the default value of the type of if branch when the else branch is missing and is triggered. Option<V>
168.
▲
by
conaclos
4y ago
One missing: Are we simple yet [1]? [1] https://arewesimpleyet.org/
169.
▲
by
conaclos
4y ago
What do you mean by Containers? A good abstraction for passing allocators could be effect and effect handler.
170.
▲
by
conaclos
4y ago
This new version brings JSON support, new lint rules, import sorting and more!
171.
▲
Rome v12 – Linter Formatter for JavaScript, TypeScript, JSX, and JSON
(rome.tools)
9 points
by
conaclos
4y ago
|
2 comments
172.
▲
by
conaclos
4y ago
I am still attracted by Flow which seems to have a simpler and stronger type system. However, Flow seems a bit unstable and the lack of support for TypeScript declaration files and widely used TypeScript syntaxes are stopping me from switch
173.
▲
by
conaclos
4y ago
A preview is available on the GitHub README [0] [0] https://github.com/system-fonts/modern-font-stacks#system-ui
174.
▲
by
conaclos
4y ago
> Libraries even let you do strong typing with TypeScript to define the expected structure of the result. The tagged template does not return a string in this case?
175.
▲
by
conaclos
4y ago
Is there a difference between dedent`something ${code}` and dedent(`something ${code}`) ? Not sure to understand the advantage of tagged strings here...
176.
▲
by
conaclos
4y ago
The Deno style guide encourages the use of `#prop` over `private prop` [0]. Other guides such as the Google TypeScript Guide discourages their use [1] for now because they are transpiled to slow code. What I could conclude is: use `#` over
177.
▲
by
conaclos
4y ago
It is also a breaking change to use new syntax and functions since old browser does not support new features. In this perspective `arr[-1]` seems a fair breaking change.
178.
▲
by
conaclos
4y ago
The same author wrote a follow-up article [0] "Names are not type safety". [0] https://lexi-lambda.github.io/blog/2020/11/01/names-are-not-...
179.
▲
by
conaclos
4y ago
While theoretically I accepted with all the points, in practice it is sometimes too bloated to add so many types that are barely distinct. It is sometimes better to trade safety for simplicity. The trade-off is always hard to make. For inst
180.
▲
by
conaclos
4y ago
ESbuild seems more popular than SWC. Moreover, ESbuild has really good documentation and a great CHANGELOG. It is always a pleasure to read a new entry in its CHANGELOG. IN the other side, the changelog of SWC is too close to the code. This
More ›