It was totally a rigged referendum, that bus hoarding propaganda somehow worked and the masses fell for the lies. But a great number didn't and it was barely lost by a few percentage points. David Cameron should have stayed and battled it out instead of resigning.
David Cameron may be the biggest idiot in almost 300 years of British Prime Ministers, and there's been a few beauties. He really could have done a better job with the whole referendum business. Up/Down only. No "by a majority of...". No requirement for a second referendum on the terms of the disengagement agreement. Asking him to stay around would have been like asking the driver that drove you over the cliff to drive you home. And then there was that other beauty, Boris!
My bet is they'll keep subsidizing for a considerable period of time, at least 1-2 decades more.
Most AI companies are just testing the waters with paid tiers right now, their greatest fear with increased pricing is folks reverting back to wikipedia, stack-overflow and other public domain organic activity buzzing back to life; that will kill any RoI potential in LLMs forever. They're playing the wait game instead, observing how the digital sphere reacts to every little increase in price.
If that weren't the case, they'd be pricing at lucrative premiums already and even gotten away in short-term considering the increased dependency in the enterprise world. But that'd be like killing for the golden egg too soon and losing all long-term potential.
Once the folks are so addicted to LLMs that even writing a hello world program sounds like a nightmare and coming up with an article draft feels like reinventing Egyptian glyphs, that's when the real pricing hammer will come.
Anthropic and OpenAI won't be around in 1-2 decades if this is their long term plan. People are not going to revert, but go elsewhere. China is proving that it can be done cheaper.
I've found some basic lifestyle changes to be way more effective at weight-loss and inducing well-being than a drastic chemical therapy like Ozempic. Imbibe at your own risk.
- Intermittent fasting (16x8 or at least stop eating after sun down)
- Daily morning pranayama (or 'breath work' if you prefer that term)
- Daily morning intake of copper utensil stored water (~8 hours or overnight)
- Weekly oil pulling for gum health.
This approach feels a bit stoic and neanderthal initially, less attuned to our modern and progressive society, but as effective as Ozempic in long-run (minus the side-effects or addiction).
If bots are being used to create chaos in society, it really isn't possible that the platforms themselves are just innocent bystanders here. It is technically possible and quite easy for the platforms to block bots if they really wanted to, in fact it's actually in their best interest to have human only organic activity as it increases the platform's credibility and reduces network cost. If they're still letting bots operate and actually post content on their platforms, they're likely in cahoots with the politicians.
> I personally do not like the Javascript frontend ecosystem. It's hacks on top of hacks on top of hacks. But, do you know another way to deploy software that's cross-platform and basically free of gatekeepers?
One way is what I call the "Modular MVC pattern" that involves pure js routing and manual DOM manipulation without using any framework at all. You handle complexity in two ways: by modularizing the "controller" parts into multiple js modules for each route, and "view" parts into multiple HTML partials - and using the event bus pattern if your app gets too complex (as alternative to modern reactive frameworks like react/vue).
Shameless plug: I've tried to implement this exact pattern with limited success in Abhyasa Quiz App[1], a side project.
Not a tailwind geek myself but I think how they justify is "better to have a little extra spaghetti in your html code than create a truck load of spaghetti in your app.css stylesheet."
The alternative to using tailwind here is to define the specific style elements for each one in the css stylesheets yourself with something like this:
.bg-sky-500 {
background-color: blue;
}
Tailwind proponents argue that they avoid this "stylesheet hell" by picking ready pre-defined tailwind classes like bg-sky-500, etc. Plus they also argue that this workflow will increase productivity by standardizing "style mindsets" of your dev team who all will think "blue" means "sky-500" (for example).
Maybe it has use cases in deep or professional design work but for most backend or full-stack devs, bootstrap is definitely better than meddling with this structure.
reply