To retain and recruit talent, and protect from lawsuits (you usually have to sign a release to receive severance/a buyout). Generally only difficult to recruit and highly in-demand employees get these packages - most people over here would also kill for something like this.
Problem is that it's been heavily contaminated with people speculating about who the author is. It would probably be difficult to get an unbiased answer out of it (although who knows - it's crazy that it can do this at all).
Probably because it appears to have been written by an LLM (the post too, but I assume comments are more easily killed by flags (?)). (To be clear I did not flag it myself.)
This might actually be quite nice - the Blender Python API is currently very useful and very touchy. Lots of differences in behavior in headless mode which are hard to debug (because you can't open the GUI to see what's happening, because that changes the behavior).
Yes the blender API feels like it sits on top of the GUI rather than the GUI on top of the API. When you are writing scripts in the blender api you basically mechanically describe the steps you would take in the UI. It can be a little fragile at times.
I've used Claude to write some blender scripts and it's an excellent use case. I look forward to even better claude/blender interaction based on this annonuncement.
I've also used genAI to write script. It works splendid up to a point, then there is absolutely no way to move the needle further. And it's not even close to renders I would ever publish.
That being said, it's about the same for the code it produces for non purely creative things, but for artistic work, I doubt an LLM in between gives any gain. After all, we do have an interface. A human interface.
You can use Copilot Chat* with basically any API provider, and if you switch to the VS Code Insiders build you can configure it to use literally any OpenAI API-compatible endpoint.
Other than that Zed has a similar experience which is pretty decent.
* By which I mean the good one, whatever it's called now - the part of Copilot that used to be a plugin and is now part of VS Code, not the thing that has always been part of VS Code.
Going around a parked car is not merely an inconvenience, it introduces an extra risk of being hit from behind (obviously you should check over your shoulder before moving into the lane, but this is the imperfect real world, and even the act of checking over your shoulder is a small risk) or by a vehicle pulling out of a cross street which didn't see you through the stopped car.
However I agree that there isn't an obvious solution without making major improvements to infrastructure - right now where the bike lane is just paint everyone parks in it (Uber, taxis, delivery drivers, etc.).
It's also possible to use a feature that is present on the bikes, even if rarely or never used by urban cyclists: braking and waiting for the passenger to drop off, before continuing for your destination.
Something car drivers and pedestrians do, usually.
Not in my city. Taxis and ride shares tell you to get out on the right hand side so that you don’t get swept by cars passing you on the left.
Also often difficult to tell as a bicyclist how long that car will be sitting there. Sometimes it’s a delivery or pickup or something inane that will have you looking like a doofus for waiting.
No. Going around a parked car is a basic ability you need to have as a cyclist.
If you can't do that safely, then you have no business riding in the first place.
Looking behind you is not optional, as you seem to suggest it is. And if it is actually a "small risk", then you are going way too fast.
Again -- if you don't have the environmental awareness to go around a parked car, then you shouldn't be riding a bicycle in the first place. Full stop.
This comment assumes a high mix of cars and bikes in an environment of unseparated traffic.
With literal decades of near daily bike riding behind me I've rarely had to maneuver a bike or a car around a parked car in regular (not US) traffic flow.
It doesn't matter how often you have to do it. It's still a basic ability you need to possess.
And yes, my own experience comes from Manhattan, where that's something pretty much everyone has to do on a daily basis. You've got double-parking everywhere.
But even if you don't need to often (lucky you), the idea that this is somehow something unusually unsafe just doesn't hold any water. If it's unsafe for you, you have no business being on the road. You are a danger to others if you are unable to look behind you when changing lanes.
$1.47/M input, $3.48/M output, open weights (MIT license), and competitive with the frontier on their selected benchmarks. Big if it holds up on real-world tasks.
I'm in the US and it's showing a 100W panel for USD 37.21 (free shipping, including tariffs but not state/local taxes).
Also the panels Carter installed were solar water heaters - in 1979 solar photovoltaics were just starting to expand beyond satellites and cost like $40/watt.
SynthID survives basic transforms including screenshots/photos, although it can of course be defeated. Even still it helps with the laziest fakes, which there seem to be a lot of - I've seen several quite widespread misinformative images over the past couple months that failed a synthID check.
Anyways I think approaching the problem from both directions is probably good.
There are a couple of AI-esque misspellings - in the More Myth than Menace wolves image, on the right in the "at a glance" section, it reads "wolves aarely approach people," and in the Typography image the text in the top right is "Type connncts us all."
But yeah the quality is remarkable, and rather scary.
reply