MKRhere's comments

Location: India

Remote: Yes

Willing to relocate: Yes

Technologies: TypeScript, React, PostgreSQL, Redis, MongoDB, Supabase, Telegraf, Python, Zig, Figma

Résumé/CV: https://mkr.pw/resume

Email: [email protected]

I'm a performance and design-oriented full-stack developer. I can both build a product from scratch or take on an existing codebase and quickly help resolve scaling or performance bottlenecks. As an architect, I'm fluent with design. I can work closely with a designer or adapt to an incomplete spec and design and build with ease.

I love a good challenge, and I'm personally fond of decentralisation-related ideas and open source. I also enjoy writing parsers and protocol-related work. I've worked with many languages and can quickly adapt on demand. I don't believe language is ever an obstruction.

Timezone is also rarely a problem; I can work with significant overlap in working hours for most countries (plenty of experience working with US, Europe).

EIG? Yeah, tough luck. This all makes sense now.

Author here. We have an idea in the works to implement `typeInfo`, but it serves a more type -> value usecase (for example, generating validations from types).

However, going full cycle (type -> value -> type) is not as trivial because we won't get to ride on TypeScript's existing language server support, and solutions such as needing to use our own patched tsserver, etc., are too hacky for my liking.

Also not possible is generic types as parameters to comptime functions like Zig.

Happy to discuss more comptime usecases though. Feel free to raise an issue if you'd like to discuss, we can look into feasibility.

Author here.

To be clear, what you're asking for is basically:

const X = comptime(condition ? A : B);

and have it compile down to

const X = A;

without attempting to serialise the functions themselves. Is this correct? The way comptime.ts currently works is that it runs the expression in a constructed block. But perhaps a new primitive, like

import { conditional } from "comptime.ts" with { type: "comptime" };

const X = conditional(condition, X, Y);

Might work though! I'm also interested in conditional comptime code removal, but not sure about the API design there. I know bundlers already do it, but I'd like for it to be possible in source->source transformations too, for example shipping a version of a library with debugs/traces.

Feel free to open an issue if you'd like to discuss ideas.

The woke reference is to LibreWolf, not Mozilla. The dev labelled themselves "very woke" and declared the project will not be apolitical. They banned someone from their chatroom for their identity/political affiliation outside the chat, and so on.

Regardless of one's political applications, I do agree who you are elsewhere shouldn't matter unless you actually start spewing that in an inappropriate context.

I believe atrettel wanted to be transparent about the nature of their reply more than protecting themselves from jeopardy. Also, this is not unsolicited as OP has asked a specific question to the community.

Are you with Proton? Maybe the documentation you need is just a lock on the sent email that says "Used key for <email> from keys.openpgp.org", and the recipient could also have a cleartext message saying "Encrypted with key for <email> from keys.openpgp.org"?

exit