jwlake

The first season is slow but it really picks up.

Why doesn't the "video card" just come with a processor socket?

Functional components are great in that they are more terse, less boilerplate.

Class components just have more lines, more boilerplate, so they have a higher cognitive load. But when you have state, you have more complexity, you can't just wave your hand wave and make it go away. You need to take the complexity into account.

Hooks are trying to do hand waving. The thing is, once you get to non-trivial use cases, the handwaving stops working. You're better off thinking a lot about where you state lives in your component hierarchy, and then limit your state to where you really need it. Once you do that the overhead of class components doesn't really make that big a deal.

The same principle applies to almost everything in programming, the more thought you put into structure, the simpler you can make everything.

I use functional components only for things without state. If anything has state I use class components because otherwise you go mad. ;)

The correct thing is to just token throttle to the max you're willing to offer for the fixed price. Then when a small minority figure out 1Gbps really is like 100Mbps, then whatever.

Isn't the solution to this just 400 for bad path, and returning a not found is 404 plus body of "entity not found"? Having to always check result: true is by biggest annoyance in APIs designed like that.

That article doesn't actually have enough data to really know. The anecdotes are all just design assist, make things faster from 20 mins to 3 seconds. Not singularity. There are teasers but nothing clear singularity. I think the big problem is they are just using it for fuzzy algorithm optimization, which is clearly not self learning.

Has anyone found the filing running around on the internet and not just the pr dump? The interesting missing bit is the price set on these.

"to purchase, at the then-current exercise price, additional shares of common stock having a then-current market value of twice the exercise price of the right"

There's around 40 million people that might have a problem with that.

I've run quite a bit of analytics on ethereum and have downloaded the entire chain multiple times for processing and it's freely available from multiple providers. All the major API providers (infura, etherscan, etc) have the all the raw blocks available readily.

Some of his points are out of date (given state of the art is old), like royalties and immutable data. See ipfs, eip-2981, etc.

Other parts are very on point, specifically everyone using opensea as authoritative for NFTs, which is crazy town. Opensea has a dog in the fight, and they are very opinionated about what's allowed in the tent and not. Things like etherscan and infura are less scary. I can't imagine building a wallet and depending on opensea for anything though, because your users are not going to appreciate that choice.

Movies usually have several terrible cuts, tv versions are usually much much worse than the bluray versions. Streaming is a mixed bad, sometimes better. Disney+ actually bringing out good versions (IMAX) hopefully will force others to improve.

Older generation fabs for major manufacturers (Samsung, TMSC, others) were heavily impacted by staffing shortages due to covid/lockdown/etc. When staffing is low, the new fabs run 100% and the oldest ones just shutdown.

This caused a bunch of chips that are old and cheap to be complete unattainable, due to a lack of safety stock across the industry. Cars, power supplies, and other "large" things are highly dependent on these older chips, and have very long redesign timelines.

Newer generation is actually simpler, its just demand growth outstripping supply. I'm sure 2020/2021 also impacted the ability to bring more capacity online but probably only to a small extent, these are long term investments that aren't responsive to instantaneous demand.

I've increasingly come to the idea that everyone is cosplaying outbreak, and somehow I didn't get the memo that this was fun.

Wonder how many weeks until everyone in CA realizes everyone has already gotten it.

There are only 2 problems I see with the existing solution in npm.

- "npm add package" puts in a "^ver", which is bad practice

- there is no good infrastructure to pull hash based blobs out of the ether in case npmjs is offline

npm-shrinkwrap has solved repeatability forever, people just didn't always use it. Auto-upgrading dependancies is the big problem, which should have never existed because it is not principled. I'd go further and say that dependancies and devDependances should only support exact versions, and peerDepenancies are the only thing that supports non-exact versions.

What is the author refering to in this line?

"It also helps to shed some light into this “Network 44” that became more famous by recent events ;)"?

The simple answer is public policy always lags the public therefor is always a bad idea to implement NPIs. Public policy should be concentrating on increasing hospital capacity, therapeutic/prophylactic distribution. Presumably never on "lockdowns" or travel bans or masks. People will lock themselves down if it's bad enough, and more importantly at finer granularity and with more equity.

You might be wearing pants wrong.

I think the problem with this article is it makes a ton of assumptions. For an open source dependency used in a ton of projects and platform, -Werror tends to be fairly infeasible. For a specific CI build on a specific platform, it tends to be a good idea. The confounder is always -Wall, which is overkill alot of the time.

The EVM design choices are tightly bound with the on-chain storage of data. On ethereum you pay for reads (less) and writes (more) but everything is very expensive because it's stored in a merkle tree with computationally expensive operations.

Alot of the WASM experimentation has also included changes around how storage is charged. Specifically NEAR does a deposit system where you have to HODL to store data on chain. That allows them to innovate in the runtime and cost structure and still incentivize blockchain nodes.

So it's not entirely gas accounting for computation, its more pricing for storage that probably keeps eth on EVM indefinitely.

Other experimental chains are must more likely to become robust and trusted and more performant and then eclipse ethereum.

Solidity isn't actually that bad language in practice; it's a very simple language.

The EVM on the other hand is harder to justify. :)

NEAR is WASM based. It's interesting but not nearly as "battle tested" as EVM. ETH2 also can't break any backward compatibility, which makes it easier to just keep going down the EVM route.

The people self selecting into positions of power wanting more power?

Only took 12 versions!

Apple's system does not allow a developer to refund a purchase. Seems like the height of half-assed.

There does seem to be some of that in the strategy and article. The odd thing is it doesn't seem to address the elephant in the room which is single threaded sustained memory bandwidth. From my usage it seems like that's the only huge upgrade.

Small amount of googling: https://julianoliver.com/output/log_2015-12-18_14-39

Next time I'm in an airbnb I'm definitely nmap'ing and trying this out. ;)

where to i submit the issue to have it reposted to substack?

I always feel like people that write these articles don't understand that energy pricing is the most regressive tax ever created. The world (read not US only) needs extremely cheap environmentally sound energy production far in excess of current capacity. Specifically China, India, Africa all need vastly more energy production to bring up their standard of living. Even the US would be greatly improved by vastly cheaper energy.

Arguing against nuclear from the future mix of energy seems like it misses the boat global energy requirements and total environmental impact.