migueloller

Omarchy has been fun to play with and perhaps is a contender against macOS for some developers.

I find it amusing the level of engineering that seems to have gone into this hand contrasted with the absolute AI slop in this blog post.

Let’s not be silly. If there are 10 people each with 10% and the company grows by 93%, then everybody’s shares, including the founder’s, grows by 93%.

The square-cube law strikes again!

https://en.m.wikipedia.org/wiki/Square%E2%80%93cube_law

I believe their target price is $20k. No idea if it costs that right now, I doubt it.

Matt Levine’s writing on this is right along this line. It delineates between liquidity and solvency problems. Worth a read. https://www.bloomberg.com/opinion/articles/2022-11-10/ftx-is...

What are your thoughts on the Fluent Forever method, specifically the part that going through the effort of creating your own study materials is an integral part of recall and internalizing new words/knowledge? It's definitely attractive to have a lot of the "manual work" be automated, but maybe it's a necessary effort to cross the chasm that is intermediate language learning and perhaps most people stay at intermediate levels not because of the lack of a tool but because there's a natural filter with how much effort is required to go from intermediate to fluent.

I've been "stuck" in intermediate Japanese for years now after being on and off multiple times. Got to 1.2k kanji, "ok" grammar and ~3k vocab words. Perhaps something like this is what's needed. I've been wanting an "instructor" that can do this sort of indexing for all sorts of content like TV shows, movies, books, articles, etc.

I started reading Crafting Interpreters [1]. It's great so far!

[1] https://craftinginterpreters.com/

Since segments are determined by folders, you should be able to do `/layout/page.js` for a `/layout` route.

I agree 100%. It can’t just be a UI on too of CSS. At that point just write the HTML and CSS...

I believe you can still do this in Next.js with some extra work to exclude the JS bundle. For example, you can use a custom `_document` page and exclude the `NextScript` component [1]. It would be nice if this was supported as a first-class concept, though.

[1] https://nextjs.org/docs/advanced-features/custom-document

I know the HN comments section is notorious for criticizing solutions they don't like because they seem too complex or unnecessary for them [1] but I'm honestly surprised that's happening with Next.js/Vercel here.

So many are saying that this could've been a static site distributed by a CDN. That's what a Next.js app on Vercel does by default! Unless you use `getServerSideProps`, Next.js will create a static site at build time and when deployed to Vercel it will be hosted on their CDN. Spending just a bit of time to understand why Next.js is so popular would've made that clear to most people here. But I guess that's not as easy as just criticizing it for bloat without knowing how it works and moving on?

[1] https://news.ycombinator.com/item?id=9224

It was a static site. That's what Vercel and Next.js does by default. If you don't use `getServerSideProps`, Next.js will generate static pages at build time and Vercel will serve them from their CDN.

If you like this type of stuff, Paul Henschel shares similar content on Twitter [1] and it's absolutely amazing. For example, incredible stuff like this [2].

[1] https://twitter.com/0xca0a [2] https://twitter.com/0xca0a/status/1357346054635544584

I was pleasantly surprised by the list of "fundamentals". Here I was, expecting something rather specific about the discipline. And I'm so happy whatever I was expecting wasn't what was there. The qualities described do seem like true "fundamentals". It's a human effort after all.

Kleppmann, et al.'s paper on OpSets [1], a specification for building CRDTs with support for an atomic tree move operation, was the best one for me.

Automerge [2] implements a variant of this.

[1] https://arxiv.org/abs/1805.04263

[2] https://github.com/automerge/automerge

Well, I guess you could say that if the store was run by robots so you didn't have to pay employees and if the shirts were made out of thin air so that there are no COGS. I'm not trying to be facetious. I think the distinction between marginal and fixed costs is important here because it's all about the feedback loop for aggregators. And one can think of marginal costs as "friction" in this loop.

That being said, perhaps aggregation theory won't be complete until Ben considers fixed costs in addition to marginal costs, which I believe might be your argument?