stanford-cs336/owt-sample · Datasets at Hugging Face

text stringlengths 0 105k
http://cryptidcommand.com

Pledge Allegiance To The Weird

The Paranormal Pledge of Allegiance

"I pledge allegiance to the Weird,

and to the Altered States of the Paranormal.

And to the supernatural, from which they come…

Many dimensions, unexplained, with oddity and strangeness for all."

Kick It Forward supported.<\|endoftext\|>In a rather ironic segment of FOX & Friends last week, Dave Mosher from Popular Science was on to talk about the use of drones and the FAA’s recent actions regarding licensing requirements for certain drone operations. Unfortunately, he crashed the drone he was flying in the studio on live TV.

First of all, it was a pretty stupid move to fly a DJI Phantom 2 Vision+ in a crowned indoor area. There is all kinds WiFi interference floating around in a TV studio, which means that it’s not the best place to be flying a drone. Even DJI has heavy-duty nets to enclose the flight area when it demonstrates their capabilities at trade shows.

And all of the people in the immediate area makes matters even worse. Thankfully, he had propeller guards on the Phantom or it would have been much worse.

For his part, Mosher acknowledged the error and apologized to hobbyists for his mistake.

For the record: Flying indoors = bad idea. My plan was to just hover, then land. I apologize to hobbyists everywhere. #hindsight2020 — Dave Mosher (@DaveMosher) February 4, 2015

Unfortunately, the damage has been done with just terrible publicity to hobbyist pilots everywhere. There was no real discussion of safety standards and best practices for flying UAVs.

Additionally, there was no clear distinction made about the FAA’s rules for commercial versus hobbyist pilots other than the intro portion and some confusing statements in the middle. The combination of the two just muddied the water further.

The Academy of Model Aeronautics sent letters to both Fox News and Popular Science expressing its concern for the way the segment was conducted, calling it unsafe and irresponsible.

This demonstration set a poor example for those new to model aviation, and it goes against the message of safety that our community stands for. Basic research into safety precautions and common sense guidelines would have shown that this was not a responsible use of this technology. -AMA

Sadly, this segment did far more damage than good for the image of the bustling drone market.

I have reached out to DJI for comment on the FOX & Friends segment and will update this post with any response I receive.

[Updated Feb. 9, 2015]

I received a response from DJI regarding this incident, which is quoted below:

DJI is continually working to improve new pilot education and raise awareness of safe flying practices, which is why we have a checklist in the Vision app specifically discouraging new pilots from flying close to people and in areas with dense radio frequencies. Without knowing the specifics of this demo, I can say that we do not recommend inexperienced pilots to fly indoors without GPS stabilization. Additionally flying nose forward (which changes orientation) and in an environment with significant radio frequency interference without netting is a challenge that we would discourage first time pilots from attempting.

As noted in my original article above, we have no idea whether radio interference played a roll in this crash; however, the comments from DJI regarding flying nose forward seem to echo the consensus among experienced hobbyists who are joining the conversation about this incident in the comments below and in other forums around the web.<\|endoftext\|>Lots of news today.

Fixed Regressions

I wrote last time about a couple of bad regressions that AWSY identified.

Seth Fowler fixed the bigger of the two, which related to the handling of images. This won us back about 40 MB.

Peter Van der Beken ameliorated the smaller of the two on Aurora, which related to DOM bindings. This won back about 12 MB.

The ongoing DOM bindings work will hopefully fully fix the second regression before the end of this development cycle (February 18).

AWSY

John Schoenick made three big improvements to AWSY.

It now measures every push to mozilla-inbound. Previously it measured mozilla-central once per day. This will make it easier and faster to identify patches responsible for regressions.

It’s now possible to trigger an AWSY run for any try build. Unfortunately John hasn’t yet written instructions on how to do this; I hope he will soon…

AWSY now measures Fennec as well. Kartikaya Gupta created the benchmark that is used for this. He also fixed a 4 MB regression that it identified.

Leaks Fixed

Benoit Jacob fixed a CC leak that he found with his refgraph tool.

Johnny Stenback fixed a leak involving SVG that he found with DMD. This was a very slow leak that Johnny had seen repeatedly, which manifested as slowly increasing “heap-unclassified” values in about:memory over days or even weeks. It’s a really nice case because it shows that DMD can be used on long-running sessions with minimal performance impact.

Justin Lebar fixed a B2G leak relating to forms.js.

