cho.sh
2,244 notes
Liked on XI made a mistake. When Jack and I decided to organize this $100K Hackathon, my biggest concern was cheating. Unlike a regular hackathon, everyone participates from home. And because the winner is whoever makes the most PROFIT (not revenue), there are so many ways to manipulate the numbers. So I added a $99 entry fee. One thing I’ve learned from building businesses is that people tend to be more committed when they pay for something. I thought it would filter out spam, attract serious builders, and make the competition fairer for everyone. But I completely missed the other side. 3 years ago, I was a living with my apps. Today, I’m financially free. My life changed so much that somewhere along the way, I lost perspective on what $99 means to someone else. For someone in India, someone struggling to pay their bills, or someone trying to make their first dollar online, $99 can be a lot of money. And those are exactly the people I want to help! I’ve spent years sharing what I’ve learned, reviewing random people’s landing pages, and organizing free meetups around the world. Not because there’s money to make, but because I genuinely love seeing people build things and succeed. And somehow, I was so focused on keeping cheaters out that I didn’t realize I was also keeping genuine builders out. That’s my mistake. So I’ve decided to make the $100K Hackathon completely FREE :) Everyone who already paid got a full refund. I’m still worried about cheating. That problem hasn’t disappeared, and Jack and I will have to figure out better ways to verify profits and keep the leaderboard fair. But that’s our problem to solve. Thank you to everyone who shared their thoughts. Sometimes you need people to remind you of things you’ve forgotten. I genuinely hope this hackathon changes someone’s life. ❤️Liked on XIt’s time to bring back Cafe CursorPosted on Xyo @pendev i can't live share edit a .pen file? it's the most needed featurePosted on XI'm coining a word "Agentsplaining" Agents condescendingly assuming the user don't know fuck and repeating the obviousReplied on X@jayhxmo @raycast Hard to explain. It's the small detailsPosted on X@raycast iOS keyboard is insanely good. Might resub Raycast pro just cuz of thisReplied on X@ishuagra02 I saw a theory that F5.2 is a post train of 5.1, but O5.5 is a distillation of F5.5(unreleased new pretrain) and thats why O5.5 > F5.2Liked on X@anaclumos don't know what is actually improved 👀Posted on Xam i the only one underimpressed with 5.2 fableReplied on X@bvvst great minds think alike https://t.co/YRFWhb1mcOLiked on XClaude Fable 5.2 is out and it's the perfect time to run this god-level prompt on your codebase: "I want you to audit our codebase, is anything here unnecessary, overly complicated in our current setup, or based on weak assumptions? Challenge them. - What can be deleted entirely? - What can be simplified now that unnecessary pieces are gone? Then make the changes. Prefer deleting over simplifying, simplifying over optimizing, and optimizing over automating. This product is being used by thousands of customers, do not cut any corners." This prompt is one I run often and leads to the best results.Replied on X@akshayadinesh19 @bot can we please BYOM for botsLiked on XTo be fair, the Chinese models have a much lower refusal rateLiked on XF*CK IT, im creating a library of AI slop indicators. my feed is full of taste larpers. stay tuned https://t.co/5Muv8nQRm3Liked on XJENSEN! THATS NOT WHAT WE MEANT BY CHINESE MODELS!!!!!!!Liked on Xmy parents had to declare bankruptcy when I was a kid, so they had every reason to pressure me towards a more stable career path instead, they were so patient with me, even as i failed startup after startup for years so getting to tell my mom that everything turned out okay was a really special moment :) for those who can't read Korean, her first message roughly translates to: "Really!!! Congratulations my son. So much :') Thank you God!" i know I've been posting about my exit for like a week now, but it really is a big deal for me and my family! i'll share more about how this all happened and some tactical advice later this week, but for now i'm just riding out all the emotions to quote my mom, thank you God!!!!Liked on X@thefarmers_Dog it stands for Egg GzampleLiked on X🦍 Introducing Memorilla: memory as a modality for LLMs Memorilla turns everything a frozen LLM needs to remember into just 16 memory embeddings ⚡ It uses up to 4,212× fewer tokens and is 27× faster than full context inference while more accurate 🎯 Pushes the Pareto frontier over RAG and agentic memory in personalization, long-document and knowledge QA A thread 🧵:Liked on XThere's a huge product opportunity downstream of Tailscale etc too. At @tldraw we've started designing for "high trust networks" and it's been a beautiful thing. 1. Features that would be a nightmare on the internet are okay on my computer and mostly okay on private networks. Websites that execute user-generated scripts, control production systems, allow for users to send desktop notifications, spend tokens, or directly prompt my agent. Crazy stuff that would only make sense if everyone was in a committed polycule. 2. When everyone on the server can be trusted to have _external_ reasons for good behavior (eg keeping their job, or maintaining friends, family, church, mafia org), the software can be designed in a default social way. Most apps default to isolation, low horizontal visibility, highly restricted collaboration. Makes sense if the social contracts are inside of the app, but if you can trust that they live outside of the app then you can get wild. Example being small group chat names as an emergent comedy phenomenon because anyone in the group can change the name. 3. This can work for commercial products, too, not just internal stuff. Security matters more than ever but the way we've seen that manifest is that more companies are more confident in their own solutions than anything we could provide, to the point where owning data and access is a better value proposition than having it managed. Always has been true for big companies but now even small companies can get a good secure network set up pretty easily, and the hooks we need to build are easy enough. tldraw offline got us started down this road (and shout out to @pendev for first introducing me to the idea of desktop + mcp). We've been bringing that product to private networks and it's been exciting to see how much we can get away with. Keep an eye outReplied on X@saradu birds eye viewLiked on XApplications close in 2 days!! If you have a cool bio idea, and $5-10k will go a long way for you, please apply!!! https://t.co/NCvmrNC53cLiked on XWe've been early adopters of Rust since 2018 and a lot of our infra, voice tech, and even some of the current client is already Rust, the holy grail was getting the whole client there. That means Electron goes away, and so does React Native, mobile keeps native UI but shares app code with desktop via Rust. We hope to get it into testing with users soon™. (And it's not Tauri, it's GPUI, so good guess everyone.) Alright, back to staring at the WoW Forever login screen.Reposted on XOh boy. https://t.co/X7SSskGuGvLiked on XRIP .si domain squatters
220614

