knubie

I've been using dark reader on mobile safari for years.

How did they bend the knee? I must be out of the loop on this. Aren't they still owned by a Chinese company?

Reminds me also of Andy Matuschak's "working notes" project.[0] This kind of UI feels very natural. I've often thought about how this kind of UI might work in a browser, e.g. wrt tabs/history.

[0] https://notes.andymatuschak.org/About_these_notes

At least among economists it is not that polarizing. Most agree we should get rid of corporate tax. [0] In reality a corporation cannot pay taxes any more than a table can. Only people can pay taxes. So who pays the corporate tax? It must come from the corporation's consumers, employees, or shareholders (or some combination thereof). Raising the corporate tax is just a sneaky way of raising tax on one or more of those three groups.

[0] https://www.npr.org/sections/money/2012/10/18/163106924/a-ta...

Going from parinfer to editing without parinfer is kind of like going from vim to an editor without vim bindings. In other languages I find myself instinctively moving or editing text around expecting the brackets to magically rearrange themselves, only to be disappointed when they don't.

> The electron part isn't the bloat but the web part.

The bloat part is the bloat. Web apps can made to be perfectly performant if you are diligent, and native apps can be made to be bloated and slow if you're not.

Also an example gist: https://gist.github.com/richhickey/fbc1439372b1f5319bb37aa19...

And documentation in the namespace: https://github.com/clojure/core.async/blob/master/src/main/c...

I think the consensus is that it is not really mature enough for general adoption. Also, most people prefer to use one of the specification libraries that are available (spec, schema, malli). These allow you to do a sort of design-by-contract style of programming.

> What I don’t understand the advantage for “state management”. Like, you build a new state object, and then mutate some pointer from prevState to nextState… that’s what everyone else is doing too.

Clojure's real super power is its reference type(s) (in particular the atom). Rich does an excellent job explaining them in this video: https://www.youtube.com/watch?v=wASCH_gPnDw&t=2278s

I think these words will make more sense in the context of Pathom.

https://pathom3.wsscode.com/

Accrding to the wikipedia article you referenced, the OECD data is already adjusted for purchasing power parity (PPP), which is a cost of living adjustment. [0]

[0] https://en.wikipedia.org/wiki/Disposable_household_and_per_c...

From that wikipedia article:

> It may include near-cash government transfers like food stamps, and it may be adjusted to include social transfers in-kind, such as the value of publicly provided health care and education.

Additionally from the OECD website:

> Household adjusted disposable income additionally reallocates "income" from government and Non-Profit Institutions Serving Households (NPISHs) to households to reflect social transfers in kind. These transfers reflect expenditures made by government or NPISHs on individual goods and services, such as health and education, on behalf of an individual household.

> Even typos like `object.detail.name` vs `object.details.name` cause runtime errors, or calling a function with the wrong number of arguments or in the wrong order, some of the most trivial bugs you can think of.

In Clojure, a dynamically typed language, referencing a var that is not declared, or calling a function with the wrong number of arguments will result in a compilation error. You don't need static typing or type annotations for this.

> I don't understand how someone can dislike writing type annotations so much that they're happy having their time wasted like this when automated assistance is right there. To me, it's like not wanting to use a spellchecker when writing an article, or opting out of syntax checking code before it's ran.

It's not about liking or disliking, it's about "wasting time." Spell checking and syntax checking are free, annotating everything with types and maintaining them is not.

> but when easily preventable problems happen

easily preventable is doing a lot of work here. This is assuming the types are already written and never need to be maintained. How often does the type checker catch a problem with the code vs the type definitions themselves?

This is possible already with tools like difftastic.

https://github.com/Wilfred/difftastic

> or just skip some days and have it adjust accordingly, instead of just leaving me with a huge back log.

Unfortunately memory does not work that way. You can't just put a pause on forgetting (if we could we wouldn't need spaced repetition in the first place). The backlog will continue to grow because memory degrades over time (without review). The backlog simply represents the cards that have a less than X% chance of being recalled (where X is usually 80-90%).

Hey sorry about that. I will take down the old FAQ, or at least redirect it to the new one. The other thing not mentioned in that section of the FAQ (that I will add now) is the re-review phase. When you miss a card during review it will go to the re-review queue. Missing it again in that phase will reset its interval to 1.

Since I created Mochi there have been some new algorithis developed. Most notably FSRS [0] looks promising.

[0] https://github.com/open-spaced-repetition/free-spaced-repeti...

I think spaced repetition can be very helpful in language learning, but the author's plan of finding a pre-made deck of the most common 5,000 words is probably the worst way to use it.

A much more effective approach is to create vocab cards yourself as you find new words through your immersion. Immersion could be anything from watching content online, to reading, to conversations with native speakers. From here you can skip the 500 or so most common words because those will appear exponentially more frequently and don't really require spaced repetition if you are regularly immersing.

Also if you're not an engineer, or you don't want to fiddle with Anki plugins you can use Mochi [0] which has built in support for text-to-speech, dictionary lookup, transcription, etc.

[0] https://mochi.cards/

If this kind of thing interests you, you might also like John Dewey's Art as Experience. It is among Paul Rand's favorite books, but be warned it is quite dense!

> That's 0.016% of their income, if anyone was curious.

Is that 0.016% of their global income, or just in Brazil?

Curious what the source of the quoted portion is, if I may ask?

Why not rama/defop and rama/defn?

Been using pikapods for years and have nothing negative to say about it. It’s an amazing value.

The central bank raised interest rates.

I would guess that most people who care about aesthetics don't use Windows. So the only alternative is Mac, and it's the people that care about aesthetics who are the ones that are going to create & buy good looking software.

Check out Mochi if you’re looking for an alternative. It probably ticks most of your boxes already.

https://mochi.cards/

> The author should be embarrassed and ashamed that they put out such a poorly researched article.

Cue the “Your music is bad and you should feel bad!” meme.

Seriously, though, providing constructive feedback is fine, but telling people they should be ashamed and embarrassed is a step too far.

Not OP, but I develop Mochi [0] which is a spaced repetition flash card app that has text-to-speech and a bunch of other stuff built in (transcription, dictionaries, etc.) that you might be interested in.

[0] https://mochi.cards

The iPhone is like a vehicle (car, motorcycle, John Deere tractor, etc). iPhone apps are like after market vehicle parts.

As a vehicle owner I'd like to be able to have a choice whether I want to install OEM parts or after market parts. The after market parts might be cheaper, or have features that the OEM parts lack. I would like to be able to purchase these parts without a 30% markup that goes to the car manufacturer.

As an iPhone user, I'd like to be able to install apps on my iPhone without having to pay the iPhone manufacturer a 30% markup.

I realize that this analogy doesn't directly address the issue of whether Apple has a monopoly on the market of iPhone apps, but it's how I think about it as a consumer.

I think a better analogy would be something like installing aftermarket parts for for your vehicle.