rendaw

Tangentially, I wonder why browsers can't store more than N history items... even from the same session.

You're acting in bad faith attaching "every change" to what the parent said.

But this isn't that crazy? Most businesses require government approval for changes that have community effects... that's the entire point of government. Stuff like construction permits and regulation around structures, water usage, pollution, building architecture. Mining companies are required to assess environmental impacts. Companies making RF devices need to get confirmation on how the devices affect people and other devices.

And that's not even considering market share/monopoly status, which also regularly invites more scrutiny.

Notably, nothing to do with jellyfish.

This is an absurdly bad take.

https://www.europarl.europa.eu/news/en/faq/9/plenary-session...

Plenary sessions of Parliament take place 12 times per year in Strasbourg and last four days

There are 48 days in sessions over a year. You're saying that it's too much to ask MEPs not to take holidays during those 48 days? Am I missing something here?

https://go.dev/blog/module-mirror-launch seems like a better source.

It seems to imply the reasons were optimization and to protect from disappearing dependencies. It doesn't imply that there were any hidden dangers to git.

I think it's very possible that google simply thinks speed is more important than decentralization. And for google's purposes, a google-owned cache is probably a safe enough hedge against disappearing repos (read: if you're not google you'd need to evaluate this risk yourself).

Edit: Discussion from the time here: https://news.ycombinator.com/item?id=20837753 - in that thread too people don't really know why the proxy was needed (or like, "is it really just for speed? but it isn't particularly slow right now"). One additional reason is analytics collection.

Most of those deal with downloading large centralized indexes using git, not individual packages.

The problem was that go get needed to fetch each dependency’s source code just to read its go.mod file and resolve transitive dependencies. Cloning entire repositories to get a single file.

Then it needs to compile the module, right? It's not downloading it twice.

Grab’s engineering team went from 18 minutes for go get to 12 seconds after deploying a module proxy.

...

GOPROXY became the default in Go 1.13.

The way this is written it sounds like go builds were extremely slow (18 minutes) so go adopted a proxy to speed things up. But Go 1.13 was released in 2020, and the blog post about 18 minutes is from 2023. There's no link to anything about GOPROXY.

The vcpkg example also isn't a git issue, it sounds like just bad engineering from Microsoft.

I'm willing to believe there are issues with using git, but that article is a letdown.

a better, cleaner Markdown alternative

What makes it better or cleaner? It isn't explained anywhere on the page. It looks about the same as markdown to me.

Are residential proxies illegal? Why is the FBI involved with civil actions?

This is terrifying... are there any other decent indie music marketplaces? And even more, why kill this? How could it possibly not have been profitable?

TBF the presentation as a whole makes a lot more sense than the 4 slides out of context.

Is a small number of people with huge amounts of money investing in things nobody wants better than lots of people with small amounts of money investing in things they want?

Do you read all ~50,000 then? Just with the ranked ones first?

Or are you using it to screen? I'm confused.

I did not say that management doesn't care about productivity. To be clear though, I did mean to say upper management.

This is obviously wrong. Management has never cared about how engineers do their job. There's never been a push for any other productivity boosting technology: better languages, better editors, automated refactorings, paid code intelligence tools, etc. But suddenly AI comes along and the CEO says "all developers need to write code entirely with LLMs".

Why do you need gvisor and not just bwrap? Is this a "more is better" thing?

It's more than just reproducing the standard flavor. By not measuring sometimes you'll get something very good, but because you didn't measure anything you won't know what you did that caused it to be good and won't be able to do it again.

Measuring doesn't preclude experimentation. You should copy your recipe, mark what changes you plan to make, then try it. If it works, you have a record. If it doesn't work, you can add a memo to know not to try that again.

I've thought a lot about how to characterize the difference between 3D and hand-drawn stuff. I think the core of it is:

- With hand drawn animation, you draw what you have in your head, first roughly, then you refine it

- With 3d animation, you first need to model everything, then rig it, then work with the bone system to get the motions you want or else mocap, and then set up rigs and stuff so that the mocap actors can do crazy movements, etc etc. Then maybe undo some of the scaffolding the 3d software does: disconnect bones, fake perspective. You have to fiddle with lighting, textures, etc. Or you don't, and just go with whatever's easy to do in the 3d software.