Randall Jesup fixed a leak relating to WebRTC.

Andrew McCreight fixed a leak relating to HTMLButtonElement.

Erik Vold fixed a leak in the Restartless Restart add-on.

Miscellaneous

Brian Hackett optimized the representation of JS objects that feature both array (indexed) elements and named properties. Previously, if an object had both elements and named properties, it would use a sparse representation that was very memory-inefficient if many array elements were present. This performance fault had been known for a long time, and it caused bad memory blow-ups every once in a while, so it’s great to have it fixed.

As a follow-up, Brian also made it possible for objects that use the sparse representation to change back to the dense array representation if enough array elements are subsequently added. This should also avoid some occasional blow-ups that occur when arrays get filled in in complex ways.

Gregory Szorc reduced the memory consumption of the new Firefox Health Report feature, from ~3 MB to ~1–1.5 MB: here and here and here and here. On a related note, Bill McCloskey is making good progress with reducing compartment overhead, which should be a sizeable win once it lands.

Gregory also reduced the memory consumption of Firefox Sync: https: here and here.

Jonathan Kew reduced the amount of memory used by textruns when Facebook Messenger is enabled.

The Add-on SDK is now present in mozilla-central, which is a big step towards getting all add-ons that use it to always use the latest version. This is nice because it will mean that when memory leaks in the SDK are fixed (and there have been many) all add-ons that use it will automatically get the benefit, without having to be repacked.

Generational GC

Generational garbage collection is an ongoing JS engine project that should reap big wins once it’s completed. I don’t normally write about things that haven’t been finished, but this is a big project and I’ve had various people asking about it recently, so here’s an update.

Generational GC is one the JS teams two major goals for the near-term. (The other is benchmark and/or game performance, I can’t remember which.) You can see from the plan that there are eight people working on it (though not all of them are working on it all the time).

Brian Hackett implemented a static analysis that can determine which functions in the JS engine can trigger garbage collection. On top of that, he then implemented a static analysis that can identify rooting hazards and unnecessary roots. This may sound esoteric, but it has massively reduced the amount of work required to complete exact rooting, which is the key prerequisite for generational GC. To give you an idea: Terrence Cole estimated that it reduced the number of distinct code locations that need to be looked at and possibly modified from ~10,000 to ~200! Great stuff.

http://cryptidcommand.com

Pledge Allegiance To The Weird

The Paranormal Pledge of Allegiance

"I pledge allegiance to the Weird,

and to the Altered States of the Paranormal.

And to the supernatural, from which they come…

Many dimensions, unexplained, with oddity and strangeness for all."

Kick It Forward supported.<|endoftext|>In a rather ironic segment of FOX & Friends last week, Dave Mosher from Popular Science was on to talk about the use of drones and the FAA’s recent actions regarding licensing requirements for certain drone operations. Unfortunately, he crashed the drone he was flying in the studio on live TV.

First of all, it was a pretty stupid move to fly a DJI Phantom 2 Vision+ in a crowned indoor area. There is all kinds WiFi interference floating around in a TV studio, which means that it’s not the best place to be flying a drone. Even DJI has heavy-duty nets to enclose the flight area when it demonstrates their capabilities at trade shows.

And all of the people in the immediate area makes matters even worse. Thankfully, he had propeller guards on the Phantom or it would have been much worse.

For his part, Mosher acknowledged the error and apologized to hobbyists for his mistake.

For the record: Flying indoors = bad idea. My plan was to just hover, then land. I apologize to hobbyists everywhere. #hindsight2020 — Dave Mosher (@DaveMosher) February 4, 2015

Unfortunately, the damage has been done with just terrible publicity to hobbyist pilots everywhere. There was no real discussion of safety standards and best practices for flying UAVs.

Additionally, there was no clear distinction made about the FAA’s rules for commercial versus hobbyist pilots other than the intro portion and some confusing statements in the middle. The combination of the two just muddied the water further.

The Academy of Model Aeronautics sent letters to both Fox News and Popular Science expressing its concern for the way the segment was conducted, calling it unsafe and irresponsible.

This demonstration set a poor example for those new to model aviation, and it goes against the message of safety that our community stands for. Basic research into safety precautions and common sense guidelines would have shown that this was not a responsible use of this technology. -AMA

Sadly, this segment did far more damage than good for the image of the bustling drone market.

I have reached out to DJI for comment on the FOX & Friends segment and will update this post with any response I receive.

[Updated Feb. 9, 2015]

