UI blunderz

Menzis: somebody's been php'in ... A `$` is not always a positive thing to see, especially in the title of your favourite website not be rendered, but a value replaced where this variable $name appears). So, hopefully the general health of the website is otherwise acceptable... More seriously, such  Source code  disclosure  ('code leak thru') bugs can indicate security faults : when code fails to render, it may inadvertently leak algorithm details or even worse connection strings and other sensitive details that a hacker may exploit...

Amsterdam lights are on ... but the license lights are out. This seems unfortunate. It's kind of understandable if you have some software on a laptop that has an out of date license. But to build a website that has unpaid for software (Google Maps here) seems doubly unfortunate, and perhaps even a little careless... but the good news is, the website basically still worked...

A friendly  Visual Studio  dialog Microsoft have a mixed history of reaching and maintain UX standards. Although admittedly the standards have risen greatly in the last 2 decades in particular, partly due to the increase in raw CPU and video of typical devices, there were early bad signs with for example the MSDOS prompt and its appalling BAT script environment, compared to the contemporary UNIX OS. Here, Visual Studio has some kind of generic error message, with a horrid modal (blocks all user input) dialog and a matchingly horrid design. Yuk, indeed.