Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
spoiler
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
151.
▲
by
spoiler
2y ago
> - Bevy (Rust ECS engine), which is nice at first but has a lot of problems with its implementation and can become rather messy. Can you expand a bit about why this was messy or comolicated? I found the paradigm leads to pretty well org
152.
▲
by
spoiler
2y ago
I've seen this be a hit and miss. My previous product manager has a technical background and moved into production management because he thought product managers suck, and wanted to be a force for good. He was one of the best product m
153.
▲
by
spoiler
2y ago
I guess anything is an implementation detail depending on what level we're talking about, but each layer is constrained by the "previous" layer in some ways, and we're working within those constraints. Sometimes we have
154.
▲
by
spoiler
2y ago
> People often mistakingly describe the vdom as faster than the dom, this is incorrect. You'll get better performance with _carefully crafted_ DOM access, but that's easier said than done, especially on a larger applications. v
155.
▲
by
spoiler
2y ago
DOM interactions (read, writes) are synchronous, they're very slow, and it must happen on the main thread. This can cause the browser tab to freezing if access and updates aren't carefully "curated" (ie you don't wa
156.
▲
by
spoiler
2y ago
> TS astronauts, left unchecked, can make extremely complex types using generics, conditionals, and all the esoteric features of TS, resulting in extremely obtuse code. Disclaimer: I guess I'm a fellow TS astronaut. Most of the time
157.
▲
by
spoiler
2y ago
A game that has similar building (albeit less "scriptable" since there's no redstone) is Enshrouded. They use smaller voxels and a different polygonisation algorithm (seems to also differ based on voxel material tool). It
158.
▲
by
spoiler
2y ago
When I last used it, as a type system it was much better than TypeScript. A lot of flow features now exist in TypeScript though too. One big annoyance with Flow I had is like you said: unpolished tooling. Another was frequent breaking chang
159.
▲
by
spoiler
2y ago
It's possible that internal SWC version will be versioned alongside Node, meaning TS syntax support won't drift. Or am I missing something?
160.
▲
by
spoiler
2y ago
Most of this is solid advice, but I disagree with some of the `useRef` stuff. Refs are an escape hatch for things that can't be modeled with React's existing reactivity features. As a rule of thumb: only use them when interacting
161.
▲
by
spoiler
2y ago
TIL labyrinth and maze aren't the same thing! I always thought they were synonyms. I grew up in Croatia, and there the word for both maze and labyrinth is "labirint"
162.
▲
by
spoiler
2y ago
Which lints are you missing?
163.
▲
by
spoiler
2y ago
I know I'm being a bit negative with regards to ESLint, but I'd just go with BiomeJS these days. It's faster and more sensible with its default lints. And to boot it comes with a very sensible (and Prettier compatible) format
164.
▲
by
spoiler
2y ago
I was thinking of adopting UUIDv7 for some of my stuff. So, I'm curious: why is this the case? Is it because of the time component?
165.
▲
by
spoiler
2y ago
I think you're hand waving a lot of problems away without giving them the thought and attention they deserve. And sometimes using arguments that aren't really unique to the JS ecosystem. > The complexity is there because everyo
166.
▲
by
spoiler
2y ago
I think you're hand waving a lot of problems away without giving them the attention they deserve.
167.
▲
by
spoiler
2y ago
Ha, I think I know what you mean, but I'm not sure we're talking about the same thing. For me personally, I'm glad that Rsbuild didn't stop decekopem when something like esbuild popped up. I'm sure people tied up in
168.
▲
by
spoiler
2y ago
All of these are lessons learned from previous iterations. Also, some of these were probably in development for a while. If you're close to finishing a product, do you just stop and abandon months of work just because a challenger appe
169.
▲
by
spoiler
2y ago
I fully agree with you, and want to add: JS/TS due to it's accessibility is one of the largest eco systems. Hell, whether you are or aren't a devekoper you're part of it through using a browser. People often scoff at com
170.
▲
by
spoiler
2y ago
Rsbuild has been really nice to use. I migrated a bunch of webpack projects to Rsbuild and it reduced config, and improved DX. One of my favourite features is probably that it understands a tsconfig file: https://rsbuild.dev/
171.
▲
by
spoiler
2y ago
Isn't accidental complexity just complexity that's not part of the problem domain? Say in the context of serving content/downloads, accidentally complexity would be caching, proxies, CDNs (etc). Basically stuff that we have t
172.
▲
by
spoiler
2y ago
I've experienced this too, but I never understood why this phenomenon happens. Is it because we start adding abstractions before we understand the problems? Like, there's a certain threshold where keep things too simple makes them
173.
▲
by
spoiler
2y ago
My 2c on the whole React and complexity situation: it's not great, but at the same time it's not as bad as someone people make it sound. Things _can_ be done in a simple way. The issue with React is that it's just a library,
174.
▲
by
spoiler
2y ago
I'll never get over how convoluted it felt to make a modal appear on the screen, using the "blessed" Next.js way. You need parallel routes, slots, intercepting routes, file names that look like the blast radius of a shell scr
175.
▲
by
spoiler
2y ago
Sorry if I'm being nosey, but I'm curious about the chronic back pain. Is it something that developed over time, is it gwneti, is it an injury? How do you cope and manage it?
176.
▲
by
spoiler
2y ago
I honestly don't remember the last time I used a terminal to edit files. I don't really miss vim that much since I still use vim shortcuts in VSCode. I briefly tried Emacs but a lot of the major modes for languages I used were too
177.
▲
by
spoiler
2y ago
Yes, that's true of TypeScript in general. Code that fails type checking still gets emitted as JS. It's a bit annoying, but there's good reason for it. However, it can be controlled with compilerOptions.noEmitOnError (can be
178.
▲
by
spoiler
2y ago
For some reason, snippy looks terrifying lol
179.
▲
by
spoiler
2y ago
The TypeScript portion is a little bit wrong. Return position void in TypeScript means the value is unobserved by the caller, not that it's undefined. It's subtly different.
180.
▲
by
spoiler
2y ago
I feel like it's a bit weird they didn't mention Rsbuild. Rsbuild is a "nice" wrapper around Rspack and SWC. It's probably more holistic/batteries included than Farm, from a cursory glance. Rsbuild also aims to
More ›