mgdev

Aaron makes an appearance in the 2005 documentary "Aardvark'd: 12 Weeks with Geeks", which was a documentary about interns building a product at at FogBugz (by Joel Spolsky, now known for Trello and Stack Overflow). I watched it again recently after many years and was sad to see Aaron appear with his unbridled optimism.

https://www.youtube.com/watch?v=0NRL7YsXjSg

Where do you think most devs work?

Also, +1 to Oracle! (disclaimer: former OCI dev)

Can the optics be used in reverse, as a short-range projector? Very interesting AR applications if so...

I don't follow. Why? If there's no income earned, why should someone pay rent on deposits in a bank account?

Facebook is net-zero emissions.

The deeper in your stack you fix the consistency problem, the simpler the rest of your system needs to be. If you use S3 as a canonical store for some use case, that's pretty deep in the stack.

> Thus, once you've built a distributed system that is able to handle a phased rollout of software/config versions (and rollback), then having cache inconsistency in S3 is no big deal.

But this would also mean you can't use S3 as your source of truth for config, which is precisely what a lot of people want to do.

They've basically bolted on causal consistency.

It's a great change.

The key is: who is allowed to see the segment ID?

In Apple's world, Apple owns the supply side ad surfaces, Apple maintains the segmentation and mapping, and Apple mediates the demand side.

What does an advertiser see? Pretty much nothing.

Oracle Cloud DNS is Dyn DNS. Same product/stack. In fact, private DNS is also powered by Dyn tech.

Except it's not far-fetched at all [1]. If you optimize for conversions, and the value of those conversions is large enough, the returns readily cover the costs.

[1]:https://zapier.com/apps/facebook-conversions/integrations

Speaking for myself, not the co: we all decide who we want to trust and why, whether it’s browser extension, or a browser, or a phone.

For me, it comes down to alignment and value. Amazon stands to lose a lot if they decided to suddenly stop caring about customers, or not take security seriously. And the Internet gets pretty small if your threat model requires zero trust.

I designed this. I won't speak to any past or current practices, but I will say this: Amazon is obsessive about protecting customer privacy.

I believe the sharing only applies when talking to those third parties. E.g., if you only ever talk to friends and family, there is effectively no change.

I know you. :)

#doppler4lyfe

Buildionaires.

I thought Bloomberg was into Bucklescript/ReasonML. Warring factions?!

> this requires nonfree Javascript

So... I get the motivation for including this, and I understand Emacs's roots. But IMO this mindset — the one that motivated including this disclaimer - is also why efforts to "modernize" will pay an extra tax, possibly preventing its success.

Emacs has a prioritization rubric that places freedom above mainstream utility. That's perfectly fine, but it inherently limits 1) its audience size, and subsequently 2) its contributor pool and 3) financial upside - either direct or indirect (used to support the project).

This means it will always lag behind the projects that are setting the bar for what "modern" means.

"GraalVM Community editions are based on OpenJDK version 1.8.262 and on OpenJDK version 11.0.8."

https://www.graalvm.org/docs/getting-started-with-graalvm/

I'd love to see sales stats shared for this. Would be a great case study for 1-person digital product sales.

Oracle used Lisp [1] in the UIs for their gen-2 cloud product. They eventually hit a wall hiring the kinds of people Oracle wanted to hire (few of whom wanted to learn an esoteric language), and made the tragic decision to move new development over to TypeScript (and port many of the key existing surfaces for ongoing maintainability). Mixed results on that. Many who were around for both the old and new code bases report that, while the old one took more effort to pick up, it was easier to trace data flow and is less prone to creating weird state bugs.

[1]: https://www.linkedin.com/pulse/building-cloud-choosing-lisp-...