Dos32.bas with Visual Basic was my first intro to programming. There was no useful search so you had to navigate through webrings to get programming tutorials. There were also networks of private vb channels where the hackers hung out, those were always fun to drop in on.
Maybe I’m looking back with rose-colored glasses but I remember Visual Basic being intuitive and approachable for beginners in a way that I haven’t seen since.
The fader text is a nice touch too, that immediately makes me nostalgic.
Recently there's been cases where searching for a company name will actually return an ad for a competitor. Companies are being forced into a bidding war to win back the top position for exact searches on their own name.
I'm not on buildbot nine (I think the new waterfall UI is a big regression), but what that is describing looks like a statically defined list of workers that scale up and down dynamically. What I'm looking for is the ability to add and remove workers at will, without having to add them to the configuration list and restart the master.
In terms of underpowered build steps, I have several fairly complicated, 1k-2k line build factories, with multiple codebases and hundreds of steps (some custom, some from the stdlib). There's many dependencies between the steps, and many different properties that can be toggled in the UI. All these steps need to be defined up-front in the master, but their actual execution often depends on runtime information, so it becomes a mess of doStepIfs. I think it would be an improvement to give a program on the worker the power to tell the service what it wants to do, rather than the other way around.
I'm still on buildbot, but it's definitely showing its age and I'm hoping to move off of it within a year. I've been keeping an eye on Chromium's buildbot replacement, LUCI (https://ci.chromium.org/). It's still light on documentation and the source is very internal google-y (they seem to have written their own version of virtualenv in go). However, based on the design docs it does look like they ran into a lot of the same problems I have with buildbot, specifically the lack of support for dynamic workers, and how underpowered the buildbot build steps can be.
A recent example of this is buildbot. The current version (8.x) has a very no-frills, utilitarian python/jinja UI which has served me, personally, and many other open source projects well (chromium, mozilla, LLVM, etc). Version 9 is a rewrite two years in the making using angular with the modern JS toolchain for its frontend. I tried out the latest (beta) build, and from what I can see I think it's exactly what you describe: more resources with less functionality. Time will tell whether the final version lives up to its promises but I'm very skeptical at this point.
"Put the secret into your shared/.rbenv-vars file"... and then say goodbye to them! http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0... . I don't think keeping your secrets in a file accessible to the web server is a good idea because of LFI vulns like this.
Some other ideas that I've heard that may be better: store the secrets on a separate "offline" server that only the web server can talk to. Or have the file readable only by root, run a bootstrap script as root that would read the file, drop root privs, and then start the webserver.
Usually Fabien gives a high level overview and dives into some of the pieces of the project that he finds interesting. I don't think this is the type of review that focuses on overall C practices unless it's something really unique to the project.
I tried this once as well and I might have stuck with it if chrome had a quick "add to js whitelist" button. Instead you have to fiddle around in the settings menu which just takes way too long.
I've accidentally pasted lines with --username --password into source files because of a sensitive scroll wheel... That's pretty embarrassing in code review.
What source are you looking for exactly? The piece was about the Dark Snow Project, and the journalist trekked around Greenland with the guy that founded it.
Swipe to navigate is a terrible design antipattern. I can always tell when I'm reading a blog on blogspot because it'll dump me to the adjacent article when I'm scrolling or trying to zoom in on an image. I dumped chrome on ios because they didn't get it right either.
Maybe I’m looking back with rose-colored glasses but I remember Visual Basic being intuitive and approachable for beginners in a way that I haven’t seen since.
The fader text is a nice touch too, that immediately makes me nostalgic.