Cycling fast in the city centre is just too dangerous. The (big) city centres are small and crowded. Cycling really fast would result in grave accidents. Cycling for exercise is almost exclusively done outside the cities. Another reason to keep the pace down when commuting, is to minimize sweating.
A lot of kids do this in The Netherlands. And as far as I can tell, not a lot have a problem with it. It's part of the culture. And as said by another commenter, most kids ride in groups. I think it's healthy to let kids ride on their own and take responsibility, both physically and mentally.
Euh... Yeah? Shoehorning SVG into 3D models ought to be slow. Manipulating DOM nodes for animation has it's limits. If you want 3D perf in the browser, use WebGL.
The canvas can be quite fast if used right, but again, it's not the right tool for every job.
Ok, the list is distracting. I mean, experience with web dev's ecosystem is more important than the languages you can write code in. Of course a list on it's own is useless, it should be supported with actual projects (hopefully some in production).
Why are you assuming s/he is putting up a "CRUD website in some framework"? I work with HTML, CSS and JS, but it does not tell you anything about what I'm building or how I'm building, so you should not "recognize my technical ability" based on your false assumption.
I have 0 years hiring people, my experience is this. The language(s) you write code in don't mean a thing. It's the ecosystem. I'm a JS programmer, but that is not why you should hire me, it's my experience with the DOM, HTTP, indexeddb, File API, documentFragment, Fetch API, TreeWalker, NPM, WebGL, interactive SVG, the pros and cons of React, when to use Redux, Basic login, NGINX, Docker, etc, etc, etc. My point is this: knowledge of Closure(Script) is a great tool in any programmers tool belt, but it is definitely not the most important one for a solid frontend engineer.
I think everybody who writes HTML, CSS and JS for a living experiences this. For me it's the never ending jokes about "JS was written in 9 days" and remarks on how easy it is to fix a problem, because "it's just CSS". I compare it too subtle discrimination. I am a white male and I won't pretend to know how it feels to be discriminated, but I do know how it feels too fight the uphill battle of condescending remarks. And I also play my part. I downplay what I do ("I build websites"), because I don't want to hear myself pounding my chest.
This is changing, I (think|hope). Two years ago I was building 1MB+ sites (because: SPA). Now I am down to 500KB, due to SSR and code splitting. Performance is back on the menu.
Complexity comes at a price. Making it easy, abstracts certain low level functionality away. Compare Rust to Python. Compare OpenLayers to Leaflet. Compare the dashboard of an Apache to your car's dashboard. Rust, OpenLayers en Apaches aren't bizarre, they have complex functionality which you don't want to abstract away, because you want the ability to use it on that low level.
Depends. Most of the time, I don't need any, because it's a quick 'n dirty proof of concept. For production, at work, we have a federated login, so external. For side projects, I use a good ol' Postgress table.
React, Express, Postgress, Nginx all in Docker containers managed with Docker Machine on a Digital Ocean box. It may not be the most simple/quick solution, but with some copy/pasting I can get something up rather quick and it's super flexible. Need OCR? Add a Tesseract container. Need a fileserver? Etc.
I understand that a company which has invested in these maps wants a ROI, but really, the polygons should be in the public domain and improved on accuracy. I can imagine a lot of people would be interested to work on this.
The data for the rulers I can get from WikiData <3, but are the land coverage polygons open source aka available somewhere? I would love to use them in my own projects.
Privacy first, profit second. I think that is a wise decision the EU makes (disclosure: I'm an EU citizen). 'The media' surviving on a distorted revenue model is not healthy and I will not believe it is necessary to break your customers privacy in order to make a profit.
The Dutch are quite famous for their fight against the water and have build enormous resources (companies, knowledge, public administration) for building dams and the like. Doing 'their thing' all over the world, for example, in Indonesia...
I long for the day I can use browser native import to retrieve all my modules and deps, but at this point it doesn't resolve node_modules and that makes it unusable to me and the reason I am using a bundler.
I did not downvote, but I do think JS is a bad example. JS has been active for over 20 years and is currently popular. Sure, new frameworks are popping up and everybody rallies around "the latest", but come on, it's not like Java and C# are written in stone.
Probably not sped up. What you're seeing is a sudden acceleration of the camera's viewpoint when panning to the left in order to keep up with the 1.9s to get to 60mph.
Events firing en listenTo'ing all over the place makes it really hard to reason about what will happen to your UI when state changes. The bigger the project (or the more complex the UI), the harder it is to keep track of all the events and their side effects.