pvidler

You can always render the text to a texture offline as a signed distance field and just draw out quads as needed at render time. This will always be faster than drawing from the curves, and rendering from an SDF (especially multi-channel variants) scales surprisingly well if you choose the texture/glyph size well.

A little more info:

https://blog.mapbox.com/drawing-text-with-signed-distance-fi...

MIT-licensed open-source multi-channel glyph generation:

https://github.com/Chlumsky/msdfgen

The only remaining issue would be the kerning/layout, which is admittedly far from simple.

Only in the random case. Already sorted in either direction and it's ~10x slower.

The bill is not split -- it says they reimburse you for the measured power usage of the device. Nowhere does it say that this only applies when the heat is being directed into your house, that I could see.

Apart from the point in the first video when they click on a link and you can still see the smudge of the text column on the newly cleared screen. A close look at the text column while scrolling makes it look dirty compared to the rest of the screen as well.

Most of it was readable, but the printf on lines 57--59 made me retch. I see what it's doing, but it's not what I'd call easily maintainable:

  printf("%8.4s", &"LEA ,IMM ,JMP ,JSR ,BZ ,BNZ ,ENT ,ADJ ,LEV ,LI ,LC ,SI ,SC ,PSH ,"
         "OR ,XOR ,AND ,EQ ,NE ,LT ,GT ,LE ,GE ,SHL ,SHR ,ADD ,SUB ,MUL ,DIV ,MOD ,"
         "OPEN,READ,CLOS,PRTF,MALC,MSET,MCMP,EXIT,"[*++le * 5]);

Because that's what makes it a unit test -- you only want the unit, the tests and any stubs/mocks in the executable. Anything more and you have an integration test on your hands.

Pulling a single unit out of a legacy codebase can be difficult, especially when you don't want to actually move, copy, or modify the source-files; stubbing out the dependencies and writing mock objects to verify your expectations of what the code should be doing are also very time-consuming.

Those are the hard parts of unit testing C++, and I wonder if anyone has found a good way of doing it (with a framework, or just a technique).

It looks like a nice test framework, but it doesn't appear to help at all with the really hard problems you face with testing C++ -- isolating the unit under test for separate compilation, and the development and inclusion of mocks/stubs.

Anyone know of a really good (preferably simple and pragmatic) C++ mocking/stubbing framework to go with this?

Thus - at the same bitrate - higher resolution images might look worse than lower resolution ones.

But the 4K stream is HEVC (H.265) vs H.264 for the other HD streams, so it may not be that simple.

Apple did just release online versions of the iWork apps with collaboration (I don't know how well it works in real-time, but then I don't know that for Office either). They also made fun of the MS equivalent in their keynote.

I'm sure that's unrelated :-)

This seems specific to image-based fingerprint sensors? Apple's version does not appear to work this way...

Average speed checks are awful — I spend more time looking at the speedo than I do the road, as I try to keep close to the limit while not hitting the car in front. And they are always for odd speeds that I find difficult to maintain (just the wrong pedal position).

Perhaps they make sense when everyone has cruise control as standard to rely on, but until then a mass rollout would drive me to public transport. Or is that the point?

Milling seems like a better bet (than printing) for home PCBs without the etching. It's cheaper and more accurate, like this one:

http://www.coolcomponents.co.uk/catalog/imodela-milling-mach...

Downside is that there's no solder resist, so SMT parts would be tricky/impossible to solder. Also the above model only handles tiny boards — something that can do a standard 160x100 mm eurocard would be nice.

In fairness the TI launchpads are astoundingly cheap -- as far as I have seen, very few of the other competitors have dev boards at that sort of price.

The mbed board is similar to the mini, but with an online IDE (not a fan) and community. There's not much difference in price there, at least not from the mbed suppliers here in the UK vs the kickstarter prices.

Just from the descriptions and photos, it looks like the mini will be breadboardable.

The bigger one almost certainly not -- it's arduino compatible and the gap on one side is visibly smaller than the other. Also, it's not clear if the big one will have pins dropping down below the board (just looks like female headers).

For developers, I suspect it's less about trust and more about providing something of value to a group of people who are already known to be willing to pay for such things.

> Legal? - possibly. Ethical? - not to me. How is this not evasion of labor laws? That this is par-for-the-course is pretty dismaying.

Surely Samsung aren't doing this for the work -- there have to be cheaper ways to get people to demo your product than flying folks from India to Germany, getting them uniforms, keeping close watch on their activities, daily update emails in the beginning, etc.?

Why not just have their own employees do it? Or just pay native German bloggers?

It sounds to me like Samsung was trying to buy enthusiasm, but failed to adequately communicate the work involved and then massively overreacted when it went wrong for them. With decent management, it could have been better the alternatives -- the 'booth-babe and slimy salesman' or 'bored employee droning through a script' approaches.