220614

Warning

Over a year old. May be outdated

Interesting Websites

Work Note

현재 상황에 대한 이해

  • 은 타사 앱을 참여시켜 플랫폼을 확장하고 OS 수준을 경험하는 모든 과정(웹앱 렌더링, 레지스트리 설치, 프리로딩, 위젯 등)을 포함하는 모든 빌딩 블록을 만드는 것이다.
  • 에서 DOM을 만드는 것은 구현 전략의 일부일 뿐, DOM 자체는 이 아니다.

목표 설정

  • DOM의 재구현이 의미가 있는지 실험하고, 유의미한 전략인지 확인하는 것이 목표이다.
  • 비유하자면, 이미 동일하게 작동하는 장치로 Web View가 있는 것이다.
  • 기존에는 모바일 앱에서 Web View를 제어하는 것이고 우리는 웹에서 제어하는 Web View를 만드는 것이 목표이다. (=가상화.)
  • 이 가상화 환경의 런타임을 수립할 세부 전략을 세워야 한다.
    • 이 세부 전략으로 을 쓸 수도 있고, 고쳐서 쓸 수도 있고, 새로 만들 수도 있고, 폐기할 수도 있는 것이다.
  • 전략적으로 유의미하다면 일부를 폐기해도 된다.
  • 과 JSDOM은 각자의 한계가 뚜렷하다.
    • 하지만 구현 디테일은 참고할 부분이 상당히 많다.
    • 핵심 컨셉은 차용할 수 있다.
  • JSDOM도 마찬가지다. 계속 쓸 수 있다는 것은 아니다.
  • 우리만의 트레이드오프를 만들어야 한다.

티어링: 지원하는 기능의 종류를 정하는 일에 대하여

  • 커버리지(어느 기능까지 지원되는지 정하는 일)과 구현 목표(무엇을 만들지)는 분리하여 생각해야 한다.
  • 티어링이란 이 가 빌딩 블록으로 제공될 때, 아주 필수적인 코어 기능으로 제공될 영역과, ON-OFF 할 수 있도록 토글로 제공될 부가적인 부분을 나누는 것이다.
    • 코어, 코어 플러그인, 커뮤니티 플러그인을 정하는 것.
  • 여기서 중요한 것은 성능, 용량 등으로 티어를 나누는 것이 아니라는 점이다.
  • 티어를 정하는 것은 잠시 미룰 수 있다.

구현 우선 순위를 정하는 일에 대하여

  • 베타 에서 Frame 데모 앱을 돌려보며 터지던 부분들을 나열해 보았다.
    • 이때 Frame Router를 선택한 이유는 네비게이션이 어느 정도 되어야 유의미한 동작을 확인할 수 있다고 판단했기 때문.
  • 가상화를 증명하는 가장 좋은 방법은 가상 환경에서 돌아가는 모습을 보여주면 되는 것이다.
  • 즉, 지금 해야할 일: 데모 시나리오를 만들어 볼 것.
  • 이 세 가지 시나리오에 부합하는 적당한 난이도의 데모 시나리오를 만들어야 한다.
    • 미니앱은 외부환경에 영향을 미칠 수 없습니다
    • 호스트에서 미니앱으로 전환할 때 로딩 없이 즉시 전환됩니다
    • 호스트는 어떤 상황에서라도 현재 실행중인 미니앱을 강제종료 할 수 있습니다
  • DOM의 구현 요구 사항(실행 환경에 대한 요구 사항)은 게스트 앱에서 나올 것이고,
  • 결합부 파트에 대한 요구 사항(예: 닫기 버튼, 최소화 버튼 등)은 호스트 앱에서 나올 것이다.
  • 검증 대상에 특화된 시나리오 예시
    • DOM 퍼포먼스를 확인하기 위해 Throughput이 높은 DBMon을 사용한다.
    • Todo MVC
    • 네비게이션 검증하기 위해 Frame을 사용한다.
  • 종합하여 의 목표를 세우고, 상위 의 스코프를 세우자.

Rust의 사용에 대하여

  • 미니앱 시스템을 만들기 위해서는 부가적으로 패키징, 로케이팅 등을 고려해야 한다.
  • 그 중에서 압축 포맷에 대한 고민을 해야 한다.
  • 이것에 대한 예시로 Web Bundle이라는 예시가 있는데, 이것이 Rust로 만들어져 있다.
  • 이런 것들은 시스템 기반 언어로 작성해야 하기 때문에 Rust로 하면 좋을 것 같다.
  • WASM과는 당장은 무관하다.
Backlinks0

No backlinks found