Which means that spontaneity and emotion, like I think this guy's arms should be all wiggly here, are lost. Yeah, you can hand animate then 3d animate on top of the hand animation, but in an industry that's using 3d to cut costs and not because it looks better, that's not going to happen (in any way that keeps the spontaneity).

3d is awesome in that once you've done a huge amount of up-front prep, the rest is easy to iterate on and tweak, but that's a large tradeoff.

I thought that this is one area where I think AI could be a force of good. Keep the animators doing the rough sketches, and AI comes up with the lines, handles the filling, and maybe adds colors with a guide. I haven't seen this yet.

---

I'm not sure I agree on the mentorship parts. IIUC all the major studios and famous animators weren't taught by someone. All the studios have unique flairs that they came up with just by playing around and copying Disney. And they got there without drawing hundreds of thousands of in-between frames for someone else.

I think that being taught the correct way to animate based on existing productions probably also reduces creativity in the field.

I wonder if the earlier creativity was due to voids though, and now that there's some amount of saturation it's harder to break in, or if somehow the increase in revenue from global interest somehow increases stakes and causes more downward pressure squashing out experimentation.

---

There's a lot I don't get about this article though. It says the demand is way up, but the treatment and pay for animators is terrible... why? I didn't see it addressed. Japan has a long history of "non-monetization" though, like refusing to sell digital music overseas, or regional restrictions on streaming content.

---

Lastly, I think there's still a lot of indie animation that gets glossed over. There are lots of independent animators making animations for music videos, for instance, or releasing small animations. I don't know if that grows into larger productions, but there's a level of creativity you'd never see if you just watch televised anime.

There's a lot I don't understand here. How did they come up with 350? I doubt there are any people who own more than 10 houses for personal use, and this is 35x that.

What's to stop people from just making multiple corporate entities? Or investors below the cap buying properties and flipping them to institutional investors above the cap bypassing the cap entirely?

This has come up several times before. It's not well cited. I read through it myself and even if the math is right, the application of the math seems incorrect.

The original data was a small number of studies with a small amount of old (1980s?) data that found a slope with so-so correlation.

The revised math finds a much smaller slope with what appears to be much worse fit to the same old data. The data was nearly horizontal before, but after the math changes it's much further away from 0.

The original study was making predictions near the data. The revision is doing massive extrapolation, far away from the range of what any of the studies tested.

I'm not a statistician, but it's not surprising to me that it's being ignored.

Nixos can cross build os images for Le Potato with device tree stuff: https://hub.libre.computer/t/nixos-for-aml-s905x-cc-le-potat...

Yeah, the first three work for me too. (just realized my original comment was kind of ambiguous)

Somehow the extra motion seems to reduce the illusion of depth, it just seems like a disjointed animation to me.

I think presumably Zebrafish aren't prone to retina cancer.

Some photos would be really awesome. What does a view in an area that passes the test look like compared to one that doesn't? 3 trees doesn't sound like a lot, I don't have a good mental concept of this.

True! My position is probably biased because I'm making stuff where I want maximum client compatibility. That's a good point.

What happened in the end?

I've been following the Japanese early gaming scene, which had a lot of parallels to the west. They had NEC PCs running DOS, and there were a lot of games for the systems. Some of them had smooth scrolling. Did they come later? Did they copy ID Software's approach?

GP's point is this isn't the 2nd car, this is the 41st car. If they had 1 car it'd be a 2x increase. If they have 40 cars, the only way the 41st car would lead to a 2x increase is if that single car cost as much as 40 other cars.

That's what the post you're responding to was asking.

The same with unit tests, they're best suited for problems where the specification is much simpler than the implementation. A sorting algorithm can be long and complicated, but a unit test just needs to present unordered input and assert that the output matches ordered output. A sorting algorithm is also well suited for formal verification.

If you're rewriting the implementation, I think it's probably not a good use for unit tests or formal verification.

As another commenter said, unlike unit tests which cover a specific case, and where you need multiple tests for edge cases and both positive and negative results, formal verification will cover all cases.

Both the submission title and the first sentence are: Prove you’re human by winning a claw machine.