HN user

Zezima

241 karma
Posts5
Comments62
View on HN

As a Recurse Center participant and alum, these rules form an important and largely silent backbone of the community's culture.

Often reading rules causes strong reactions. Seeing how those same rules are implemented makes all the difference.

Rather than discussing the rules, I'll share experiential evidence: the community is welcoming to beginners, gentle, curious, kind, playful, and above all else: supportive.

The rules are a helpful "buck" to stop at should mistakes or conflict - small or large - arise (which rarely occurs). The key is commentary and forgiveness.

The experience of attending a batch at recurse is largely regarded as their best for many of my fellow Recursers - it certainly is one of mine.

If you're curious please reach out to them. I'm also happy to chat or answer any questions (and give a glowing review).

I have this as well, it's mildly entertaining but not overpowering. The floaters only appear when looking at a very bright blue clear sky, it never triggers otherwise.

When it does I can pause, appreciate the show, and then go back to my day. It's a fun one for sure.

Seconding Zola. Fantastic project. I built a site with > 200 pages (including media) in 90ms on an M1 MacBook Pro.

There is no plug-in ecosystem unfortunately.

Shortcodes are nice and a modest replacement. Missing any headless CMS integration naturally because it's statically typed and compiled.

Not the poster. What exactly are you asking about?

The usage of the error type the OP wrote is to get the line number of any error without using a macro on top of every single function in our crate.

The person who wrote `MyError` accomplished it by defining their error type as "something that can be constructed from any other error" (`impl From<E: StdErr> for MyError`) and additionally heap-allocated the original error with `Box::new(error)`.

So the usage would be to write one single error type in a crate which can "capture" or be constructed from any error type `E` and also prints out the line number of that error via `impl Display for MyError`.

You've described Brooklyn and NYC at large... if you're anti-car then consider the city. Boston is a good second choice. I've lived in both.

NYC comes with the normal downsides of the biggest city in the US: expenses, limited space, crowding, and noise. But this is true of all large cities in the world: Paris, London, Tokyo, etc.

But it comes with the immense upsides of a functioning metropolitan transit system, which covers the majority of the living spaces, at an affordable price, and doesn't require Uber or car to go the "last mile".

Additionally there are countless flex offices, coworking spaces, etc. Everyone I've met in tech in the city has some sort of WFH/WFO at this point in the pandemic.

City life isn't for everyone but if you're looking for a good transit system in the US there are two or three (Chicago too)

Best of luck with your journey

Apple Passkey 4 years ago

That doesn’t sound correct. It’s not the finger print which identifies you to the website, it’s the public private keypair.

The private key is stored in the device’s Secure Enclave. It’s the face and fingerprint recognition which authenticates to the Secure Enclave in order to retrieve the private key.

When purchasing an android phone, you do need to sync the private key to the new device. Hence Passkey, which uses iCloud as its secure and authenticated syncing scheme.

Effortless.

Muscle memory is a wonderful thing. You don’t struggle to wear two different pairs of shoes or ride two bikes.

With enough practice (three months for me) I can type easily on phone keyboards, kinesis/moonlander, and qwerty laptop keyboards.

Do yourself a favor and take care of your hands. Split, ergonomic, welled, and ortholinear keyboards make a noticeable difference for finger fatigue, RSI, etc. my wrist tenderness is gone after using my kinesis for 3 years and has not returned after using the ZSA moonlander for 3 months.

This is the comment I’ve been looking for.

I’ve been writing exclusively React for 3 years and the majority of react community are ill informed as to the origins of React.

Originally an OCAML implementation, there are clear benefits from pure functions, immutable data structures, and representing views declaratively in a DAG. I am simply restating the motivations and characteristics of React.

Then Redux comes long, inspired by Elm and it’s immutable update cycle, and the React community proceeds to spend the next two years utterly confused as to why anyone would want to use Redux. Followed by an onslaught of “You might not need redux” and “How I built my react app without redux” articles by shortsighted developers who merely reimplement Redux. :facepalm:

Redux-saga is the desired solution to handling async rendering while also staying true to the core properties of React. I’m glad you mentioned it in your comment.

I find the React community to be largely defined by its misunderstanding the core design and goals of React.

I find Crank an interesting and clever application of async generators.

However claiming that the core properties principles of React - functional properties, DAGs, and priority scheduling - are “dogma” is a shameful misunderstanding.

The correct criticism is of the behavior of the React team in their community response and the Suspense API alone - rather than the intrinsic properties of functional user interfaces.

Nonetheless, I am impressed by the technical effort in creating a new async generator API for rendering JSX. This project is no easy undertaking. Sincerely hoping for its future success (and self reflection).