stevebmark

I'm really into audio production, and I would re-record the video without using a mechanical keyboard, and ideally not in an echo-y room. It's not very watchable right now. In addition to using a noisy keyboard not appropriate for video recording, you type very hard / angrily. Switching to a quieter keyboard with low key travel might help you prevent RSI in the future.

Very happy to see the punishment start against Matt, and I sincerely hope it continues and escalates. Not wishing for the end of WordPress, but Matt clearly needed to go a long time ago, and repercussions for his constant terrible actions will hopefully force him out.

It's intuitive and obvious that nothing remotely like a Boltzmann brain has ever existed nor will ever exist.

The misunderstanding comes from the common, but fundamentally wrong belief, that an infinite universe means infinite possibilities.

Start Your Own Corporation (Garrett Sutton, 2012) https://www.amazon.com/gp/product/1937832007/ . Big focus on "charging order protection" - if you are sued and lose, states like Wyoming with charging order protection mean that you have to give up future profits of your company, but you are not forced to do anything to actually generate future profits. This also means that lawyers won't get paid as easily for lawsuits, since they aren't sure if/when they can actually get money from the proceeds, which may make lawsuits less likely.

No one knows what San, EPD, EPDSan, Sanepd, Kep, etc, are. No matter what the word, you have to learn it, and it's a small one time cost, and you're done. The additional cognitive load to learn a made up term is negligible.

I see his point about the "fediverse" and the potential benefits of anyone hosting their own message board, that has interoperability with other message boards, aka Mastodon.

We've seen it though, Mastodon's model is garbage, and they lost from the start. No one wants horrible Reddit style mods ego tripping over their own echo chamber. There is no future for Mastodon.

To the point of the article, the real question is if we'll see more atmosphere hosts (aka using a PDS other than Bluesky's) and more applications built on the protcol. And I think the real test will be if anyone ever builds their own relay that gets popular.

Bluesky's model is still better (more open, unbiased, harder to censor) than Mastodon/Threads/X by default, and yes it has a long way to go, but we've known that from the start.

Your response is a lighthouse sized red flashing light to never use your tool.

Rubocop is one of the worst Ruby tools there is. Flog and reek are also unhelpful, but Rubocop is style nonsense that doesn’t belong in a linter. The ESLint community used to be big on useless opinion based rule overload, until everyone realized how bad of an idea it was.

The human body doesn’t indiscriminately burn its weight in calories as fuel. Energy intake and expenditure is complicated. If someone expends energy through using up their stored glycogen, as most of us do, that may not use energy from fat mass.

I don't agree React is good for game development, and I also am surprised by the title of this blog post compared to what you actually built.

To be clear, the entire video is adding a textbox overlay to a non-React game. The actual game is not driven by React at all, it's driven by "kaplay" as you can see imported here: https://github.com/JSLegendDev/react-kaplay/blob/5ee7d69ac86... and all the sprites and controls are set up independent of React https://github.com/JSLegendDev/react-kaplay/blob/5ee7d69ac86...

React is very challenging to use with game development, and probably not worth it. This blog post doesn't get into the reasons you would actually want to choose React for gamedev, so there's nothing to refute. But before you choose React, consider:

- React is fundamentally inappropriate for a 60fps game, both because of the need for re-creating immutable data every frame causing a lot more GC, which will slow down your game, and because the component render process is always slower than imperative mutation. So you have to bail out of React, and forego immutability, to get performance. Both react-three-fiber and react-spring sidestep React rendering entirely to get 60fps!

