I hope the UK remains stable and grows even after leaving the EU. It's sad to see the most common sentiment among remain voters is to hope everything about the UK will crash and burn because results weren't what they expected.
My thoughts exactly. To be honest, I'll be surprised if we do actually leave the EU. Even the staunchest leavers seemed a bit worried this morning about what happens next.
In the short run, things will be bad. In the long run, nobody has any idea. It's the medium term where the real threats lie - how long it takes to leave, what terms we get from the EU, and how eager the rest of the world is to set up direct relationships with us.
I'm not going to rule out that the EU will see this as such an existential threat that they will change enough that a future government will be able to make the case for staying in after all. I know that Juncker said no to that, but today has made his position untenable as well.
It's perfectly fine. Just go through the naturalization process that is available to you, swear allegiance to the Queen and you can have your say in the country's future.
Being a citizen is more than being a tax payer or generating wealth.
Isn’t it absurd that as someone who lives somewhere and pay their taxes you can’t have a say on local politics, just because you don’t have a piece of paper that says you have the right nationality? As a French I can live 10 years outside of the country and still vote for the mayor of Paris. You don’t even need to live in Europe to vote for European elections if you have that paper that says you’re “French”.
> If you have a huge nose or a massive protruding mole you'll never be attractive no matter your body composition
BULLSHIT. I was very self conscious of my big nose but Asian women love it! The first time I heard 'I like your nose! it's so nice' I couldn't believe it.
I had to turn off notifications for Tinder because it's so active after 11:00PM.
They'd still be burning the furniture to make quarterly numbers look good? Mark Hurd had no idea what to do with an engineering company. Making numbers look good by cutting costs and reallocating assets was his only skill.
I'd wager that this - the notion that school is for a degree, abstract from challenging oneself to learn anything is a healthy contributor the apparent glut of 'uderemployed' graduates.
>A few years from now no one will care about your GPA, let alone your final year project.
Perhaps, but they'll certainly have more to gain from someone who cares about doing quality work and is willing to challenge themselves.
Further, it's not an entirely safe assumption that you'll even be capable doing 'the cool stuff later', particularly without having tried.
I actually disagree. If you feel compelled to do something cool, do it. This is a great opportunity to challenge yourself. And someone will care about the project you do -- you will. Never do anything but your best.
But to the other posters merit, if you can't narrow down what it is you want to do, then pick a "boring" thing -- it's better than nothing at all.
"Build the cool stuff later."
Later becomes until I have dont need to pay the bills.
Then it becomes until my kids get older.
Then it becomes until I'm retired.
Then it becomes until I'm out of my deathbed.
So for how long will the python community pretend that performance isn't a problem? (Inb4 "all the intensive parts of my app are written in C", addendum: "my app isn't CPU bound", "we have libraries written in C")
The interpreters (esp CPython) need some hardcore engineering (like how javascript got V8). Languages that have the same theoretical performance limits of Python are now blowing it out of the water.
The stories about teams that were able to go down from N servers to 1 server by switching from Python to Go/Scala/node.js will hurt it in the long run.
> So for how long will the python community pretend that performance isn't a problem?
Which python community are you talking about? Cython, numba, numpy, pypy?
> The stories about teams that were able to go down from N servers to 1 server by switching from Python to Go/Scala/node.js will hurt it in the long run.
Have you followed anything that is going on or just link-bait articles? Nearly everyone that re-implements something in another language uses different paradigms during the re-implementation, because they've learned something from the original implementation. Besides, those articles normally don't discuss any of the opportunity cost of re-invention or the long-term maintenance costs. I'm not saying they can't improve those things, but until you have the TCO over a few years, it's not an accurate portrayal.
The large amount of excellent work being done on PyPy would seem to indicate that the Python community does not, in fact, pretend that performance isn't a problem.
I don't think it is denial per se, but rather mostly inertia. Python has been a victim of CPython's success, in the sense that there is now a huge body of work that is tied to the CPython API. This is a problem for IronPython and Jython, and continues to be a problem for PyPy (though they are making strides to solve it), and it will be a problem for newer projects like Pyston. Numba has sort of skirted the issue by integrating with CPython, but the jury is still out there.
>>The stories about teams that were able to go down from N servers to 1 server by switching from Python to Go/Scala/node.js will hurt it in the long run.
concurrency designs and architecture play a greater role than the language , most of the times.
Bottle-necks are often in bad-sync patterns , data-structures or overall designs.
Language plays the role for semantic verification,formal models (for model-comparison...) ,type-system designs , proof systems etc .GIL is just one!
Can't compare language vs another.
After which the buck passes on to underlying implementation but cpython in our discussion is only thrown as a reference implementation and for production grade interpreters we might have to look outside like one by enthought.
However language's built-in patterns to help advertise concurrency is another question altogether.
Even scalable web-whatever is often IO-bound... of my several apps in production, there's only one where CPU is a serious concern, and I run that one on PyPy. cPython is fine for the others.
I'll go so far as to say that we haven't done enough with making things fast on multicore processors except with IO-bound tasks. The current architecture of multicore processors stinks for achieving anything but the "embarrassingly parallel."
I'm among those who think this organization isn't doing it right, but I'm a 'colored' developer. Does that make my opinion any more valid than the white men's ?
To me this is as beneficial as a 'white girls rap' bootcamp, but hey, whatever helps.
