I'm reading 'An Editor's Burial', which is a collection of essays which inspired the film.
There's an interview with Wes as a foreword, and that's exactly what he describes as his intention for the feel of the film.
There will be lots of users who don't have the same workflow as a developer opening vim all day. People who spend their lives in meetings probably need the reminders. I like the idea and it's a super simple execution.
Agreed this was one of the first things I thought outside the balance of energy required for the whole thing doesn't make much sense.
What are we supposed to take away from this project other than its kind of neat and that methane occurs natural in the environment? We are not about to mining ponds for methane - we already have plenty of it accessible at LFG, waste water treatment facilities, methane from O&G operations.
it probably speeds things up rather than killing them, and you know on the scale of BP pouring millions of oil into the ocean, I reckon what this guy is doing is absoloutley fine and the environmental damage is well within range of what the local environment can cope with and recover from within a reasonably small time frame.
>and you know on the scale of BP pouring millions of oil into the ocean, I reckon what this guy is doing is absoloutley fine and the environmental damage is well within range of what the local environment can cope with and recover from within a reasonably small time frame.
But BP serves millions of customers. If you normalize by that (ie. pollution divided by customers), my guess is that digging up ponds is more environmentally damaging than buying gas at the gas station.
I think you're misreading my comment. It's not to say that it's okay for BP to spill oil, it's that all things considered, the environmental impact of a tank of gas (extracted using current methods) is much less than what this guy is doing. Imagine the alternative: rather than every american filling up at the gas pump, they're dredging up ponds/ditches for methane. How much environmental impact would that cause? Is that better than the occasional oil spill we get?
In France at least they are under investigation because they were illegally spying on their employees and even some of their customers. I am not sure what is the status of the trial, but this was big in France at the time, and happened for a very long time.
Me too. I remember being told by a rather stuffy teacher that if you pointed your fingers to the sky, that the prayer would shoot up to heaven! If you interlaced your fingers it would 'bleughhh not go anywhere!'
I was raised Protestant, and there I was taught that the folded hands were to keep you from fidgeting.
I don't get the pointing at the heavens thing, I mean Jesus himself mentioned to basically be humble, not like those guys on the street corners making a bit show of praying.
Lighting behind a truck is poor (no white lights on the back), and it gives an idea of how bad the roads are getting between snow plows. This is useful since plows often run notably slower than normal traffic can safely run for the conditions.
Being able to pin a set of requests to a specific path inside the infrastructure to they touch only specific instances running specific versions without adding "if blah-blah-blah" custom code into every deploy
Being able to trace every request across the entire infrastructure including all sub-requests the original request triggered.
Being able to observe issues pinned requests caused, automatically trigger an action when an error rate exceeds the threshold, typically removing the pinning.
I'm asking myself the same thing... but I think he is referring to Load Balancing and Logging and maybe Public Key Pinning? Not sure... I'm however sure that Google and Facebook are not the only ones who do Load Balancing and Logging and therefore aren't the only ones who can benefit from CD :)
It's 95% there, but English is hard… We can be helpful about it so the authors can fix it.
¶1: Meet Lefthook, the fastest polyglot Git hooks manager out there. It ensures not a single line of unruly code makes it into production. See how easy it is to install Leftook, which was recently adopted by Discourse, Logux, and Openstax. Lefthook works with the most common front-end and back-end environments so all the developers on your team can rely on a single, flexible tool. And it also has emojis
¶2: The days when a single piece of software that millions rely on was created by a single developer in an ivory tower are long gone. Even Git, universally believed to be the brainchild of Linus Torvalds alone, was created with the help of contributors and is now being maintained by a team of dozens.
¶3: No matter if you work on an open-source project with the whole world as your oyster, or your code blooms in a walled garden of proprietary software—you still work as a team. And even with a well-organized system of pull requests and code reviews, maintaining the code quality across the large codebase with dozens of contributors is not an easy task.
¶4: Hooks—ways to fire off custom scripts when certain important actions (commit, push, etc.) occur—are baked right into Git, so if you are comfortable with Bash and the internals of the world's most popular version control system, you don’t need any external tools: just edit ./.git/hooks/pre-commit and put in some well-formed script that will, for instance, lint your files before you commit.
¶5: However, when you work on a project you are most interested in writing the project’s code, not the code that checks it. In the world of modern web development, tooling is everything, and a myriad of tools exist for a single reason: reducing overhead and complexity. Git hooks are no exception: in JavaScript community, the weapon of choice is Husky with Webpack, Babel, and create-react-app relying on this Node-based tool; the Rails-centric backend world however is mostly ruled by Overcommit that comes as a Ruby gem.
¶6: Both tools are excellent in their regard, but in a mixed team of front-end and back-end developers, as Evil Martians are, you will often end up having two separate setups for Ruby and JavaScript with front-enders and back-enders linting their commits each in their way.
¶7: With Lefthook, you don’t need to think twice—it’s a single Go binary that has wrappers both for JavaScript and for Ruby. It can also be used as a standalone tool for any other environment.
¶8: Using Go makes Lefthook lightning-fast and provides support for concurrently executed scripts out of the box. The fact that the executable is a single machine-code binary also removes the need for handling external dependencies. (Husky + lint-staged add roughly 1500 dependencies to your node_modules.) It also removes the headache of reinstalling dependencies after each update of your development environment. (Try running a globally-installed Ruby gem with another version of Ruby!)
¶9: With Lefthook added in either package.json or Gemfile and a lefthook.yml configured in the project’s root (see examples below), the tool will be installed and used against your code automatically on the next git pull, yarn install/bundle install or git add/git commit. All with zero overhead for new contributors.
¶10: An extensive README describes all the possible usage scenarios for Lefthook. Its straightforward configuration syntax does not hide actual commands being run by Lefthook, making sure there's no funny business going on.
¶11: Discourse—an incredibly popular open-source platform for forum-style discussions—has recently transitioned from Overcommit to Lefthook and never looked back. With almost 700 contributors authoring 34K commits and counting, running linters on all new contributions is a priority. With Overcommit though, team members constantly had to remind newcomers to install required tools.
¶12: Now that @arkweid/lefthook is a dev dependency in the project’s package.json, no setup is necessary for new contributors.
§1: Lefthook halves the time that pre-commit scripts take on localhost.
¶13: The PR that changed the Git hook manager simply required changing .overcommit.yml to lefthook.yml. If you compare them, you will see that Lefthook’s configuration is much more explicit while the Overcommit’s relies mostly on the magic of plugins.
¶14: Besides changing the way the output looks, Lefthook offers a nice summary of everything it does. Lefthook halves the time that pre-commit scripts take on localhost, and increases the CI run speed by 20% (on CI environments with better support for parallel execution, the gain can be considerably more).
Well, if they're trying to get you to switch or to adopt something new, they're trying to sell. There's more to trading than just money for product/service; could be attention, effort, endorsement, opinion and other signalling factors, etc.
By your definition, technically, any piece of content on the Web should be considered a sales page—including your comment, where you'se selling your opinion or attention. If that's the case, does it really make sense to label something a "sales page" in a negative way?
Is there any other way to present a new FOSS project besides telling about the upsides? Trashtalk it from the start, maybe? I don't really get it.
Yep, that's kind of the point of upvotes or karma: You present your content and try to get people to buy it. Not sure where you get the negative sales page aspect though. I made no judgement on the presentation technique or quality, just that open source or not, they are still selling something.
