varsock

I'd really want to know what's driving them

likely ego

I heard in their Q3 2023 quarterly earnings call that 6 years ago they left a PCIe slot free in every server so they could accommodate upgrades in the future as they grew. They were suspecting it'd be with the boom of AI/graphics cards but didn't want to commit to it yet.

Now they are plugging up that empty PCIe slot with newest gen graphics cards with their launch of Workers AI.

This is cool because they had foresight to make an uncomfortable decision initially but were able to respond to their growth objectives without spending capital expense to upgrade the entire servers.

Their recent blog on the design of the new servers is mostly around temperature, efficiency, and rack density. So unfortunately no hints at what's to come.

This is interesting. Don't have an opinion on it yet.

I wonder what effect this will have on developers' code reuse practices and how it comes across in the interview.

At work I often look at my previous work for how to do boilerplate stuff. And in my recent interview experience I had more opportunities to use the internet and other examples. Very practical

When I was in college, two older classmates whom I respected got into a hilarious argument of why Gnome was awesome and now eats rocks (their views, I had no views).

Their elaborate and very specific descriptions of functions and inconveniences drew up a picture of functionality and a e s t h e t i c I had never experienced on windows. So I proceeded to install a distro and take it for a ride

I would appretiate if someone could explain the practical utility of snippets because it just dawned on me how useful they might be.

The letter is a post on his own blog . Hard to distill into a summary so I recommend reading it get more context. But it seems to have boiled down to:

• How It Was:

  • Strong adherence to the "don't be evil" ethos, focusing on societal good over profits.
  • Open, transparent communication and decision-making processes.
  • High morale, with a culture of learning from successes and failures.
  • Work focused on benefitting the web and users, rather than Google's immediate interests.
  • Collaboration and lack of internal silos, encouraging innovation and autonomy.

• How It Is Now:

  • Shift from user-centric to Google-centric, and then to individual-centric decision making.
  • Eroded transparency and increase in organizational silos.
  • Decline in morale and a culture of distrust between employees and management.
  • Focus on short-term financial gains leading to layoffs and defensive employee behavior.
  • Lack of clear vision and leadership, resulting in confused and ineffective management.
  • Overall deterioration of Google's unique, innovative culture and values.

cool. yeah you would know best, I see you're very involved on this instance

I've actually found his blog where he talks about this "optimistic merge"

http://hintjens.com/blog:106

any utility in enforcing/suggesting a post template that address (for example)

1. What task are you accomplishing with this code?
2. How is it implemented (give an overview of your solution)?
3. Why did you choose this approach (if several valid approaches exist)?
4. What specifically, if anything, do you want suggestions on. Security, best practices, etc (Optional)

There is a very effective approach (34:00), that big companies like cloudflare use, to ship a product in a fast and quality way. It bears parallels to what you are describing. In essence engineers should not get hung up in the details to trying to solve everything.

1. Just build a proof of concept
2. Discard the prototype no matter what and start from scratch keeping the initial feedback in mind
3. Build something internally that you yourself will use
4. Only once something is good enough and is used internally, then release it to beta.

So that tedious process in trying to flush out all the details before seeing a product (or open source effort) working end to end, might be premature before having the full picture.

Brave has superior fingerprint protection, they achieve this by randomizing the browsers fingerprint. Visit EFF's cover your tracks to test your browser.

To achieve the same functionality that brave achieves out of the box with Firefox I need many extensions and then when I profile both browsers, Firefox is more resource intensive. Brave's blocking is native to the browser. I will give Firefox the W because I've read that uBlock is technically more capable. But as a long time Firefox/uBlock user who switched to brave - this has not been noticable.

As for accessibility, I can configure brave to be really aggressive at ad blocking, tracking blocking, fingerprint blocking, and restricting JS even, and all those options I can set from one place instead of in different settings/extensions. When a website breaks, I click on the button next to the URL and immediately have options to granularly dial down the "protection" or add a website to my trusted list. In Firefox I was annoyed to having go through settings for the extension.

Brave plans to continue supporting Manifest V2 after Google kills it. For Ungoogled Chromium, however, it's still undecided, likely depending on whether UG contributors are willing to maintain it.

Brave has superior fingerprint protection, they achieve this by randomizing the browsers fingerprint. Visit EFF's cover your tracks to test your browser.

To achieve the same functionality that brave achieves out of the box with Firefox I need many extensions and then when I profile both browsers, Firefox is more resource intensive. Brave's blocking is native to the browser. I will give Firefox the W because I've read that uBlock is technically more capable. But as a long time Firefox/uBlock user who switched to brave - this has not been noticable.

As for accessibility, I can configure brave to be really aggressive at ad blocking, tracking blocking, fingerprint blocking, and restricting JS even, and all those options I can set from one place instead of in different settings/extensions. When a website breaks, I click on the button next to the URL and immediately have options to granularly dial down the "protection" or add a website to my trusted list. In Firefox I was annoyed to having go through settings for the extension.

Brave plans to continue supporting Manifest V2 after Google kills it. For Ungoogled Chromium, however, it's still undecided, likely depending on whether UG contributors are willing to maintain it.