news.volyx.in

The Well-Tempered Traveler (google.com)

483 points by nvahalik · 1898 days ago · 172 comments on HN

Article summary

The article appears to be about a web application called The Well-Tempered Traveler, hosted on the google.com domain, which features a unique and uncompressed implementation of HTML and JS. The application's existence and accessibility have sparked interest and discussion among users. The project's code is available on GitHub, and its development and hosting raise questions about ownership and intellectual property. The application's functionality and features are not fully described in the comments, but users have noted its quirky behavior and arbitrary city selection.

Main themes

  • custom stack vs common framework
  • security and exploits
  • intellectual property and ownership
  • company policies and laws
  • personal projects and moonlighting
  • Google's development practices

What commenters say

  • Using a custom stack can make it more difficult for attackers to exploit, but it may not provide the same level of protection as using a well-maintained and widely-used framework.
  • A custom framework may be more secure than a common one because it is less likely to be targeted by automated exploits.
  • The use of a personal stack can make it harder for determined hackers to find vulnerabilities, but it may also make it more difficult to maintain and update.
  • Google's policy of claiming ownership of employee-created code, even if developed on personal time and with personal resources, is a common practice in the industry.
  • California law provides some protection for employees who develop personal projects on their own time and with their own resources, but the company may still try to claim ownership.
  • The ownership of personal projects developed using company resources or equipment is often unclear and may depend on the specific circumstances and company policies.
  • Some companies, like Microsoft, have more permissive policies regarding employee-developed projects, and may even encourage moonlighting and personal projects.
  • The development and hosting of personal projects on company infrastructure can raise questions about ownership and intellectual property, and may be subject to company policies and laws.