Hacker News: atoko

New comment by atoko in "React Three Ecosystem"

atoko — Sat, 10 May 2025 23:50:20 +0000

Hello! One of the main challenges of figuring a JSX syntax out is what to do about the “children” prop.

Experientially, typescript still has a bit of trouble figuring out the right types for these nested structures. Even with a typed jsx function it sometimes doesn’t infer correctly, so providing plugin capability would take a very careful hand

New comment by atoko in "React Three Ecosystem"

atoko — Sat, 10 May 2025 23:42:56 +0000

I’m working on the documentation, but I have a useful implementation of JSX:

https://github.com/levicape/fourtwo

The best way to use template JSX is either with a CLI, or by using #! pragma to output the constructed yaml after using a builder.

New comment by atoko in "Static as a Server"

atoko — Thu, 08 May 2025 20:07:56 +0000

Thanks!

More concisely: it’s not always the case that prop drilling is possible within a component hierarchy. In a more involved application you store this object in context.

Is what you are describing compatible with this pattern? How does this inform the design of RSCs and as a developer, how can I expect this to affect me?

New comment by atoko in "Static as a Server"

atoko — Thu, 08 May 2025 19:19:12 +0000

I wonder if the omission of React Context in this example is intentional. Do you think Context is compatible with suspense? In the sense that posts is being passed to components as props three times over.

Is it because each component is expected to abstract over async, relying on the promise state?

New comment by atoko in "Bun 1.2 Is Released"

atoko — Thu, 23 Jan 2025 16:12:22 +0000

From what I can tell, this change was merged and released without a passing build. Indicating that the project’s quality assurance process is little more than lip service. I’m not sure how you would track regressions if your tests are flakey to begin with.

New comment by atoko in "No YAML"

atoko — Thu, 28 Oct 2021 02:27:43 +0000

I would bet on the source probably being gitlab-ci configurations

New comment by atoko in "Next.js 12"

atoko — Tue, 26 Oct 2021 16:53:15 +0000

Are there any plans to address Bazel compatibility?

I understand that the Next philosophy is very monolithic but so far I’m having trouble getting it to play nice with build tooling.

New comment by atoko in "Ask HN: What's a promising area to work on?"

atoko — Tue, 22 Oct 2019 17:04:18 +0000

Probably Kaggle competitions

Reactive RunLength Encoding

atoko — Mon, 21 Oct 2019 16:56:34 +0000

Article URL: https://simonbasle.github.io/2018/03/reactive-runlength-encoding/

Comments URL: https://news.ycombinator.com/item?id=21314498

Points: 1

# Comments: 0

Would you pay 100$ for a can of tomato sauce?

atoko — Wed, 21 Aug 2019 15:44:16 +0000

Article URL: http://giangonz.com/cio-essays/pagarias-100-por-una-lata-de-salsa-de-tomate/#english

Comments URL: https://news.ycombinator.com/item?id=20758294

Points: 2

# Comments: 1

New comment by atoko in "IT Runs on Java 8"

atoko — Fri, 10 May 2019 19:48:40 +0000

Spring Boot with Webflux and any rx supporting libraries you can get your hands on

New comment by atoko in "Languages I want to write"

atoko — Sun, 14 Apr 2019 07:46:56 +0000

I believe we’re still trying to dig ourselves out of that particular hole since html days :)

New comment by atoko in "JIT-Less V8"

atoko — Wed, 13 Mar 2019 15:56:59 +0000

How is it slow? [Citation needed]

The async model is easy to use so you get good performance before even optimize it. It comes out of the box with good json serialization/parsing, so that’s one less dependency. Not really sure where you’re coming from.

New comment by atoko in "Scheduling in React"

atoko — Thu, 07 Mar 2019 18:48:48 +0000

Then you end up with data fetches being tied to the rendering lifecycle in a way that makes modifying the mechanism painful

New comment by atoko in "Node.js Logging Made Right"

atoko — Tue, 05 Mar 2019 15:24:16 +0000

It's single threaded. You can usually stick the context in the request object itself.

New comment by atoko in "America’s Cities Are Running on Software from the ’80s"

atoko — Thu, 28 Feb 2019 15:41:58 +0000

I would vouch for IntelliJ. It's clean, customizable and nothing is hidden away

New comment by atoko in "Fundamental Algorithms III"

atoko — Thu, 28 Feb 2019 00:49:16 +0000

I would appreciate better naming on the variables. Some of this is hard to read through with single letter names

New comment by atoko in "New ‘past’ link on HN front page"

atoko — Sat, 23 Feb 2019 07:33:04 +0000

It’s probably rendering what would be “front page” given the same data but with today’s engine.

It would be interesting to see how everything is being cached for a particular day, though.

New comment by atoko in "3 years later, IntelliJ is still unusably slow on macOS with a 4K display"

atoko — Tue, 12 Feb 2019 18:07:21 +0000

It's not the sharpness but the incredible amount of real estate you have. I can have documentation, a preview window and the code open at the same time in what would be their full screen resolution.

To anyone considering one, make sure it supports 60hz at full resolution, otherwise the choppyness makes it unusable.

New comment by atoko in "Stop Learning Frameworks"

atoko — Tue, 18 Dec 2018 17:14:06 +0000

This seems like a good example of what the OP is preaching:

Learn the box model[0], and you won't have to 'fiddle' anymore, you'll know why your elements are arranged the way they are.

Or, you could keep ploughing through permutations of bootstrap magic until you stumble at the correct implementation.

[0]: https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Box_Mod...