173 karma · joined March 22, 2011
The idea being that when you do a deploy, the launch config is updated to use the new AMI ID. The old instances are terminated and the new ones popup in its place. You can play with the scaling options to set an update pause time. We can get a 0 sec downtime with this.
I'm not sure why you think we're using bootstrap, we're not. Everything in our code base is bespoke (with the exception of jQuery 2). As a result, we get to choose our breakpoints, and they're flexible for now (there's a lot of movement before we go to the next one).
The iPad in portrait mode doesn't have the available width to show the second column without cramming the stories in the main column.
We settled on the breakpoints we have due to the amount of devices we want to offer our content on. We're a service that's trying to work on as many devices as possible, from Nokia 100s to modern desktop browsers. So we did the logical thing of splitting devices into groups, feature phones, smart phones, tablets, and above (desktop & TVs). Some of the larger screened Android phones cause issues since they have a massive resolution, but can't display content as a tablet because it would be hard to read.
You're right, we don't have volume settings right now, so we can't emphasise any of the stories except to make them the "top" story. We haven't got to that point yet, we are after all in beta. All I can say is it will come.
I can't comment on editorial context, just the technology.
The most read functionality is being worked on to be richer.
Thanks :)
For those of you who are on a wanting to see the site mentioned in the page: http://www.bbc.co.uk/news?view=beta
You can ask us about any of the technical points of our site here: http://github.com/bbc-news/feedback
> Lord Blair told BBC Radio 4's Broadcasting House programme: "The state has to have secrets – that's how it operates against citizens.
There's a ruby refactor that allows you to just specify an environment var.
We use this for catching things that we'd never spot, a good example of how it has helped us is after a giant Sass refactor, we ran this tool against the old CSS site and the new CSS site, this showed us where things were off by a pixel or two (as well as big formatting changes).
We've found this tool rather valuable, we're not saying everyone will, or that others should use it. We open sourced it because it might help someone.
The content on /future is generated and created by BBC Worldwide and thus, unavailable to the UK because of this...
They can't show adverts on this page and allow people from the UK to see it because this would cause confusion and make people wonder where their licence fee is going.
Everything else is down to preference... I'd rather write native Obj-C code, but the guy next to me would rather write in ruby.
It's very subjective and down to coder preference, I can only hope that the ruby world has a great work around for the very verbose selector names in the iOS SDK; I was expecting some sort of wrapping for the iOS SDK to make it simpler.
But I assume it uses storyboards in the same way as ObjC, set it in the target and in the Info.plist, and it figures it out... it'd be nice to see it working though.
I agree with #3... a way to create requests with custom headers would be fantastic.. for example when you're trying to connect to an API via JS...
But generally, working for startups isn't mentioned as an option to students at any point during their course. This is perhaps an issue with university faculty, they probably assume it's not an option since they don't have any contacts to any startups. Placing a call to Microsoft recruitment is easy.
Another reason might be an issue with the education students receive at university, I feel as if only 10 students out of a class of 120 people will know how to program correctly. Startups normally want people with lots of knowledge in many different areas, they don't want people who only know how to do certain things; Hiring a graduate who can only code HTML isn't normally an option for startups since they need the most out of the little money that have.
Until at least 50% of a graduating class are able to perform in multiple areas, backend, front-end, perhaps mobile in multiple languages (they don't have to know them amazingly well, but enough to program efficiently whilst checking documentation – when needed!), startups aren't really an option for most graduates. You would be amazed at how many students can't debug problems in their code, because they're taught to just copy code they find on the internet or on some sort of Blackboard style intranet app.
TL;DR: Students graduate with piss poor skills and until more students graduate with the needed skills, they'll never find themselves in a startup.
I think it's foolish to think that Apple uses private frameworks for their apps exclusively, when they could be using the public frameworks that other 3rd party apps use.
It's more likely to be: Apple uses the public frameworks for the majority of their apps but use the private frameworks for controlling the underlying hardware and subsystems of the OS [stuff like communications which could cost the user money, SMS, phone calls].