1. For why would everyone want to use their laptop longer than MacBook lifespan? I'm typing this on a 5+ year old MacBook, which I expect will work for 3 more years. At this lifespan, it will be outdated by all means. I can replace it with a new one at the cost of $1-1.5k. If I had a Framework, I would gradually replace this with new parts? Well, only the mainboard takes a huge portion, or even more, of that. Screens became outdated too, by the way!

2. Repairability. Apple has bad repairability, in terms it glues the laptop from three parts. That means you can't do anything by yourself, but you can get a repair in a day or two in any point of the world. Can you fix your Framework in Tbilisi, Georgia? Last time I replaced the screen on a Mac, it cost me $300 including human work, the same as a Framework display costs.

3. MacBooks are just better in terms of performance and battery life per buck. They also tend to have the best screens, sound, and input. All of these are quite important for a laptop.

I like the Framework premise; I would like to own a Framework as a Linux machine. But we should remember that these are hobbyist laptops with a product/cost ratio, and gimmicky features.

All this discussion, amplified by voices of Apple-quarreled people like DHH, is stupid and kind of harmful – unexperienced people are ending up with expensive enthusiast devices (...or worse, with Dell XPS, you know).

P.S. Please don't bring "computer ideology" into this – there is no walled garden on MacBooks like on other Apple devices. There are no services actively sold to you. I don't know where this argument is coming from. It is just a Unix-based computer, with good hardware and a nice-looking GUI.

That said, I would definitely like to see comments of peope who actually used a MacBook and switched to Framework.

1. Over-reliance on complex concepts and terminology. Let's compare with Vue: `useEffect` vs `watch`, `useMemo` vs `computed`.

2. This useless "clever" stuff also slips beyond terminology: many years ago, Redux was considered the go-to state manager, and it required writing a lot of code across multiple files even for incrementing a number, because its author liked a lot of clever CS concepts. VueX at the same time allowed just to increment that number. Thankfully, nowadays, the React ecosystem is full of sane state managers.

3. React ships without any tools to work with CSS. That said there is no chance you would use React without CSS.

4. React doesn't bother optimizing anything for you. You need to know how and when to properly use or not use these clever `useEffect` and `useMemo`. There is a lot of stuff to know, and there are a lot of folk legends about optimizing React. This is while rerendering is its main purpose. In Vue, the framework makes you always use its tools, and does most of the optimizations inside them. I never thought about manually optimizing a Vue app.

5. The folk legends. React API and the "correct way" to write React radically changed so many times, so it is very hard to understand what is still true today and what is not.

All of that can be summarized into one – React is overly focused on ideas, computer science, and being high-level. And not very focused on actually making drawing interactive HTML on screen simple.

I do write a lot of React, Vue, and Svelte. And when I write React I always need to think about stuff, of which I never would think about with Vue and Svelte, because they already took care about it. And performance wise they are on par.

btw, I wrote a related post some time ago https://www.brachkow.com/notes/what-i-like-in-vue/

Big thing I made recently is moving it from SvelteKit to Hono + Inertia + Vue.

I like SvelteKit, but I was struggling with stability in active development periods, and writing proper tests was very hard due to mocking all the magic, especially outside trivial testing tools.

Now the whole app is straightforward Hono MVC with Vue powered UI. Logic is easy to test, and all UI states exposed in Storybook.

I wrote a custom adapter that makes Inertia run on Hono, and coincidentally same thing was released by Hono author itself as official module, which is great sign for adoption!

So, try Inertia – it is a best of both worlds. You write MVC backend as you like, and use modern JS frameworks for templates.

https://inertiajs.com/docs/v3/getting-started/index

I actively browse Wikipedia in English, Polish and Russian, and see a lot of traces of government efforts.

For example in Poland related topics:

- Russian articles usually have negative stance, and articles have a lot of very strange quotes like wiki editor interviewed some person from 1920 in a bar with a drink. Most of these quotes are either folk anecdotes or made up by author.

Not related to Polish topic – Russian editors are also dominating Russian Wikipedia, and significantly affect important articles for other russian-spoken countries like Belarus, Ukraine and countries of post-soviet east.

- English articles about PLC are actively edited by Lithuanian editors. Polish nobles are renamed into Lithuanian manner, despite they definitely didn't knew Lithuanian and had absolutely slavic names, only by the fact they had any position on territory of modern Lithuanian or participated on event that considered "good" by Lithuanian historicans

While I annoyed by these events, I think it's big win for a country if it can do that. Being able to shape opinions via "neutral" source is a big PR win. And country PR is very important – just look at "nice" Switzerland or Japan, catastrophic PR failure of Israel in recent years, or what oil-rich Arabic world does right now.

What I don't understand is these loud "voting with money" comments. What they are canceling is very subsidized plan to buy something that delivers a lot of value.

