An Android version would also bring added benefits of smarter/less battery intensive background operation which could make this run all the time. Constant GPS-monitoring like Latitude or this seems to run way better on Android for some reason.
>It is recommended to use a separate GPS device to record your tracks. This would save beattery life of your iOS device and avoid GPS signal loss when Internet connection is unavailable.
Otherwise, looks batteful.
Now this? Congratulations, you have turned a peaceful and enjoyable experience into a slot machine. Now rather than enjoying where I am, I can enjoy hearing my phone go DING! You will lose all connection to the places you go. Rather than rely on my own memory, which takes a few trips, I will just go to a neighborhood once, cross it off my checklist and probably never go back. Because going back wont give me the exp I need to level up and release endorphins.
Gamifaction is the public relations term for addiction.
Anyway, get off my lawn, yada yada...
Some feedback on the site itself: I'm having trouble reading the text due to the low contrast. (Maybe my monitor isn't setup properly?)
I think I could do something similar in an open format that will still be accessible in 50 years: an image of the world map, with an alpha channel that has pixels where I've been made opaque.
Unfortunately though I don't want it on game center, I want it in some sort of open exportable data that I can access, perhaps make a widget for my website out of, or update from other devices.
If this can tap into that same urge, I think it could do pretty well.
In a nutshell, the 2.x version of declaring a unicode string is now valid (although redundant). From the PEP:
In many cases, Python 2 offered two ways of doing things for historical reasons. For example, inequality could be tested with both != and <> and integer literals could be specified with an optional L suffix. Such redundancies have been eliminated in Python 3, which reduces the overall size of the language and improves consistency across developers.
In the original Python 3 design (up to and including Python 3.2), the explicit prefix syntax for unicode literals was deemed to fall into this category, as it is completely unnecessary in Python 3. However, the difference between those other cases and unicode literals is that the unicode literal prefix is not redundant in Python 2 code: it is a programmatically significant distinction that needs to be preserved in some fashion to avoid losing information.
This version of python should see more uptake by 2.x developers as it is now easier to port.
Having to re-do any part of your code from one release of a language to another became a real deal breaker for me.
For an interpreted language that problem is even worse because you don't know you have a problem until that bit of code gets hit.
It is a thorough read and not the easiest, but you can always pick and choose what chapters you're interested in. I highly recommend it. You can buy it from Amazon here (not an affiliate link):
1. C & S exchange messages to agree on versions, ciphersuites, and nonces.
2. S->C certificate, which includes an RSA public key.
3. C verifies certificate against its local cache of CA roots.
4. C->S random secret encrypted under the RSA key (the "pre-master secret").
5. C & S derive (the same) set of MAC keys, crypto keys, and crypto parameters.
6. C & S verify every message of the handshake with the MAC keys.
Other useful things to know:
* SSL/TLS operates over a "record layer" of TLV-style messages. The TLS record layer itself supports fragmentation, which is a little crazy.
* The server can ask the client to send a certificate too; this is common on backend connections and unfortunately not common with browsers, because the UI is terrible.
* Less commonly, C & S can opt for a "DHE" (ephemeral Diffie-Hellman) key exchange, in which the RSA key from the certificate is used to sign a DH key exchange (DH allows both sides to use random public keys instead of long-term fixed keys, but suffers from exposure to MITM attacks --- the RSA key from the cert "breaks the tie" in a MITM situation, making the exchange secure). This has the advantage of ensuring that even if an attacker has been recording all your traffic for years, she can't compromise a server's private key and then decrypt older connections. This is called "forward secrecy".
* The two common cipher suites used on most connections are AES in CBC mode and RC4. AES-CBC chunks plaintext into 16 byte blocks, padding the last block if there are insufficient bytes to fill it. Until TLS 1.1, TLS ran CBC in a continuous stream over the whole connection, using the last block of the most recent message as the IV for the next, which gave rise to the BEAST flaw. RC4 is a stream cipher that encrypts byte-at-a-time --- but nobody trusts RC4 much.
* TLS 1.2 (IIRC) introduces AES-CTR, which runs AES as a stream cipher.
If you haven't seen any of Marlinspikes presentations, you are missing out on some fascinating stuff.
Moxie @ Defcon 19: http://www.youtube.com/watch?v=xIiklPyS8MU
Those who keep saying "Maps is great" need to leave an egocentric view and realize that there are millions of users all around the world with different experiences.
According to the apology letter they serve about 500 million searches in one week. That means two billion searches per month. What does this mean in therms of customer experience?
According to this either 60% of the locations either incorrect or missing altogether. I'll be generous and propose that Maps, world-wide, might have an average of 5% incorrect or missing locations. I don't know if this is too low or too high. It's just a number that I pulled out of my imagination in order to get a sense of proportion.
If only 5% of the data is wrong and we have two billion searches per month, that means 100 million bad searches per month. I'll let the reader guess as to how many users that affects. It certainly is in the millions.
If data errors are larger than that the situation is far worst. Again, I'll leave it up to the reader to guess as to how much user anger would trigger Apple to post an apology letter on the front page of their site.
If you live here in California, and, in particular, the Bay Area, please refrain from posting how "Maps is great and it is beautiful". You do not represent the experience of the vast majority of users who had almost no issues whatsoever with Google Maps.
Oh, yes, on the whole "Maps is beautiful" mantra. Who the f* cares? 3D view? Who the f* cares? First make them dead accurate, then add eye candy if it makes sense. Accuracy is far more important than bling when it comes to maps. Nobody is going to want to use a beautiful map that takes you to the wrong place. And 3D view. Really? Get it right first. Then play.
I think the new Maps app is fantastic; the data accuracy leaves a bit to be desired, but I notice that those doing the most high-profile complaining point to errors in rural England, rural Ontario, etc. Here in the Bay Area, the data is working fine for me as well.
It is not shocking to me that a map database that is a few months old is less mature than one like Google's, which is the product of a decade's effort, and also the product of 5 years' worth of improvements riding the back of iOS users' crowd-sourced data. Now Apple has that data coming into its database, instead of flying out the door to Google's.
Maps is likely to improve, and fast.
In any case, blaming Forstall is idiotic and talking about firing him is Fortune-level idiotic. He made great things at NeXT, Mac OS X is great, Siri is great, and Maps is a work in progress that shows great promise.
Have you tried reloading map data and zooming in and out on maps in Google Maps vs. Apple Maps in an area with EDGE or otherwise bad internet coverage? Apple's app wins hands-down versus reloading non-vector map tiles.
Gargade in, garbage out.
Probably less than 1% of developers have GitHub repos and there's no correlation between skill level and having a GitHub repo.
If you have extensive and current open source contributions, for most people it means you're unemployed, or you're violating your employer's contract terms.
Evaluating a GitHub repo for a summary of skills in not a trivial task, as scanning a resume is.
When all of your work is online, it suggests you are not spending much time contributing value to whoever is employing you.
Companies that can't find developers often have bizarre and useless criteria such as "must have GitHub repository" or "must have LinkedIn" or "must have FaceBook", none of which is correlated with ability.
We hire lots of capable people without GitHub repositories.
You'll never see the flight computer system of an F-16, but it's probably a much cooler project to work on than an iPhone app. Or nuclear reactor engineering.
Is a resume relevant in this day and age? As a device to portray the best of what you've accomplished yes. For a few people, the answer will be no, that's best done through portfolios like github and open source projects.
In the end, everything old will be new again but with a twist.
I certainly hope a resume remains relevant for people in my position, because it's really all I have.
So you are looking for a concise and centralized resource for listing your qualifications for a job. And you are asking if a resume is still relevant? It seems like the way to tell employers about your github, SO, udacity, etc, profiles is to list them on your resume.
To resume means to summarize. Your GitHub profile is not a summary, it is a raw dump of everything that you have done without weighting.
So, of course a resume is still relevant today. And it is still up to the applicant to present himself to the employer, because most of the time the applicant is looking for a specific job when the company is not looking for a specific employee.
After a series of emails, we proposed that we should pay him a few months consulting fee - to help us integrate. As a bonus of course, he could take the improvements and fold them back into his his open-source project.
Things continued like this and eventually he proved useful in other ways, so he is permanent hire now.
In this day and age, there really is no excuse for having "no experience" (in the software world at least). Moreover, who really cares about what university you went to if you can prove your immediate usefulness in other ways?
Jobs at technology companies might be what ArsTechnica and Hacker News readers go for, but those jobs are such a small percentage of the jobs filled every day in the US.
Completed live projects instantly visible on any browser or smartphone with a quick technical explanation have always been far more valuable for me.
You don't need to ask anyone's permission to build amazing software.
(Unfortunately, you continue to need permission to build many other things.)
Also, an emerging trend is "Github for X". You have sites like Grabcad (Github for Mechanical Engineers), Dribbble and Behance (Github for Designers), Benchling (Github for Biology), Proformative (Github for Accountants), etc. As these professional communities grow they'll increasingly be looking at by employers.
It's early for this trend but we believe deeply in it.
Has there been any writeup that explains the potential impact of Persona on privacy? Not just the impact when used as intended, but also any unintended effects?
(Maybe I'm not looking deep enough? Anyway, thanks in advance.)
If we're going to have browser support anyway, I'd rather just use standard two-way SSL and put the work into developing better UI and private key distribution systems for it. It's even more secure and has a great user experience once you've set up the key in the browser and authorized it to the site.
I suppose mobile apps would ideally use some sort of Persona login service provided by the underlying OS, and until such a thing exists I guess an app could reimplement all the user-agent logic and load the user's login page in a webview. But I have no idea how at all I would go about designing an API for a website which uses Persona for logins.
I'd rather they made OpenID less scarry (to average Joe) instead.
I cribbed these from one of the examples, but my favorite "beyond just resizing" commands are:
bind ;:cmd;ctrl throw previous
bind /:cmd;ctrl hint ASDFGHJKL
On the app store: http://itunes.apple.com/us/app/spectacle/id487069743?mt=12
(I have no affiliation with this program. But I like it.)
- WebDev, push Chrome to the left, iTerm to the right
- Dev - fullscreen iTerm, and inversely, Web - fullscreen Chrome.
- Support - Mail on one side, browser on another
One thing I wish it had was Spaces support; so I could set up a layout across multiple spaces.
Another great feature is 'default' - I switch between a standing desk setup and my laptop (seated) a couple of times during the day by enabling/disabling my second monitor. Slate is set up to rearrange my windows how I like them for both setups automatically when a change of monitors is detected.
bind right:alt push right bar-resize:screenSizeX/2 bind left:alt push left bar-resize:screenSizeX/2 bind up:alt push left bar-resize:screenSizeX*2/3 bind down:alt push right bar-resize:screenSizeX/3
Love it, certainly going to use it when I need a video player. It even has full screen!
Edit: Even better, it's responsive to browser width changes!
Safari 5.1.7 on Snow Leopard
Online news is broken for one fundamental reason: It's currently hard to generate enough revenue from online ads to pay for the creation of high quality content.
This is the only problem that needs fixing and anything else is polishing brass on the Titanic. Fancy news reading systems (Instapaper, Flipboard, Pulse, etc.) are nice because they strip out all the ads. "Wow, look how much nicer it looks! We're totally saving journalism." They aren't. They don't have to pay to produce content, so they can repackage it inexpensively or for free.
The truth is more people are reading the news now than ever before. 16 million people read The New York Times online last month. The print publication peaks at just over 2,000,000 on Sundays.
We don't need better social crowdsourcing of stories. We need more ways to pay for great content.
Second, I suggest the next step is crowd sourced expert curation. Some of the most popular posts on Reddit are where an expert enters the comments and lays the article bare for the masses. This is valuable. I'd pay for this.
But, and it's a big one, experts aren't cheap and their time is scarce. They're not going to curate content for free all day like Reddits 12 year olds and the granularity of expertise means you'll never cover everything with a small number of experts.
Two solutions: volume through scale to fund expert curation or find a way to gather and have them work for free. Maybe the research journal system be used here to provide non-financial incentives?
High-quality news with high-quality context and interpretation can only really be generated by highly-paid, extremely educated and learned journalists. And it takes time to research and write -- you can't get quality analysis and context 2 hours after an event.
The best example of quality reporting that comes to mind for weekly news is The Economist. Although there is also some excellent long-form journalism in the New Yorker, The Atlantic, Rolling Stone, Vanity Fair, etc. And if we're talking about online, for me the whole point of Instapaper is to bookmark these articles to read later.
And I really don't see how crowd-sourced content is the future for news. Most good Wikipedia articles take months if not years to build up. I just don't see how approaching the quality level of The Economist is possible with crowd-sourcing. The kind of people who have the kind of extreme skills and education to write at that level, do it for a living, not for fun on the Internet.
Luckily for me there is a market for premium financial journalism (the recognisable sources cited poll at the lower end of the spectrum in terms of annual cost). For other types of news, however, my willingness to pay for quality is too small a market. In the space left behind we get people cribbing about news aggregators and paywalls.
Online news need a whole new revenue model that can support and encourage quality journalism instead of chasing ad impressions that encourages or perhaps demands the AOL-ification / Demand Media-ization that makes "news" a byproduct of an SEO and link bait game.
What, pray tell, is wrong with black text on a white background? Or at the very least, personal tastes being what they are, any significant contrast between text and background?
You must be able to answer the "Amazon question" if you're starting an online commerce company. If your product category makes sense on Amazon, they'll obliterate your margins the second you're successful by using revenues from high-margin categories (think: AWS, e-books, etc.) to subsidize low prices for products in your category.
That's when the acquisition offer comes. Just ask Zappos or Quidsi. Who has the leverage in that situation?
It's harder, but if you sell something nobody else does† and successfully brand it, Amazon won't ever be able to compete. If J.Crew, GAP, LVMH, Hermès, etc. ever go out of business it won't be because of Amazon.
†: Vertical integration, i.e., "making your own stuff," is just one way to satisfy this condition.
So far it's the only to really work, but companies like Shoptiques are trying to satisfy it other ways.
Given this, it amazes me how primitive the location features of travel guides are. When I buy a Lonely Planet guide, even as an eBook, at best I get a small, low-res map with numbers that cross-reference a list of labels that cross-reference the actual blurbs about these places! This is very slow and labor-intensive to scan. What I really want is a way to overlay the travel guide on top of my phone's Google Maps, so I can easily see my current location, any markers I've added like my hotel, and travel guides all in a single map. I want to be able to click a location marker to get the travel guide's blurb. Bonus points if I can easily combine different travel guides onto a single map (Lonely Planet, Wikitravel, etc.)
One awesome thing this would allow is for people to create and curate special-interest travel guides. For example, the Puget Sound Business Journal maintains a list of attractions called "The Geek's Guide to Seattle" (http://www.bizjournals.com/seattle/blog/techflash/2009/08/Th...). I would love to be able to search for these kinds of guides when I visit a new city and combine all of them into a single map. Sort of like Amazon Listmania lists, it would give you an opportunity to find like-minded people and what they think is cool.
This is a lot like what KML allows in Google Earth (and maybe Google Maps too?) but very few people use this format and the workflows for using KML in this way don't seem to be very streamlined (for example, it appears you can "import" a KML file into maps, but you can't subscribe to one by URL).
Established content providers for travel guides might not like this approach because it commoditizes them, but I think it would help the best content to ultimately win out.
Many of us in the '90s were burned by the CDDB/Gracenote debacle, which was my first unpleasant encounter with the problem. My experience contributing lyrics to songmeanings.net, which used to be a community-run/crowdsourced lyrics repository, not full of pop-up ringtone ads, was similarly negative.
Since then, I contribute only to nonprofits that seem to have some long-term credibility with their data licensing and governance, such as Wikipedia, Musicbrainz, and OpenStreetMap. In principle I'd contribute to a for-profit if it were really convincing about its long-term good faith (and provided data export), but the bar is high.
Incidentally, my favorite use of Wikitravel has nothing to do with travel -- using it for a more candid or colorful take on a place than the drier treatment you'll find on its Wikipedia page. A Wikitravel page often leads with facts and images that IMHO are more interesting than stats, rankings, etymology, and history (which is how most Wikipedia place articles start).
- More pins, enabling more input/output. While there are some projects that only need a few pins, larger ones like big interactive light installations benefit from more
- Almost all pins are analog or digital compatible, with a few high current digital ones
- Compatible with Arduino header boards
- Better IDE
- Included ADC (two types, one can drive CD-quality audio), DACs, comparators, op-amps for bufferring, capacitive sensiving. These remove the need for a lot of external stuff to make simple and common things.
As someone who already has a stack of Arduinos, a PIC programmer, and a handful of Raspberry Pi's... this is still something that is unique and relevant. Pretty awesome and I hope it makes its funding goal.
Does it works on Linux or mac?.
It that software opensource?
Why then I should choose this thing instead of more powerful and closed micros like this?:http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_P...
Otherwise I wouldn't even bother.
What is interesting is the ability to program them via a graphical drag and drop style visual programming language and that is something for people learning that will appeal strongly. As for the specs and abilities I shall leave that to those more vested in this microcontroller.
They chose a crowded traffic-clogged endless concrete jungle, over the airy, green, lush beachside tropical paradise of Rio?
At least it says they went to Rio on long weekends.
I can see how it kinda makes sense, a bit of fun, and a bit of holiday, good team building and so on, but its not something that appeals to me. Maybe, probably, I'm just too old....
Edit - it also probably helps that I live in a town with good weather all year round.
Well, I didn't keep have a specific goal at first, actually. I just know that I gotta write something. So I did, and eventually got a specific goal later. The fruit of labor thus far is one essay an a page full of half completed random essays that are constantly evolving.
These are the result:
1. http://kibabase.com/articles/notes-and-thoughts The page of random essays totaling to 7.5 K words)
2. http://kibabase.com/articles/self-quantification (A 2K words essay)
Well, I didn't produce much, but that's only for about two months. It just mean that I need to keep writing constantly.
As an American living in Denmark, I would personally prefer to bootstrap a business here rather than in the U.S., though it does depend on what kind of business. The main advantage to doing it here, imo, is that the healthcare story is solved, though maybe that'll be better in the U.S. after PPACA comes into effect in 2014. Another plus is better government support for small businesses: grants are available, and you can get some cheap early part-time employees by participating in subsidized internship programs intended to "upskill" people on unemployment. The main downside is high wages (though that matters less in tech, where wages are very high in the US, too), less access to venture capital if you're going the non-bootstrapping route, and some general problems from not being in the U.S. (less media visibility, problems with payment gateways, etc.).
- Lack of "drive". Young people mostly want to find a nice job and that's it. In my perception this is less in France, where people may want to "kick ass" more (historical pride maybe) and maybe in the UK or Germany
- People are 'naive', and by that I mean the sentiment "this is the way it is, don't bother changing". Since everything pretty much works, it's difficult to see faults (or maybe faults enough to motivate a change)
- People in Europe need more hand-holding. They are usually more theoretical as well instead of "go there and do it", something is much stronger in the American continent (which goes from Canada all the way to Uruguai/Argentina/Chile in the south)
- Labor laws, difficulty in getting talent outside of the EU (depends on the country really - still, usually easier than getting an H1B)
Also, every country has its quirks: French cannot speak english to save their lives (usually)
In the end, Europe has a lot of opportunities, they have only to think outside of the box. But don't be so quick to count them out, they have literally thousands of years of experience.
That said, I do really feel the 'good enough' vibe here in the EU; most people I talk to who have companies (just started or older) have the 'it's good enough this way' attitude. 'We' generally don't want to be billionaires or even have billion Euro companies. Once you are making insane profit margins and have a fat company bank account, all employees are happy, growth is stopped and the goal becomes to sustain that situation. I know great entrepreneurs here who started out with crazy plans; once hitting that point (and that can be any revenue mind you; for some companies it's E10 million/year, for others it's E100 million/year, but rarely more than that) they find it good enough. I think a lot stems from that feeling of not actually wanting to be 'the biggest', just wanting a stable, sustainable company producing profit margins year after year to lick your fingers by.
Edit: read the comments; 500 biggest companies in the world, 132 US, 166 EU and France has more than the UK. Didn't check those things, just copying here for completeness.
I've been starting businesses in two very different European countries, and lived in a third, just like I've been living in America. And I certainly don't believe America is equipped with better laws for entrepreneurs or with a more risk encouraging mentality.
It's the welfare state and related systems. But not a Ron Paul style get rid of the lot, we should recognise that unemployment and welfare payments make a huge amount of short term sense. We do not want a skilled worker made redundant to lose house and family becaause it takes three months to find a job.
But we should look carefully at long term welfare payments (long term unemployment, chronic disability and especially retirement). Just when we should change the expectation from how many jobs did you apply for, to how many customers did you advertise to is important not only for an entrepreneurial society, but a sane and fair one.
Look for work for three months, then look to create a company, and welfare will support you.
Most importantly I would change the focus for those under 24, whose first encounter with welfare (pretty much all school leavers and graduates in this climate it seems) should be a positive creative experience, not a dismal on the scrap heap one
Come on Economist, money lending at rates the Kray twins used to do is not an indicator of a functioning entrepreneurial society
Other than that usual Economist quality
I don't agree that the various EU governments are starting to "get it". It's the entire contrary for a lot of countries.
There are very, very few, say, EU success software stories (SAP! Yeah. German. Not french). And it's not just software and that is for a very good reason.
In some countries like France and all the other socialo-communist EU countries people are not just looking with a very bad eye entrepreneurs who failed: they're also and, most importantly, developing a hatred of people who work hard and a hatred for the fruit of hardwork (they hate both success and money, success and money being related but not identical).
So there's this entire mindset which is ruining, for example, the France economy and it's ruining it fast. Rich people are leaving the country (Belgium, Switzerland and the U.S. all being destinations now seeing more and more rich french persons coming).
The unions here are way too strong and SMEs and independents are seen as people you should milk as much as you can.
And for those who "succeed", don't you dare to buy a Porsche because you'll then be seen as an "ennemy of the (socialo-communist) state".
Honestly it is sad but France is deserving what it is getting now: recession, SMEs going bankrupt, big companies delocalizing, rich people fleeing, they're debt skyrocketing (91% of the GDP), the GDP that shall fall (0% Q2 growth and now a recession that shall start), the loss of its status as the world's fifth biggest power (should be in 6th place by the end of Hollande's mandate).
Socialo-communist countries spreading the hate of succesful people can only go one way: mediocrity.
France and it's crazy wellfare system is going the way Greece and Spain went. This is only the beginning of the eurocrisis and it shall get uglier by the day. Unemployment is going to skyrocket. In the end debt shall need to be monetized and we'll see a massive drop in the value of the euro.
Because what we're seeing now is a joke compared to what is coming: how is France going to save its sinking economy without investors, without entrepreneurs and without people willing to work?
Want an example as to how crazy the socialo-communists are in a lot of European countries? In Spain in 5 years 210 000 SMEs went bankrupt. Unemployment is sky-high and Spain is probably going to default (it's debt is "low" compared to its GDP but its GDP is falling and its debt is taking +9% per year... It's only a matter of time before Spain becomes the new Greece). So 210 000 SMEs bankrupt: can you imagine how many people previously unemployed are now without a job? And you know what the public servants do? Public servants who have a friggin' job working for the state do protest in the street because they had a 3% cut on their salary.
A 3% cut and they protest in the street. While a lot of people who previously had job working in the private sector don't even have a job anymore.
That is why all these socialo-communist state are fcked. It's over for them. The "sense of entitlement" of the people working for the state is way too important and the part of the state in the economy of these socialo-communist countries is way too important too. There is no way out.
And that is just today... What about tomorrow?
Well, entrepreneurs are way less prone to create a gig in France (or in Spain). They're moving to greener pasture. I've got friends who created companies in the U.S. (SoCal) and in Asia (Tokyo). Why would they stay here in France?
Why would I* stay? You see, now I may be pitching soon: I'm frequenting the local "startup" scene but I already have contacts outside Europe. I'm (of course) willing to move: should I succeed in France I'd be not only milked like a cow to pay for the 56% of the french economy that is directly directed by the state (that number only went up and up: France shall soon default, just like Greece, it's only a matter of time) but I'd also be regarded as a greedy rich bastard responsible for some perceived slavery (which, ironically, is of course the fault of the socialo-communist state and the way-too-greedy state system).
If you live in the U.S. I'd seriously have you consider to not vote for Obama: the public debt of your country never exploded as much than after five years of Obama. That wellfare system and the sense of entitlement it creates shall lead to a socialist country. This has always been the plan of leftists: create a gigantic number of state jobs and promise more and more wellfare, to make sure to get reelected. Once you're too entrenched into socialism the only way out is default.
And then once the nany state defaults you'll get tyranny.
Oh, sure, for a few years your shiny healthcare system shall look nice. And then the discfonctional system shall be hidden under more and more debt.
And then you'll default, just like Greece. Just like Spain is going to. Just like France is going to.
It's not that I'm not a good person. It's not that I wouldn't want everybody to get a good healthcare system. But the only thing socialism leads to is poverty for everyone, besides the leaders. Don't forget where you're coming from and what made your country so great.
It's all a matter of choice: do you want REALLY good conditions for the top 10% or decent conditions for everyone?
Economies like China, the USA or Canada favor the former, lots of European countries the latter.
I stopped reading there. I must be living on another planet entirely from whoever wrote this article.
I laugh at the media-fabricated 'Euro crisis' and the 'Economist'.
I think a lot of this stuff is due to the attitude of the general population towards entrepreneurs. If the only question that matters to people is "Have you made any revenue yet?" there's probably not much hope for Europe ever catching up with the US in terms of new fast-growing tech businesses.
(I'm hoping the UK is something of an exception, but I'm not really sure. Lots of people here are still very sceptical or pessimistic about new tech companies, especially very small, innovative ones.)
So I was really interested in trying out this fork. A couple of problems:
* Doesn't look like tiling is automatic, you still have to tell each window which side of the screen to tile on (by using Command+Option)
* I was using it for a minute before it crashed - which I didn't even notice
If those two little problems were fixed I think I could definitely use this until I get my version of Xmonad working properly.
Is this the new definition of a tiling window manager?
I've felt so useless on OSX after having started using a dynamic tiling wm at work.
edit:Ah, just saw the link to http://spectacleapp.com/
ShiftIt @1.5 (aqua) Managing windows size and position in OS X
tl;dr: <3, Jacob and I quit Twitter, he's going to Obvious, I'm going to GitHub, it's been amazing, nothing but love, Twitter is great, no ill will, Bootstrap is going to keep going, <3.
First, thanks for the love everyone! Jacob and I love seeing people as excited about the future of Bootstrap as us. We're hopeful that this is just the beginning of it. And now, onto answering some of the questions/comments folks have brought up here thus far.
Jacob left over a month ago and my last day is next Friday (10/5). He's going to Obvious, and (announcing it here for the first time) I'm going to GitHub.
The timing has nothing to do with a disagreement about Bootstrap (seriously, none what so ever), and more to do with us both wanting a change in our own lives for what we do day-to-day. Twitter, the company and product, are both amazing and Jacob and I have worked there for 2.5 years. We're stoked for our next things and we both want to keep working on Bootstrap no matter what. We have an obligation to the community and know it could go much further. (Oh, and yes, I screwed up the date on the post. My bad, yo.)
Bootstrap was created by me at Twitter as a means to make better looking internal tools (I wrote about this on A List Apart awhile back: http://www.alistapart.com/articles/building-twitter-bootstra...). It started off as a simple HTML/CSS thing, then Jacob built plugins on top of it, and we open sourced it together. We made it at Twitter, so when we wanted to open source it, we went to Twitter to ensure it was good to go. Thus, it was named Twitter Bootstrap (originally, "Bootstrap, from Twitter" actually). Now, it's back to just "Bootstrap".
We don't really think of it as the next jQuery, Django, or Drupal. But you can't deny there is something to front-end frameworks like Bootstrap, and that's what we're excited about. HTML and CSS are the two easiest and most basic building blocks of websites. Everyone knows and uses them, and that's a big part of why Bootstrap has grown so much, and can continue to grow more.
The move to making Bootstrap its own project and organization is a joint one, between myself, Jacob, and Twitter's Open Source team (@cra). The transition will take time, but we need to grow Bootstrap beyond the two of us and Twitter, and into something more. There is really sooooo much potential for making better things on the Web, and we're hoping we can keep that up with the help of the community.
Anyway, we're both stoked to keep working on Bootstrap. It's a great project that can be so much better, and that's pretty damned awesome to us. Twitter has been amazing for both of us and will continue to down the road. We wish nothing but the best for everyone we've worked with.
Major kudos to the team and to Twitter for having the generosity to acknowledge a responsibility to the community that extends past their ownership of the project they've created. Thanks. :)
Just looking at the caliber of other projects that have gone this way (at the top of my head: Apache, Drupal, Django, Zope...) and looking at Boostrap I don't think it's even close to the userbase/clout needed to pull this off. Even the maintainers of those other projects, successful as they are, tend to have a day job.
I don't know, maybe I'm reading too much into this, but I think it might be a little to early to make this move. Just my 2c.
This is a new engine, without figuring what causes those fractures, NTBS should ground them. I bet they already know what it is.
My father (37 year of flying) always tell me stories where engines in the industry had vibration resonance problems that caused fractures in the whole airplane those engines never ended up flying.
(this is serious because - as far as i can tell - this engine has a 330 minute ETOPS rating http://www.geaviation.com/press/genx/genx_20120308.html http://en.wikipedia.org/wiki/ETOPS which means that a twin engine plane (like the dreamliner) can fly 5.5 hours (the number in the report above) from "safety" (eg over the atlantic), so if one engine fails the other must continue working for that time. if the problem is common then that is not so reasonable an assumption...)
(not all dreamliners are affected; rolls royce also provide engines)
Mandatory warning: please don't use those unless you really know what you're doing. Most modern CPUs have instructions for computing all of that stuff and the compiler will try to use them. Those clever hacks might actually hurt both readability and performance if they're misused.
Typically on PC architectures (and even on most modern embedded systems) you shouldn't have to use those hacks.
Hackers are not heroes. Certain individuals out there are heroes. They aren't all hackers. They're people from all walks of life and professions, at varying skill levels who do something at great risk, who often sacrifice something, and do something for the good of one or many people. The term hero can be very subjective and I am not comfortable labeling a group of people or even a subset of a group of people as heroes. The fact that someone wrote an article like this just leaves a bad taste in my mouth. Hackers, you're not heroes. Only heroes are heroes.
A hero is somebody who goes further than others even imagined, it is always a label bestowed upon somebody by others. Hacker is a mindset and when it is bestowed by others is generaly refering to some electronic vandalism.
Using a bic pen to perform a trachyotomy so somebody can breath, that would be a hero hacker if such a definition was needed.
Systems always have weaknesses and systems always change. Sometimes we improve the weaknesses for fun or profit or usefulness, sometimes we attack them for fun or profit or malice.
Not one person posting on HN and the many blogs really knows what happened behind the scenes. Apple engineers are not known for being dumb. Someone had to know that Maps was a bad idea. A huge step backwards. They had to know.
So the question might very well be: Why did they do it?
This couldn't have been out of spite. Just to kick Google off the platform. One just doesn't do that. Maintaining a complex code-base such as iOS is difficult enough. Adding to that the friction of delivering a substandard product is not something one does without very good reasons.
Conjecture is all we have from the outside. My humble guess is that it had to come down to a business deal they did not want to make. The details of the deal are not important. Who was right and who was wrong isn't important. What is important is that whatever they had in front of them convinced Apple management that it they had no choice but to, effectively, downgrade the next release with Maps.
I already know of a lot of non-tech people, particularly outside the US, who are livid about Maps. After dutifully upgrading their devices to iOS 6 they discover that Maps are, in their words, "crap", "useless", "unreliable", "a joke", "not accurate", "una mierda" (shit), etc. The reason for the strong feelings is that, let's face it, if a good tool such as Google Maps is available to you, you might tend to use it.
And a lot of people would use it all the time. My own wife relies on Google Maps all the time. Thankfully she was wise enough to marry a geek who promptly told her not to upgrade her iPhone 4S to iOS 6 and not to swap it out for an iPhone 5. In fact, not one person in my family will do either of those things. And that is the case --that has to be the case-- for millions of people at this point.
This is the data we are not getting and that Apple will probably never release. I own eight iOS devices. Not one of them will be upgraded to iOS 6. In fact, the upgrades stop here until either Maps starts to get really good marks. And, of course, we probably would have purchased at least three iPhone 5's. Not happening. I'll get one for development but it will not be activated.
How many millions are in this boat? If someone is a heavy Google Maps user it makes no sense to get an iPhone 5. What's wrong with a 4S? Nothing. Use their website you say? Not the same, most would say.
As a developer there's a lesson that needs reinforcing every-so-often. What better way to reinforce it than to see a tech giant make some of the mistakes lesser companies make: If you can at all help it, don't base your product on someone else's technology. Don't make someone else's technology such an important part of your offering that not having them will hurt you. Of course, sometimes you have no choice.
As a user and a developer I view iOS 6 as a significant, if not huge, step backwards. Between Maps and the eviscerated app store one has to ask that cliche-ish question: What were they thinking?
Wouldn't we like to know.
I'm yet to read the paper, but the comment highlighted in the thread from Wednesday raises some points. For ease of access I'll re-replicate it here;
"This is just a PCR study. No evidence that the foreign human DNA even entered host cells, much less that it was expressed. Probably shows only that minute quantities of foreign human DNA can hang around a host body for a while. Most likely explanation is that it gets bound up in the extracellular matrix. Being that the DNA is of human origin, it would not trigger an immune response, but rather, it would just be slowly degraded like the host's own DNA when it is released from dead cells (part of the normal, perpetual turnover of cells). DNA is hardy stuff; people have sequenced DNA from Neanderthal bones.Study co-author J. Lee Nelson's comments are ridiculous hype. He should be ashamed of himself. That those comments were published in this newspaper uncritically is also an embarrassment.This work was published in PLoS ONE. PLoS ONE articles are peer reviewed only for the validity of the methods used, not for the importance of the subject matter or the validity of the conclusions drawn. This is where you can publish all sorts of meaningless crap."
I disagree with the extremity of the commentor's view on PLoS ONE articles, and feel they should perhaps have noticed that Dr. Nelson is a lady, not a dude, but still something worth considering.
 - http://www.latimes.com/health/boostershots/la-heb-women-brai... , comment 2
They do use the phrase "male cells of fetal origin" but they don't explain why these are male cells. There are several possible explanations, and I am curious which one is true here. Again, they could be talking about a type of expression that relates to Y chromosome. But there was last year the interesting study that suggested end-stage cells know their sex through a process we do not yet fully understand. So what is this study actually saying? I wish they had clarified what "male DNA" means in this context.
Fetus donates stem cells to heal mother's heart: http://www.newscientist.com/article/dn21185-fetus-donates-st...
Baby/mother cell exchange:http://kottke.org/12/01/babymother-cell-exchange
The iOS 6 Maps app is an excellent client. Its only problem is with the data it fetches from Apple. Their maps data is very new and rather less polished.
It is silly to compare the two. Building a worldwide database of map data is orders of magnitude more difficult than writing an iPhone app.
Edit: This comment was a response to OP's headline, which was "Apple built original Maps app in three weeks". He has since changed the headline.
They also refer to Tim Cook as "Timothy D. Cook, Apple's chief executive," which honestly baffles me for some reason. I suppose it's just strange seeing an article not refer to him as just Tim Cook (which is what everyone else would use, including Apple). They also seem unable to spell "iPhone" correctly when it begins an article.
At any rate, I think the Apple's own page is sufficient unless something unique is added, and I just don't get the impression that the NYT is doing that. If anything, they're actually ignoring aspects of the message: there's no mention of the alternatives Apple suggested, including Bing. I personally found that interesting, and to ignore it seems a little strange.
I however, haven't been able to attract any serious content creator.
I believe this kind of approach is good at solving the two main problems we usually face in projects:1) Getting started2) Delivering at least something
(If you have contacts with one, please forward the idea. Come on HN, let's make this happen)
Another way to look at the issue: who's fault is it that you don't know the key people behind the browse engine that powers Safari and Chrome and is dominating the mobile web?
What dotted line? A free developer account lets you access all WWDC videos since 2010.
Also not sure what you mean by "sign on the dotted line." The Safari developer program only requires you to create an Apple dev account and is otherwise free. So are all WWDC videos if you simply have an account, regardless of whether you're in any program.