I received a response from DJI regarding this incident, which is quoted below:

DJI is continually working to improve new pilot education and raise awareness of safe flying practices, which is why we have a checklist in the Vision app specifically discouraging new pilots from flying close to people and in areas with dense radio frequencies. Without knowing the specifics of this demo, I can say that we do not recommend inexperienced pilots to fly indoors without GPS stabilization. Additionally flying nose forward (which changes orientation) and in an environment with significant radio frequency interference without netting is a challenge that we would discourage first time pilots from attempting.

As noted in my original article above, we have no idea whether radio interference played a roll in this crash; however, the comments from DJI regarding flying nose forward seem to echo the consensus among experienced hobbyists who are joining the conversation about this incident in the comments below and in other forums around the web.<|endoftext|>Lots of news today.

Fixed Regressions

I wrote last time about a couple of bad regressions that AWSY identified.

Seth Fowler fixed the bigger of the two, which related to the handling of images. This won us back about 40 MB.

Peter Van der Beken ameliorated the smaller of the two on Aurora, which related to DOM bindings. This won back about 12 MB.

The ongoing DOM bindings work will hopefully fully fix the second regression before the end of this development cycle (February 18).

AWSY

John Schoenick made three big improvements to AWSY.

It now measures every push to mozilla-inbound. Previously it measured mozilla-central once per day. This will make it easier and faster to identify patches responsible for regressions.

It’s now possible to trigger an AWSY run for any try build. Unfortunately John hasn’t yet written instructions on how to do this; I hope he will soon…

AWSY now measures Fennec as well. Kartikaya Gupta created the benchmark that is used for this. He also fixed a 4 MB regression that it identified.

Leaks Fixed

Benoit Jacob fixed a CC leak that he found with his refgraph tool.

Johnny Stenback fixed a leak involving SVG that he found with DMD. This was a very slow leak that Johnny had seen repeatedly, which manifested as slowly increasing “heap-unclassified” values in about:memory over days or even weeks. It’s a really nice case because it shows that DMD can be used on long-running sessions with minimal performance impact.

Justin Lebar fixed a B2G leak relating to forms.js.

Randall Jesup fixed a leak relating to WebRTC.

Andrew McCreight fixed a leak relating to HTMLButtonElement.

Erik Vold fixed a leak in the Restartless Restart add-on.

Miscellaneous

Brian Hackett optimized the representation of JS objects that feature both array (indexed) elements and named properties. Previously, if an object had both elements and named properties, it would use a sparse representation that was very memory-inefficient if many array elements were present. This performance fault had been known for a long time, and it caused bad memory blow-ups every once in a while, so it’s great to have it fixed.

As a follow-up, Brian also made it possible for objects that use the sparse representation to change back to the dense array representation if enough array elements are subsequently added. This should also avoid some occasional blow-ups that occur when arrays get filled in in complex ways.

Gregory Szorc reduced the memory consumption of the new Firefox Health Report feature, from ~3 MB to ~1–1.5 MB: here and here and here and here. On a related note, Bill McCloskey is making good progress with reducing compartment overhead, which should be a sizeable win once it lands.

Gregory also reduced the memory consumption of Firefox Sync: https: here and here.

Jonathan Kew reduced the amount of memory used by textruns when Facebook Messenger is enabled.

The Add-on SDK is now present in mozilla-central, which is a big step towards getting all add-ons that use it to always use the latest version. This is nice because it will mean that when memory leaks in the SDK are fixed (and there have been many) all add-ons that use it will automatically get the benefit, without having to be repacked.

Generational GC

Generational garbage collection is an ongoing JS engine project that should reap big wins once it’s completed. I don’t normally write about things that haven’t been finished, but this is a big project and I’ve had various people asking about it recently, so here’s an update.

Generational GC is one the JS teams two major goals for the near-term. (The other is benchmark and/or game performance, I can’t remember which.) You can see from the plan that there are eight people working on it (though not all of them are working on it all the time).

Brian Hackett implemented a static analysis that can determine which functions in the JS engine can trigger garbage collection. On top of that, he then implemented a static analysis that can identify rooting hazards and unnecessary roots. This may sound esoteric, but it has massively reduced the amount of work required to complete exact rooting, which is the key prerequisite for generational GC. To give you an idea: Terrence Cole estimated that it reduced the number of distinct code locations that need to be looked at and possibly modified from ~10,000 to ~200! Great stuff.