Of 3 million residents, maybe a few thousand - at most - will be full-time politically committed and active.
The problem isn't the numbers, it's breaking into the patronage and power networks. That's not a numbers game. It's a relationship, influence, and networking game. And some elements will be corrupt, while others will be about carefully cultivated appearance management.
We were so close to having ranked ballots for Toronto which is exactly what we need to improve accountabilituy, but Dougie scrapped that for all Ontario cities. Hopefully we'll get things back on track. https://www.unlockdemocracy.ca/123ontariohttps://www.rabit.ca/
Becoming actively involved in politics is a quixotic endeavour with a high personal cost and very low chances of success. Moving out has much lower cost and much higher chances of solving your problem.
Thank goodness some people get into politics anyway, but it is not a rational choice for a utility-maximizing actor.
It's actually not hard to get into local politics and you can certainly get things done. There's not a lot of competition or money involved and most people haven't figured out you can do it yet. Mainly what happens is older people will scream at you when you say you want a bike lane.
It does take a lot of patience though; you won't get much done in the first year or two.
Forgive my naivete but yes, that's how change happens?
If we look at social movements of the past century, they weren't easy on the members but many of them were successful in bringing about change.
I don't know when it became fashionable to only do things that guarantee success within your lifetime and openly dismiss any other way of life but that's not how people who actually make a difference live.
It's a million times easier to just move away than it is to change anything about a global problem in a city with millions of people. Making a difference doesn't solve personal problems.
Highline BETA combines the assets and experience of leading enterprises, the agility of startup founders, and the methodology of investors to launch new ventures. We're building a new model for corporate innovation and startup investing.
We've got a lot of interesting projects in the near-term and are looking for strong, entrepreneurial developers to help us build new companies.
Specifically looking for React Native specialists, but also for full-stack generalists who like working with React, Node.js, Elixir/Phoenix, AWS, etc.
We believe that diverse teams build better companies and better products. We encourage applications from qualified candidates from all backgrounds, including candidates of colour, women, queer candidates, candidates with family caregiving responsibilities, immigrant candidates, transgender candidates, and candidates with disabilities.
Shoot me an email: rohan@highlinebeta.com with questions/inquiries.
There are some confusions in that post -- perhaps understandable, as trying to deduce things from code review alone is tricky -- but Grisha and I have been communicating and hopefully it'll be updated.
React is a view framework, and knowing the internals of React is a completely unnecessary set of knowledge for the majority of developers using it to build products with.
As with anything, the longer you use a library, the more you must know at least some of it's internals to use it efficiently/axiomatically/well. Even something small like the class/className attribute thing is an implementation detail that leaked through, which will bite and likely confuse a beginner for 3 seconds if they didn't throughly read the docs.
Other libraries don't have that problem (because they didn't accept that trade-off in that fashion).
IMO Libraries that beginners should be shown should not be ES2015-in-every-example, and introducing transpiled DSLs for generating DOM elements.
Some people in the thread you linked to recommend lazy loading, another idea would be to use a bloom filter – I used this in a project to check server-side for hashes of (MMs of) common passwords.
Excuse me, it's less than one MB for actually useful (and rarely used) functionality, in a time when many websites routinely weigh in at several MegaBytes for tracking, advertisements, silly pictures and other cruft.
It is very noble that you are concerned about page size (seriously, I frequently travel and am on awfully slow WiFi or mobile networks (remember GPRS and Edge?) and hate wasteful websites with a passion) - but I'd much rather you remove all the other cruft (seriously, how much can two fields for "Enter username and password" take?) and include the most excellent zxcvbn.
