wldlyinaccurate

The author appears to have added a CNAME since this was posted to HN. The updated URL is http://blog.ppelgren.se/2015-01-03/DIY-Make-Your-Own-Program...

Most (all?) component manufacturers use lead-free solder these days. Lead alloy solders are harder to come by since they're generally only used by hobbyists who find them easier to work with.

My jaw always hits the floor when I see the salaries they offer in SF/NY. Then I remember that working in the UK I typically get twice as much paid annual leave as most people in the USA, usually with the option to purchase more leave. I think I'll always choose more time off over more money.

As somebody who has only recently started looking into functional programming, this was absolutely fascinating.

Even though I'm not very familiar with Haskell, I find this code much more concise and easy to follow compared to the original git-clone implementation in C. Though perhaps that's more down to the author's coding style?

Kumail Hunaid, who made Grid Forms, is also the creator of Flakes.

Neither are very elegant, but you could always do something like:

    var R = require('ramda');
    
    with (R) {
        var propEq = use(pipe).over(get, eq);
    }

...Or even:

    var R = require('ramda');
    
    for (var f in R) {
       window[f] = R.f;
    }

> You mean I can easily share copyrighted movies with strangers on dropbox? I've never seen anyone do that.

Actually, this is very common. It works in exactly the same way as MegaUpload did - Señora Pirata uploads her ripped movies to Dropbox, and distributes the public link to strangers.

I've worked on Angular projects of varying sizes -some as large as 30KLOC (products where every page has enough interaction to justify an Angular controller)- and I can never find myself agreeing with these articles.

Have I just drunk too much kool-aid? Or is it possible that with the right team, the right architecture, Angular can actually be a really great framework to use? The common theme for every large Angular project I've worked on is that the teams have leaned towards a more functional design where state is rarely used. This has always seemed to encourage smaller, decoupled modules which don't suffer from many of the problems that the author mentions.

But hey, it's probably the kool-aid.

I'm having trouble understanding why I would use this over ES6 modules, or even RequireJS/Almond? The README comes across as more of a blog post than technical documentation.

I've been doing the same and so far have seen big performance gains as well. Using HHVM also has the benefit of being able to "tack on" any Hack code in the future if (for example) you have some important code which could benefit from static typing.

I do this a lot in the JavaScript console. If I need DOM interaction, I'll usually just mock-up some HTML and access it via the file:// protocol.

I've read the whole page and I genuinely can't tell what this product is. Is it like PhoneGap - develop once, deploy to multiple targets?

So much this.

In my experience it is extremely useful to have a bunch of "Unfinished; WIP" commits that I can look through to figure out what I was thinking yesterday when I started writing code. When I'm ready for other people to pull my commits, I'll rebase them into more meaningful commits (or often just one single commit).

I may be biased, since I've been using (and enjoying) Angular for quite some time now. But I don't agree with any of your points.

1. I can't think of a single case where the Angular documentation has failed me. Yes, it's sketchy in places, but what open source documentation isn't?

2. I'm not sure which toolchain you're referring to, but Angular is just a framework - you can use whichever toolchain you like. You can even use no toolchain if you wish.

3. Debugging has improved significantly since 1.0, especially since Angular started adding HTML comments to denote where markup is generated from. Browser extensions like AngularJS Batarang and ng-inspector help out as well.

4. Again, I don't know exactly what you're referring to here, but I feel like Angular's concepts and semantics fit in just fine with other systems. Scopes, services, controllers, modules... These all mean what you think they mean.

5. I'm genuinely interested how you think using an open-source JS framework will tie you to a corporation? Hell, I'm interested how using Java will tie you to (I assume) Oracle when things like OpenJDK exist?

If this sort of thing disturbs you (and it should), now is the perfect time to make a change by voting. If you're overseas but have been in NZ at all in the last 3 years you can still vote: http://www.elections.org.nz/events/2014-general-election/vot...

This company makes millions upon millions of dollars from selling surveillance malware to (by the looks of the customer list) anyone who will pay.

If I were to set up a company which sold similar products at similar prices, I would expect the FBI to come knocking at my door very quickly.

I think you'd be surprised at how many people in the UK and Germany are (quite seriously) looking over to Lisboa as a place to go and work. The startup bubble that appears to be happening over there combined with the food, weather and culture is very attractive.

I visit Lisboa 2-3 times a year and every time I go back, it seems more vibrant, more buzzing with energy.

Annoyingly, Google seems to consider my installation of Chrome 37 on Ubuntu 14.04 an "old" browser, so I now get an outdated version of Google.

