The extreme values for "Optical Size" really alter the character of the font for me. Changing the angle of the lower arc of the "e" for example really alter how the font feels, and it's unrecognisable to me as Helvetica:
Huh, I'd assumed that ink traps would somehow be absent from fonts intended for screen use. Thinking about it now, though, it does make sense that (at least on typical computers) it's the same font file used on-screen as sent to the printer, and at small sizes on-screen they're probably hidden by hinting anyway. A cursory search also reveals that varying paper and ink conditions made for an age-old problem of achieving consistent weight.
And indeed, the distinctive spur of the 'R' all but disappears at low optical size. Something else I never noticed: the spur of the 'a' changes from vertical to horizontal at high weights in many grotesques.
A stylistically different example is One Central Park in Sydney [1], which appears to still be going strong. Although I don't know what the maintenance for it is like.
This is pretty cool. A couple of years ago I found an old map of Singapore and built page to compare it with a contemporary one [1] - this a lot better!
The reclamation completely changed the outline of the island, and the reservoirs change the interiors. But it was fun looking for things that haven't changed.
Nice work Ashish! I agree, I found your version more accessible.
Singapore’s land reclamation over the last few decades has been fascinating. Not sure how much longer it can continue though. Indonesia and other neighbouring countries have started getting tougher on sand exports. There are actual smugglers who take away boatloads of sand from neighbouring uninhabited islands to sell.
I actually think your version presents a more accessible view of the true extent of the reclamations! It's a very intuitive and immediate view of the effects, rather than clicking layers on and off.
This is cool. I'm pretty excited about AWS lambda.
Keep in mind the current limitations of the AWS lambda at present:
A process can't take longer than 60s.
Only 25 concurrent executions.
The zipped package containing your code and all dependant libraries can't be larger than 20MB.
I'm almost disappointed to see a post like this with no comments - because while it's often quite negative - HN comments often provide me with context and a counterpoint that's really quite useful.
My first reaction is that I quite like it. It's more semantic than dozens of nested divs and spans, and perhaps that's not as useful for machine generated code - for those of us coding html by hand.
Is it really more semantic? Consider the first example, starting "<calendar><month name="January"><day>1</day>...".
It looks reasonable from the start, but then you get into real-world issues: why do you need to specify the days? What do you do if you want a 10 year calender? How do you treat February? What are the odds of everyone getting the calender correct, especially when doing it by hand? How do you specify the first day of the week? Some countries start the week on a Sunday and others on a Monday. Can the month name be localized, so that French readers see it as Janvier while the back-end still knows it's January?
People tried really hard to get semantic namespaces working with XML/XHTML, but it didn't really seem to pan out.
That sounds secure, but help me understand:
Is it the same password everywhere? How do you manage the different passwords for different services?
How do you enter your password to login on an ipad, or on your phone?
My biggest problem with the Apple's password policy is that I'm required to enter it periodically on an ipad or iphone - meaning I can't keep it lastpass and that complex alphanumeric passwords are even harder to enter.
My iOS accounts are, unfortunately limited to a password that I can remember but I use one with numbers and letters and a mixture of uppercase and lowercase characters.
Most of my website passwords are generated keys; each different - all stored within 1password, should there be an issue at any point (doubtful) I can always go through the "forgot password" features on any given website to reset it to something temporarily that I can use easily.
I agree somewhat, but I think the article underlines a problem with the Genius UI as it is now, rather than the concept.
The current Genius UI of 'annotation' restricts the concept to highlighting words and phrases. This is limiting. But annotation thats both richer and looser would be more flexible: Allowing people to reference chapters or sections more generally, and potentially multiple sections simultaneously and cross reference annotations themselves.
I could see utility in something that allowed the creation of CliffNotes style context alongside the real content. And that also falls under the umbrella of 'annotation' in my mind.
There's also potential in the idea of real-time annotation, rather than the snapshot, more curated content they seem to have now.
Doing any of this in a way that isn't overly complex or cumbersome will be tricky, and I've no idea if it's a direction that the creators want (or can) develop it in.
Genius were a lyrics site with an interesting javascript UI and great SEO. They sold that JS UI as part of a bigger picture. But for the reasons the article mentions that JS UI isn't going to take them there. Hopefully they can use that 15 million to build something that will.
For an organisation which is insolvent they must have invested a fairly significant sum on a 3 letter .com domain.
This happened yesterday!
What's going on here?
Yeah, but shouldn't they try to pay people back before they spend what's likely tens of thousands of dollars on what amounts to superficial marketing? I mean, it's not even much of a re-brand!
> Yeah, but shouldn't they try to pay people back before they spend what's likely tens of thousands of dollars on what amounts to superficial marketing?
"Should" based on the assumption that they are profit-maximizing entity, or "should" based on the assumption that they are a moral actor? Because, you know, the answers are quite different.
It's fertile breeding grounds for conspiracy theories, so I'm not going to post my elaborate speculation here. I'll just summarise it as "there are several people working at Mt. Gox and they're probably not very good at talking to one another".
They SHOULD pay secured creditors which could include domain provider. I dont imagine its customers are SECURED .. so will be last .. in a proper insolvency..
The Indian program involves giving multiple doses of the oral vaccine to babes (Pulse Polio). Unfortunately the number of does of the oral vaccine babies receive is correlated with AFP - Accute Flacid Paralysis - a tragedy similar to the paralysis caused by polio.
http://www.thehindu.com/opinion/lead/polio-free-does-not-mea... In some states babies are getting over a dozen doses.
A move to the injectible vaccine will reduce this risk, but since the injectible vaccine costs a lot more it's likely the coverage will fall.
I'd characterize that article as saying it "may be" correlated at strongest - sounds like the WHO says oral doses have been decreasing for years while AFP cases were still increasing?
https://imgur.com/a/vtQZc9I