vc98mvco

Note the logo of Oculus, it was changed a few months after the Facebook acquisition.

The eye went away. I wonder why.

Do they expect us to believe that the parts will be reused, like it is implied in the video? Of course not, there is not chance the parts will match the next model and even if they do they would have to undergo inspection and testing. That is way to expensive and time consuming. Instead they will be melted into raw components, which is not shown in the video.

What will happen in reality is the phone will go into a industrial shredder and then the process of separating/recycling will begin. The robot seems like a marketing gimmick (they even have it a name), and will not be involved in 99% of the recycling process.

I really want to be proven wrong.

To gauge the interest in the Model 3. The 1000$ is a large enough sum to dissuade non-serious buyers and thus get an accurate assessment.

That cannot be the case, becuse you can still search, it is just missing from the UI: https://news.ycombinator.com/item?id=11322207

Sorry to be off-topic, but the site partially disables my input, i.e. causes high lag. It makes it unusable. I'm using Firefox on a modern PC.

Opera seems to run fine, but it maxes out two cores. Uhhh...?

Thanks. Why did remove it from the UI?

Search is still there https://github.com/search although there is no link to it from the main page: https://github.com. Try and find it if you can!

However the search inside a repo is missing now and using site: to search inside a repo doesn't seem to work with Google.

It looks like a typical factory.

> But that type of action is extremely rare and isn't likely to happen here.

Given the importance of the situation it seems it is very likely it is going to happen just here. It's up to the judge(s).

>and family court judges aren't overly likely to go along with that.

It's up to the judge(s).

>The FBI could potentially convince a psychiatrist...

This is just redirecting pressure to a different person, keep doing it until you find that someone who will buckle.

> Most members of the law enforcement community are decent people and aren't willing to do that type of stuff.

Just like above, most are honest, but you only need one that isn't.

If you think all of those are impossible by the US government, take a look at you know where, where torture doesn't happen, and no-one was prosecuted for torture that didn't happen.

Thank you! Can you also link the second podcast?

Edit

Here it is: https://www.youtube.com/watch?v=Yp6IhjK75oE

> Just making sure. Fix that code will you! :)

> Yes, alloca. (Don't use it.)

> Just make a fast allocator that uses heap instead of the stack. You only need to malloc once and it can be used for any type since like you pointed out, it's effective type can be changed.

Did you even make sure the memory was aligned?

Non-allocated memory (stack char) cannot be used like that. I'm sure you know alloc(), and malloc() is fast for small sizes.

That is undefined behavior for two reasons. You're interpreting an object as an object that has an incompatible type.

It also violates string aliasing because 6.5.7. only works for one way. See my other comment.

Derived can alias Base, but not vice-versa.

It is defined.

6.5.7. An object shall have its stored value accessed only by an lvalue expression that has one of the following types:

- an aggregate or union type that includes one of the aforementioned types among its members (including, recursively, a member of a subaggregate or contained union)

This means Derived is allowed to alias Base.

If you ever asked yourself how does one feel when assimilated by the Borg... now you know.

I see you use C macro templates. I have been experimenting with containers that use those. The advantages are speed and full type safety, and disadvantages are long compilations times (which have to be done only once though), the need to define a new template for every type in (only one) separate file, code bloat, and somewhat long function names (I don't use member function pointers).

I'm not sure if all that is worth it.

A quick look shows this is storing void* pointers only. My excitement was quickly over as I was expecting something with _Generic macros or ability to manage memory for any type.

https://github.com/srdja/Collections-C/blob/master/src/hasht... shows the container is manually configurable. Look at the defines at the bottom. This would mean the container file source-header pair, would have to be duplicated for every type, which is somewhat manageable.

Why isn't this written in the readme?

I hope it won't turn out they let him win.

Any suggestions to fake the appearance? Think of distorting background images, for 2d video game purposes. And it doesn't have to be very accurate, just a general resemblance.