I really wish this went into more detail. You are notified when a query is slow. You can EXPLAIN it in chat so everybody can see. What happens next? Are slow queries treated as high priority? Is there any tooling around debugging complex queries? Basically, what makes GitHub's process different to the decades-old "grep the slow query log and run an EXPLAIN"?

Everybody seems to be taking about moving away from Puppet lately. Maybe I just don't do anything sufficiently complex with it, but I've never had any problems or gripes with Puppet. 99% of the time it seems like the thing I want to do has already been done in a well-written module on the forge.

The author seems to cite two main reasons for wanting to move away from Puppet: their codebase was large and badly structured, and their techops team didn't know Puppet well enough to manage it. Neither of these sound like problems with Puppet itself -- they're certainly not unique to Puppet. I'm not convinced that moving to a newer, less mature technology (which I assume techops don't know well either) will solve these problems.

Coconuts are already being produced in vast quantities (60+ million tonnes[1]) for their meat and oil. I imagine the coconut water manufacturers are just using the water which would otherwise be thrown away, which is why the coconut water market has been able to grow so rapidly without increasing global coconut production.

[1] http://en.wikipedia.org/wiki/Coconut#Cultivation

IMHO multiple inheritance is a bad solution to this problem. I would be more inclined to use a DI pattern and inject an event manager wherever it's needed.

Even when multiple inheritance is genuinely useful, it still feels dirty to me. PHP actually has a nice feature called traits, which is essentially compiler-assisted copy & paste. It means you can re-use code without duplication and without the confusion that multiple inheritance can bring.

My thoughts exactly, although to be fair, the human body can't survive on ketones alone. Some cells cannot metabolise ketones and rely on glucose produced by the liver to function.

Hey, thanks - that'll teach me for not reading the full page!

Probably worth pointing out that this won't play nice with most minification utilities unless you don't mind leaving all comments in the output.

I think for this reason I still prefer using Array.prototype.join for multiline strings:

    var str = [
        '<!doctype html>',
        '<html>',
            '<body>',
                '<h1>❤ unicorns</h1>',
            '</body>',
        '</html>',
    ].join('');

To see a young person say this bolsters my opinion that technology is moving too fast.

Everybody is in such a rush to learn new frameworks, new languages, new toolsets; nobody is learning how to actually _program_. I've worked with people who looked down on me for not knowing WeekOldFramework, but who couldn't architect a simple CRUD application to save their lives.

I feel like so many developers have this "quantity over quality" attitude about knowledge, and it's hurting the industry. With such shallow knowledge, we're doomed to never learn from history and forever write bad software.

Get off my lawn, etc.

This is normal after a few days as your fingers aren't used to the high force required to actuate the switches. Give it a week or so and the pain should subside -- your fingers will get stronger and you'll probably never want to use membrane keyboards again.

Edit: It really depends on the switches, as well. Cherry MX greens, for example, have a much higher actuating force which some people find unpleasant even after long-term use. Browns and reds have a lower actuating force and are much nicer as a sort of "introduction" to mechanical keyboards.

Just to be clear: PHP didn't change these language constructs. The old constructs are still available. You made a conscious choice to use new language features and are now (understandably) frustrated that they don't work in a 5-year-old version of the language.

> 5.3 was released in 2009. Language constructs ought to have been standardized by then.

Absolutely not. By this logic, no languages would ever evolve. The PHP core team are making an effort to evolve PHP into a better, modern language. If you want to take advantage of this, then do. If you want to write code that runs on your clients' older servers, then write backwards-compatible code and don't expect to be able to use new language features.

This essentially boils down to the fact that your development environment and production environment were running completely different software. This isn't a PHP-specific problem.

> the designers’ strategy to break code compatibility between PHP versions only for aesthetic reasons (array(a,b,c) vs [a, b, c]) is bound to lose the confidence of its users sooner or later.

This is not a backwards-compatibility issue. You used features which were introduced in 5.4, and expected them to work in 5.3.

> Saying "we can only give you this much because your title is X and we don't have an open management position, but we really value you!" is a great way to lose your best people.

This resonates with me so much. I've left a few companies after having conversations which ended with my manager saying exactly this. In most cases they have ended up hiring somebody else at a salary higher than mine.

It really confuses me. I usually don't want to leave these companies because the work is good and finding a new job can be stressful. They usually don't want me to leave because I do good work and finding a replacement is costly. I don't understand why all this bureaucracy and nonsense about job titles has to get in the way of finding a middle ground.