I still prefer Apple's approaches to product demonstration -- either a big on-stage demo followed by relatively unsupervised hands-on time for a large number of reporters at once, or a personal demo by a senior executive for certain lucky individuals.

There is what looks like bounce back at around 0:36 onwards in this video review:

http://reviews.cnet.com/smartphones/samsung-nexus-s-at/4505-...

It's some sort of app list screen though and happens between what looks like screens of icons, so I'm not sure if it counts. For lists it looks like an orange glow effect, possibly with some small bounce, but that may be an optical illusion.

This might be enough to confuse a jury? I haven't checked the patent to see if it actually infringes or not.

I see less of this on ios devices, but that may be because I keep up–to-date with newer hardware. I guess devs are targeting the older devices that are still in use -- together with the restricted multitasking on ios, this probably side-steps most memory problems.

(Except for the odd memory hog that occasionally gets terminated while in use, like the Facebook app).

I've been using the ikea standing desk from a few weeks ago -- the lack side table with a shelf screwed to it. I simply put my laptop on top and then use the rest of the normal height desk as a sitting desk. I just move my laptop across to switch. I already had the standard desk and chair, so the whole setup cost me about £10.

I leave the keyboard, mouse and power adapter on the standing side, as motivation to spend less time sitting. So far I can manage alternate hours sitting and standing, which isn't too shabby considering how out of shape I am.

I think intel would bend over backwards to get their processors in an apple phone; it would completely open the mobile market for them. They already give apple some influence anyway -- there was something back in 2011 about apple 'persuading' intel to work on the ULV version of the sandy bridge CPU for use in the air.

Yeah, that last part is my concern -- if I can't use FP on a daily basis, is it still worth my time to try learning it?

Fascinating, thanks. I would have said that the for-loop is at least somewhat intuitive -- the step-by-step (lather, rinse, repeat) nature resembles the way most instruction sets are written. Not to mention flow charts, which most people have been exposed to at some stage.

Do you have any advice for languages and techniques for getting the necessary exposure to these concepts? I'm not in a position to use FP through work, so I'd need some easy intro and way to practice.

Do maps, folds and filters become as natural as for-loops in time? (If you have already been exposed to more traditional techniques). They strike me as similar to regular expressions, in the sense that however long I spend using them I will always have to think it through carefully when I encounter a new use.

By contrast, a for-loop is spelled out for me. They are certainly longer, but I guess they match my thought process more closely. I suppose the question is, do I think this way because of my prior exposure to for-loops, or would it be the same if I was exposed to functional programming first? I'm really not sure.

It's largely intended for the retina MacBook pro, which has two thunderbolt ports, but I do agree -- many of the early peripherals seem to lack support for daisy chaining. As for the USB version... the thunderbolt one is much faster. File transfers at over 900 Mbps from the one testing report I've read so far.

I'm not fully convinced that there's much advantage to the USB one over just using wifi, except where the latter is unavailable.

A product developed while Steve was away from Apple, a project he was forced away from, a success (if not up to iPhone levels) and a probable future success (for Intel!). What's your point?

Seriously, the AppleTV is only a 'failure' by the standards of the iPhone and iPad -- most companies would love to have a product that sells nearly 3 million units per year! The margins may be lower than the iPad's, but my understanding is that it does still make a decent profit.

Thunderbolt is an Intel technology and an incredibly useful one. The available products are already starting to look impressive in functionality and prices will come down before too long; Apple themselves use it to provide gigabit ethernet on devices that are about the same thickness as an RJ45 connector, and they sell those for just $29.

If their controller fails horribly, perhaps they could use the OnLive 'universal' controller -- the one that works with OnLive's console as well as all laptops and android/iOS devices. It's actually a really nice controller -- better than the PS3, slightly worse than the Xbox 360 (but without the battery pack issues).

Interesting, but does that mean delivered all the way to the recipient, or just to the iMessage server? Is there good feedback? If I'm in a low-signal area, I need to know how long to leave my phone in that one spot that gets signal.

Even the messages app is almost too confusing, let alone combining everything else as well. As far as I understand it, if I send an SMS then anyone with a signal can get it; if I send an iMessage, then they need an internet connection or it won't go through -- is that right? If so, it's a pain to mix them up, as many areas do not get good 3G coverage (especially indoors) but excellent phone signal.

Surprisingly few of the people I text have iPhones (or smartphones at all), so I can't easily verify this.

No, as long as you followed the UI guidelines the mini could just use your image-ipad.png -- the 44 point minimum will be smaller than on the big iPad, but it's the same physical size as on the iPhone and so still usable:

http://castirony.com/post/26466421254/the-case-for-a-7-8-ipa...

The only issue is if you have UI elements that must be an exact physical size (some sort of measurement app with onscreen ruler). Not a very common situation, as far as I'm aware.

Yep that's the one, thanks!