I've used Laravel since v3. Taylor's ego has started to tick me off in the last ~5 years. And, I feel like him buying a Ferrari made his priorities apparent. I'm not sure what happened to making a framework that had the nuts and bolts included out of the box. But he's clearly moved from "build a framework" to "build a platform" that drives money to his pockets.
Ignoring tariffs for the moment... No one should be shocked that Amazon would do this.
Remember back when it was controversial to apply sales tax to online shopping? The biggest lobbyist against it was Amazon, which they marketed as fighting for the market against the government. Then they got big enough to survive a reversal ... and swung the other way to weaponize the law against their smaller competitors.
They've done a lot more than this, including creating their own brands to inject into a successful niche product or segment. They did all that off of sales/product data they aggregated from all sales on their platform.
Amazon is a dirty player in the market, and everyone should remember that.
Upvoted because we’re seeing the same behavior from all AI and Seo bots. They’re BARELY respecting Robots.txt, and hard to block. And when they crawl, they spam and drive up load so high they crash many servers for our clients.
If AI crawlers want access they can either behave, or pay. The consequence will almost universal blocks otherwise!
Okay, but why not work on making atmospheric methane more useful/practical? CO2 is less of a warming influence than methane, and there have been huge natural gas leaks (of methane) in the last 10-20 years. Even MIT admits that Methane is more important: https://climate.mit.edu/ask-mit/what-makes-methane-more-pote...
So 5,000 qbits to crack a 50 bit prime key. That’s an interesting factor. Assuming a similar scale, 204,800 qbits would crack RSA 2048 keys. I’m curious why it scales to needing “millions” according to those researchers.
Maybe you misunderstand the market my employer serves?
We've built sites for clients both huge and small. Our clients like WordPress because it's well supported, easy to roll out, and easy to find someone to work on. Lots of people have experience with it, from having their own blog.
Even infrequently updated content can go through a logjam of revisions. And this is the failure of WordPress's versioning model: there's no way to "check in" a revision. So you can't mark what's approved/reviewed. Instead of a "check in" that nukes the middle revisions ... now you have 5-7 revisions where someone updated a button text.
Add in ACF fields (which uses approx 2.5 rows in post_meta PER FIELD) and now you've got a complex page with lots of rows that build it up. Now each "revision" is 1 post row + 20 - even 1000 post_meta rows. You see the problem.
Over time the DB bloats, and the index isn't partitioned in any way. That page a cheap dev built to query something? Runs 5x slower after a year, and the client doesn't know why.
The only reason we use WP over other platforms is: support, maintenance, but most importantly to the client COST.
I have used and developed in Wordpress since 3.2. Mullenweng is a dictator and maverick, and I’m not convinced that he’s good for the Wordpress ecosystem.
But neither are highly customized WP hosting platforms.
Revisioning, especially since the post_meta table was added, is a huge burden on the DB. I’ve seen clients add 50 revisions, totaling thousands of revisions and 200k post meta entries. Important enough to call disabling it by default a “cancer”? Chill out Matt.
Wait, so they added 30g of erythritol and observed negative impacts? Most the time I see it around 7g plus other sweeteners. It’s almost never alone now.
I bet they need to look at 30-45g sugar harder now. Maybe uncover some of that (big sugar suppressed) research that it causes heart disease.
I think this flag was added because a lot of these sex workers want to post pictures without flagging their sensitive media. Then they dog pile replies on all the trending tweets, and people find the adult content.
Any time that happens to me, I flag sensitive content. And then I block the user—so I don't need to deal with it.
I see this as punishing people who're not following the terms, not gatekeeping.
> Please don't use HN primarily for promotion. It's ok to post your own stuff part of the time, but the primary use of the site should be for curiosity.
You're simply posting your podcast as self-promotion of each episode, assuming that we're interested. I suggest you try a "Show HN" approach, and let _others_ post links to episodes they're interested in. If you don't, you'll hit a wall for self-promotion and get flagged/banned. (Eventually.)
Tailwind is also bad if you do know how to use it. The need for an atomic abstraction off every combination of property and value… is not a sign of skill or good design.
Not okay.