In case anyone is interested in what Volkswagen did exactly in "Dieselgate", I can recommend this talk at the Chaos Communication Congress 2015, that does a technical deep dive: https://media.ccc.de/v/32c3-7331-the_exhaust_emissions_scand...
The talk includes some pretty impressive reverse engineering.
The repo has 12.9k stars.
I really want to believe that they all recognize this project for what it is.
If someone had a real need for this and uses it, it will be interesting to know their reasons.
I'm guessing some share of them are just because they reacted the way I did -- "This name is genius, where can I give it an upvote?" Funniest and most devastating takedown I've seen in a while.
I can easely see some under pressure dev use this project not as an joke.
Some workplaces have publicly visible CI dashboards and managers put fire under you if there is some useless blip there.
If someone had a real need for this and uses it, it will be interesting to know their reasons.
I need to push this out and go home.
If someone had a real need for this and uses it, it will be interesting to know their reasons.
Stars are basically the Github equivalent to Facebook likes. They have no real value, and they're definitely not a review.
function assert () {
var ok = function () {}
ok.ok = noop
ok.fail = noop
ok.equal = noop
ok.notEqual = noop
ok.deepEqual = noop
ok.notDeepEqual = noop
ok.strictEqual = noop
ok.notStrictEqual = noop
ok.deepStrictEqual = noop
ok.notDeepStrictEqual = noopnew proxy(()=>{}, {get() {}})
I only barely speak JS, but that reminds me of a crazy idea I had to combine proxies, tagged templates, and the old `with` statement ... smoke tests showed it would probably work but I never polished it off.
What would the end result be/do?
Instead of applying the template immediately using lexical variables, return a function that can be applied later and uses an object's properties (or whatever method of computation you want). Only a few variable names are forbidden.
You can start already by adding our evergreen build badge to your README
I can do that easy! Just use a static image for the badge!
Let's not pretend that other car manufacturers didn't do the same exact thing. [1]
Volkswagen was a good scape goat out of which US law firms could pull huge sums. People in Europe didn't get such generous refunds as the people in the US did.
[1] https://www.nbcnews.com/business/autos/gm-accused-cheating-d...
Just a weird wrapper for the package "is-ci", which is a wrapper for a variable "isCI" exported in the package "ci-info". I hate the npm universe.
That was unexpected. I had a really good laugh at this project. How funny.
Tangentially, I am just remembering I never followed up on what happened with those trains that detected if they were in an enemy repair facility.
Sounds like the publicity might have forced the manufacturer to open up the relevant control software a little?: https://rollingstockworld.com/passenger-cars/newag-to-make-c...
Wheels of justice grind slowly and all that, but I was really hoping to see more formal government investigations by this point. Especially given the Russian hackers who had previously shutdown the trains.
There is an investigation ongoing. Things like these take time. There's no point in informing the public about every action undertaken during the investigation, because the entity being investigated may take appropriate precautions.
Anyway, don't despair just yet. And yeah, I also wish it wouldn't take that long.
There is an investigation undergoing.
https://youtu.be/XrlrbfGZo2k
There's a Dirty Money (one of the few great Netflix docuseries that never renewed for a season 3) episode on this topic which I can recommend https://m.imdb.com/title/tt7909168/plotsummary/
Hah! I was wondering where the name came from