Isn't the only EV F-150 the Lightning? The Lightning has always been the sports model, so I can't imagine it ever made sense economically as a work truck.
They reused the name much like they used the Mustang name for their electric SUV. Past Lightnings were single trim level performance trucks. The current Lightning mirrors the regular F150 trim levels but with an electric drivetrain.
It's a little more complicated. The Lightning has always been about performance, and that includes the EV. It'll demolish every other F150 (and most other regular cars for that matter) that doesn't say "Raptor R" on the side.
Grip seems like a bad example since in most cases gripping something a little bit stronger will make your grip a little more robust to an unexpected perturbance (e.g. you stumble, or someone bumps into you). Unless you have good data on how common such perturbances are, how changes in grip strength affect robustness in the face of perturbance, and what drop rate is acceptable, how would you know whether you're gripping things too strongly?
> The isolationist and xenophobic rhetoric of recent years is mostly a reaction to a growing sense that increasingly few Americans are benefiting from global goodwill and development.
I'm not sure I buy your claim that this is the reason for the rhetoric. And if you're right that this is the reason for the rhetoric, it's extremely flawed reasoning.
Diminishing material conditions makes a fertil breeding ground for right wing nationalism (isolationism and xenophobia). It's a pattern being replicated all over the world. UK citizens don't have high heat bills and sewage leaking into their rivers because of privatization and Brexit, it's because there's too many refugees!
Of course it's incorrect, but without the diminishing material conditions, it's a lot harder to get people to drum up the energy to be racist.
Amazon is selling digital copies (or licenses, if you like) of the books, which means they need permission from the copyright holders. This permission is likely backed by a contractual agreement that covers some details about how Amazon presents the digital copies to the end users.
(This of course wouldn't be the case if they were reselling physical books.)
> It's not training on books, but it will answer questions about the book you're reading. Doesn't pass the sniff test.
What do you mean? Presumably the implication is that it will essentially read the book (or search through it) in order to answer questions about it. An LLM can of course summarize text that's not in its training set.
"Reads the book" is the issue, yes. It's possible they aren't training. Vit to be frank, we're long past the BOTD where tech companies aren't going to attempt to traon on every little thing fed into their servers.
Writer and director Steven Lisberger made that claim in interviews, so I wouldn't quite call it an urban myth.
As far as I know, any film can be submitted for Academy Award consideration in any category, then an executive committee determines the eligibility of each submission and chooses up to 20 films to move onto the nomination process.
I don't think this committee publishes anything about its decision-making process, so presumably Lisberger is just guessing based on his impression of industry sentiment at the time.
It doesn't seem significantly more wild than the simpler observation that all these islands are populated by humans. Surely the wild part was that they got there, not that they brought their languages with them.
Correct, their main purpose is ecosystem lock-in. Because why return json when you can return html. Why even build a SPA when the old school model of server-side includes and PHP worked just fine? TS with koa and htmx if you must but server-side react components are kind of a waste of time. Give me one example where server side react components are the answer over a fetch and json or just fetching an html page?
The only example that has any traction in my view are web-shops, which claim that time-to-render and time-to-interactivity are critical for customer retention.
Surely there are not so many people building e-commerce sites that server components should have ever become so popular.
The thing is time to render and interactivity is much more reliant on the database queries and the internet connection of the user than anything else. Now instead of a spinner or a progress bar in the toolbar of the browser, now I got skeleton loaders and use half of GB for one tab.
Not to defend the practice, I’ve never partaken, but I think there’s some legit timing arguments that a server renderer can integrate more requests faster thanks to being collocated with services and dbs.
which brings me back to my main point of the web 1.0 architecture. Serving pages from the server-side, where the data lives, and we've come full circle.
It's an open-source project that started as a fork of SpringRTS. To my eye it looks nearly like a clone of Supreme Commander.
I watched a few ranked 1v1 games on uThermal's YouTube channel (he's a former Starcraft 2 pro who mostly makes YouTube videos about Starcraft 2). Here's the playlist.
Well, when I saw the first Supreme Commander video it looked a lot like Sprint RTS running Balanced Annihilation to me. Right down to how the terrain deformation worked and the command queuing.
Was there any particular reason for the fork? There's a lot of Spring RTS projects but they all use the same codebase.
http://springrts.com/wiki/Games
reply