There are only two providers that can provide this level of models at very subsidized price - anthropic and openai. Both of them are bad in terms of reliability.

So I wonder what these people do after they "cancel" both of them? Do they see producing less result at same hourly rate as everyone else on the market as viable option?

Here is a breakdown, which was posted on HN few years ago – https://lunduke.locals.com/post/4387539/firefox-money-invest...

I always thought that ugly UIs on Linux are because of good designers do not intersect well with programming enthusiasts.

But looking how ugly same app looks on Linux, I’m starting to think it could be a technical limitation. Can someone elaborate?

[0] https://news.ycombinator.com/item?id=19394399

[1] https://www.reddit.com/r/PhoenixPoint/comments/b0rxdq/epic_g...

But these UI's are occasionally slipping into a countries where tipping is not expected.

This leads to a strange situations like "transaction isn't approved by me because instead of ApplePay and walk away, I need to solve some quiz on a payment terminal or payment will not pass".

Every time this happens, it annoys me a lot which affects my wish to visit this place again.

CD Project makes great games, but gaming industry is all-or-nothing. They already had colossal flop at their previous release. If another flop happens shutting down GOG is clearly would be on a table as a cost cutting measure.

I live in EU for many years, but due to my birth country being sanctioned I can't use any financial instruments like investing or even simplest savings deposits. Getting mortgage or loan is also much more harder for me, even tho I have much better financial situation than average person in that country. Apart of that I need occasionally go to the bank in person to proof the bank that i'm good person with valid documents under the threat of freezing my funds and closing my accounts.

Funniest thing in that is all these sanctions are issued by EU and US, and not by the country I live, where i'm pretty welcomed.

So I would better prefer them playing three-in-row. I think after some time it even would be possible easier to "sell" to them playing some kind of minecraft with grandchildren.

Also, I vividly remember parks in Georgia (country!) crowded with elderly loudly playing chess and domino, instead of watching "who deserved to die by our god-chosen almighty army today" crap.

Most of us were able to earn money to buy a pizza or some additional snack betting on teams, or trading keys. Some exceptionaly lucky or with natural born trading skills were earning serious money — from quater to multiple salaries of an adult.

Maybe because casino-tourism in Belarus made people here slightly less prone to gambling, or maybe parents were not used to gift their children micro-transactions — e-sports betting, gambling and trading was financed mostly via in-game drops, returns from these bets and trades, and of course, sometimes, pocket money (which, on average were like 3$ per week).

That said, in modern times where micro-transactions are so common that you are ok with giving your kid V-bucks as birthday gift, I want say that anti child gambling narrative is a good thing.

2) At that time, and afaik it is true even today — you could use skins as a virtual currency to pay for a real things. It was proto-cryptocurrency/NFT in terms of being KYC and AML free.

This is really big market. There are aritcles on NYT about real life terrorists buying real guns for skins.

But without US-centric sensationalism, I beleive you can still pay for VPN or ChatGPT in very sanctioned Russia in CS skins. This can be also done with crypto (and mostly done now), but crypto has learning curve and you already playing CS.

1. I shared the app with the small audience I have and received some feedback in very unexpected places. First, it was hard to understand how lists work because putting things into lists was an unobvious process. I fixed that by adding DnD that works well both with mouse and touch (turned out it’s two separate APIs). Second, users thought that the screenshot on the quite minimal landing page was the real app, and they clicked on it. The problem was so frequent and surprising that I decided to add something funny for people who do that, as I’m not willing to contribute a lot of time to the landing right now.

2. I underestimated how bad discoverability on the internet is. My expectation was that I would make my site fully server-side rendered, add a basic sitemap to Search Console, and have a few dozen organic users during the pre-holiday season when users are filling their wishlists. In reality, I got zero — not even users, but even visits. So I started actually working on SEO, no black magic but just adding slightly more complex sitemaps, micro-markup, and other stuff which I thought only products competing for the first page would need.

My next steps are to work on getting some minimal organic inflow of users and improving stuff related to auth and user management, which is the most time-consuming part of the work right now.

I try to read everything on the internet via my reader so it is important to me that it:

1. can discover not so obvious feeds like youtube or reddit 2. makes rss feeds for non rss services — in the past it had feeds for twitter, vk and instagram that didn't provide feed. Sadly this is no longer a thing I beleive as such thing as social media public api dissappeared 3. can retreive full text of article

That said I believe you need to think of choosing of RSS reader as about choosing a mighty backend for the feeds. There is nothing difficult in rendering nice text from XML. Real difficulty is in making RSS avaliable on sites that are hostile to RSS (and will became more hostile in future).

And for the chosen backend, you can choose any frontend — just look at RSS apps in app store for your platform. Most of them will support using other backends. Reeder for Apple devices is nice.