- Think about what goes into a game. The content is probably 100% dynamic. Making a React component is easy when you're hard coding the contents, or have limited branching (like if the user is logged in). In a game, displaying components is purely dynamic based on state. So you'll need one or more components that do something like

    {currentLevelObjects.map(obj => obj.type === 'player' ? <Player ... /> : obj.type === 'wall' ? <Wall ... />}

and React clearly offers no benefit here. For the record, most react-three-fiber demos are static scenes with hard coded components. If you want an actually fully dynamic game, based on the output of a level editor, you're going to be in trouble. And god help you if you need to consider building a level editor as well! Building a level editor and asset pipeline will take up 90% of your efforts, you'll build a bad one, and give up eventually.

In the year of our lord 2024 I am baffled that anyone doesn't know about the protein content of quinoa, oats, and other starchy grains.

The only relevant study linked in the article is https://www.thelancet.com/journals/lanepe/article/PIIS2666-7...

> Plant-sourced UPF contribution showed a positive association [with CVD risk]

The study is using an existing dataset on food recall. That doesn't necessarily the results are correct or incorrect, but it's lower on the pyramid of science quality. There is nothing else of substance in this BBC article.

To this day Zod is still a huge PITA to use. See https://github.com/colinhacks/zod/issues/372

"No formal definition" includes where we are today, not the original, outdated idea. By the original (not useful) definition, an "available" distributed system can return a response 10 years later, which is not helpful nor relevant when thinking about distributed systems.

In distributed banking back-ends, if one of your datacenters goes down, you don't take down the other one for safety. You don't force global consistency/linearity of all transactions before allowing UI updates. There are delays in financial reconciliation all the time, the important thing is they are eventually consistent with a ledger, not that if one thing fails, you stop the train. And the reality of distributed systems is things fail constantly. Hard drives, networks, bugs, clock drift...

This is in contrast to something like a supercomputer, or a distributed map-reduce job, where if one node fails as part of a distributed process, it will corrupt your data, and you have the luxury to stop the whole thing, fix the issue, and restart the whole process.

I prefer the walkthrough of the CAP theorem in “Designing Data Intensive Applications,” which says that the CAP “theorem” is an undefined and generally unhelpful concept in distributed systems. “Available” has no formal definition.

And it’s confusing that it’s three letters, because it’s not “choose two”. It’s not that a system is “partition tolerant,” it’s if there’s a network partition, you choose availability or consistency. And obviously you choose availability for the distributed systems you most commonly encounter.

I don't think this article is well written, it doesn't really articulate a point other than it's not PHP because

> we've developed solid principles for building UIs

There's not really any substance to this statement or the paragraph it's in. I would skip this article entirely, and I think a much more profound view of this concept is "Mind the Gap" talk by Ryan Florence about dissolving the concept of the network and explicit code needed to manage that: https://www.youtube.com/watch?v=zqhE-CepH2g

I am also miffed that the criticizers of React = PHP are often Rails developers who completely overlook that Rails is PHP on cocaine, it is implicit, untraceable database calls sprinkled across templates, and the more use the worse it gets and it quickly becomes un-optimizable. At least with React API calls are explicit, not magic!

I'm guessing that Forbes Marketplace offers revenue sharing with each website they make this deal with, so it's profitable for all parties. Is there actually an issue here - legal or ethical or deceptive? This seems like business as usual. Is the main complaint that the integrity of these news websites is weakened by having affiliate marketing? Asking seriously because while no one likes ads, I'm trying to understand what the moral/ethical implication of this is, if any.

Content moderation and visibility is a much more interesting question and space in BlueSky/ATmosphere. It's hard to care about the Twitter nonsense now.

What is the intent of allowing arbitrary document assignment to any other global user in the system, with zero default security checks in place? That seems like a fundamentally terrible idea. Other sharing systems require explicit steps to share documents between users (sharing a Google doc with an email address, for example), and it's a very controlled workflow. In Firestore, user IDs are global, and you can arbitrarily give them data? Even if you can get around this with specific security rules, why is this even a thing in the first place?

It's hard to empathize with the people mailing that much cash. It's an inherently careless and risky thing to do, and mailing that much cash is very obviously (and ironically) done to avoid taxes and legitimate business transactions.

Hopefully you've already come across myopic defocus lenses and low dose atropine in your reading about myopia. Overfocus in peripheral vision is a known trigger of myopia progression.

This doesn't really matter. We already know how this plays out because we've seen it on repeat. Bluesky gets a surge in users, then no one stays, no one uses the platform. They're missing too many features for Bluesky to be worth using right now. The most obvious one is video: no one wants to use a social platform without video.

LastPass, Keeper, or 1Password. This is a fully solved problem you don't need to ask SO about.

Pretty good indicator of the nonsense hype bubble of AI!

AT Protocol aggregators (“relays”) can choose their own content moderation policies. It’s possible that if there are multiple relays, and one of them doesn’t block violent / hate speech, the government would ban that relay and corresponding domain, and others could continue to thrive.

Mastodon was dead from the start, it isn’t in the running.

Threads has too big of an image problem to overcome. No one wants Instagram for Twitter.

Bluesky is the only platform currently that has a chance, but it’s an under funded, tiny team who can’t ship on time. Bluesky will see a surge in registrations but no change in DAU as they still haven’t supported video, so no one will stay on the site.

Strongly agree with this recommendation! The Manager's path is the most useful write-up of technical leadership qualities I've come across so far.

No settlement should be granted here, on principle. The law should not protect those that use an asset designed to subvert the government.

This is fairly obtuse longform writing with no obvious message. What is the intention of sharing this?