I know the HN crowd is very pro-Tesla but do not underestimate traditional car-makers.
2,212 karma · joined July 9, 2012
I know the HN crowd is very pro-Tesla but do not underestimate traditional car-makers.
For smartphones I would stay at the current 2 years requirement though. A phone stays most of the time on a person, which is one of the most harsh conditions if you think about it.
The shots from this story though, I can relate. I can imagine myself (as a middle aged male) in a war going against live rounds and it is very scary. I can imagine both being a civilian, unable to do anything or a soldier going at the heart of the conflict and I hope I will never have to be in such a position.
I disagree with people saying these are good shots. In the collection another user posted ( http://www.kainoalittle.com/mosul ) there are better shots technically and artistically. Yet that the photographer chose these shots for the article speak tons. These aren't photographs to make you feel better, these are photographs to make you understand (even a tiny bit) what real war looks like and it is ugly.
This is the way politicians should operate, legislate for the future.
Place strategically a few of these antennas and you can monitor a huge area.
The catalyst was developed in EPFL and is renewable. I believe this is the one: https://www.nature.com/articles/ncomms5017
They take CO2, H2O and electricity from renewable sources to create their fuel. The secret here is the catalyst they developed. The fuel is liquid, thus stored easily.
In order to use it they use a reverse chemical process which creates H2 and CO2. The H2 burns with oxygen (and releases part of the stored energy) to produce H2O and thus they end with the elements they used in the first step.
If in its currrent capacitiy can be used for transportation, it probably can be used for many other things as well.
If they had competed and won this share fairly, they wouldn't get a fine.
Remember that EU, during these years was consistently the largest, or the second largest, depending on year, economy of the world, so this 80% is huge and justifies the size of the fine.
Opinions on the decision will sure differ among readers, but I think the decision is in place with the majority of EU citizens' consensus.
Also, an important issue with such arguments, is that generics is a feature, so obviously it is an easy side to choose for an argument. You can either have or don't have a feature. People will instinctively select the have option because common sense dictates that it is better to have something even if you don't use it. People want to quantify an argument and having is better than not having.
People don't want to argue about language design —there are few people on the planet that could really argue about language design anyway-, they need language MHz to compare.
There are many languages out there that have generics. Go is build on different principals. Just use something else, no need to enforce your ideas on people who don't want them.
Maybe go users should start going into every language discussion they can find and ask for generics to be removed.
In Greece for example, we have 3 mobile operators and they announce exactly the same changes to their plans within a couple weeks difference. Things like “we increase our basic plan by 5 euros” or “you have to top up your prepaid phone at least once every 3 months instead of 12”. This way, there is no point at switching.
Especially roaming was a golden goose until few years ago, because each telco charged termination fees for roaming subscribers. So your telco was like “I can't do much, I have to pay the foreign telco”. What happened in EU, is that by law these termination fees started getting smaller until today where they become zero.
Microsoft also does not provide a solution for Skype for Business as well which is a serious drawback imo.
Though in some cases I am quick to blame MS, in this case many of their rivals are in a similar state unfortunately.
Not only this wealth would be better distributed, but also FOSS would be widely accepted and a sought after career path. Additionally, in my experience at least, FOSS leads to better professionals. My limited sample, says that a junior developer that can read the source of the library he uses, grows to be a better senior developer than the one that can't.
I am all for entrepreneurship and I do think that companies and competition create progress. But when one company reaches the level of Microsoft, where every year we learn how many billions Bill Gates' bank account increased —I do know that he helps with his money but still, his bank account does increase—, it just takes money off the market. Hoarding is bad.
I've seen it upfront two times in the playstore, where apps I liked released a new version. I was eager to buy the new version but the new/updated reviews for the old ones were ruthless. One app had to give the new version for free. The other had to promise to keep updating the old version too. The first team just gave up on both apps. The second team (one developer actually) continued but slowly toned down his efforts, going into essentially maintenance mode.
Anyway, in the 60s the profession was in its infancy, so I'm not sure how much studies from this era matter today.
I can set up both nginx and apache (and get paid for it), I've automated LE for new sites via ansible, etc. Nowadays if I can do with caddy, I just use that and proceed to the next task. Also remember that easy (and short) configuration means easier maintenance.
Devs also love it, they can develop locally using advanced functionality (e.g proxying an API that doesn't provide CORS).
However most companies out there aren't Facebook, Google, Oracle, Coca Cola or Nike anyway.
Maybe the town could add a tall plate next to each statue, with information about the creator, the installment date, etc and let people who care enough, to judge themselves.
My solution around this, is, when regexp is enabled, to query for all the history and then have Go perform the regexp search itself —the normal is to let SQLite perform the search.
Depending on your CPU and history size, you may need a couple seconds for the result. For example when the server process runs on an Atom processor and the history is about 150.000 lines long, a regexp search takes about 7 seconds. A normal search with a wildcard on the same machine and history database, needs only 1 second.
Written in go, uses sqlite and can work locally or remotely. In the latter case you can send history from many accounts and search globally. Transport encryption is based on NaCl. One binary serves all roles.
Doesn't store other information than command line and time but this is what I need most of time.
The main pain point behind its creation was searching in history. There is a global flag (search in all accounts, -g), the wild card is SQL's wild card (%). Less frequently used but very helpful, content search (-A, -B, -C, like grep). Also regexp is supported though very rarely is needed.
Furthermore, for many people, using the command line is part of their daily job. Not keeping a history and/or log, is akin to compiling your source code, keeping the binary and deleting the source.
If there are certain things you don't want in your bash history, use the ignorespace capability and explicitly do not store them.
If the flight was canceled, the contract wouldn't be moot but the case would need to be resolved outside the plane anyway. As the plane wouldn't be anymore part of the problem, the airline could ask for the passenger to be removed on the ground that he was trespassing. The passenger could also ask the police make sure that the plane stays grounded.