weland

> > You should be (or have a strong desire to become) a HTML5 geek, JavaScript nerd and CSS wizard.

Indeed, it seems that there is hardly any room left for mere programmers in this industry :-).

It will be fun to see someone lecturing JWZ on what he can do and what he cannot do on the web.

> If the citizens demand access to those services, or find it offensive that their privacy and security is being violated and circumvented, they will take action.

Hah, right. They'll just file a complaint to their ombudsman and the Congress will take care of it.

No, this is Kazakhstan, not California. If citizens band up and demand something that the government is against, the police will crack down on their homes, arrest 15,000 people at random out of which only 10,000 or so will return to their homes (not necessarily alive), and the remaining 5,000 will rot in jail for high treason. And if they keep getting wise ideas, they'll send in the army.

Yeah, that's why that proportion is important. There are a lot of examples for that. XML, C++, PHP. The list goes ever on and on :-).

I stopped using mutt a while ago, but I just used separate config files for every mail account and a bash alias to launch mutt for each one.

Unless you actually need to do things like move entire e-mail threads between accounts, it works well enough.

To be fair, if you stick to the good parts, any language is good.

It's the good parts : bad parts proportion that tends to ruin things.

When studying power consumption for this type of devices, it's extremely common to measure the current being drawn, rather than to put out values in watts.

For one thing, it's the current that you usually measure in these cases anyway. For the other, power consumption in watts is not what you generally want to know when you design a battery-powered circuit. And, last but not least, it's more useful to have a figure in (m)A than (m)W when batteries are rated in mAh.

It's not correct terminology, mind you, but then neither is that of energy in your energy bill, so I guess this can be forgiven.

Netscape before 4 kicked ass. Netscape 4 was terrible. Netscape 6 was late.

The Pi foundation being good friends with Broadcom also helps.

It's a case of not really telling the truth, which is pretty much what lying means.

> how inportant was/is a switching supply

Fairly important. Linear power supplies are pretty large and put out a lot of heat. It was commonplace back then for most appliances, including computers, to have a linear power supply. A switching-mode PSU was an improvement over the status quo in general.

> and was incorporating it really as simple as copying a well-known design?

Yes, it was.

This is a pretty interesting article! I raised more than my fair share of eyebrows by telling people I'm not really surprised with this kind of complexity (note: I'm an EE by formation, I took a frickin' two-semester course on power supplies) but that it doesn't fully justify the price difference.

Also, Jobs was a blatant liar :-). The SMPS in any modern computer is based on a standard topology that Rod Holt -- though a brilliant engineer in his own right -- didn't invent. I don't remember the specific details, but it's based on a flyback design that was certainly well-known at the time.

If you use an actual pdf reader instead of the JS-based in-browser crap, it's quite instantaneous.

Yep, what ics said :-).

Basically, I think OpenBSD is a good operating system. It has a clean architecture, great code quality, and I am fond of its engineering principles.

I don't think it's Good (TM) -- there are things that other operating systems do better, and I don't think its engineering principles apply everywhere.

I admire its design, but I don't try to emulate it in any system I build.