inlined

(I work on Firebase App Hosting, which also supports Next.js directly rather than OpenNext)

I want to +1 that Vercel has been really improving their portability. We still have Next.js specific code in Firebase, and having different architectures can sometimes make us have to figure out the best mapping of their features, but Vercel has made a noted effort to improve encapsulation of Vercel-specific features and portability has improved. I’m honestly surprised that OpenNext, which is not a new project, seems to have gained a lot of attention in the immediate past.

I think the hardest gesture to do would be to scroll. Cheekily I nominate sticking your tongue out and virtually licking the UX up/down

I teach AED use and both my curriculum and trainer AEDs have one pad on the right chest and one on the left side. Is this the “two on the chest” method? If so, why have organizations not updated their curriculum and tooling?

Should I assume that irrespective of this finding, pads should be placed where the AED indicates so that rhythm detection works correctly?

Traditionally, you would sign with the government’s public key so that only they can decrypt it. But ballots are so low entropy that I’d be worried about brute forcing it (maybe some significant nonces can be added?) a solution where you use the block chain signed with certificates held in a central database is just… another case of people pushing blockchain without understanding it

Things I like:

- Everything is an expression

- Async imports just work without thought

- Yaml-like object structuring

- JSX improvements

- Multi-line string literals without leading whitespace

Things I’m on the fence about:

- Pipe operators (better than .pipe I guess?)

- Pattern matching (love it in Scala and swift, but this doesn’t feel done right)

Things I loathe:

- Signifiant whitespace (removing brackets in general)

- Optional parentheses in function calls (a foot-gun in VB and Ruby)

- Splats in the middle of function definitions (I can’t imagine how this works with overload definitions)

Mom and pop are the consumers/victims here. And if 46% of all websites are WordPress, it’s probably likely that it has a monopoly on sites in its domain (e.g. blogging, commerce)

Do you want antitrust investigations? Because this is how you get antitrust investigations.

Wordpress is nearly half of the Internet. There’s a pretty compelling argument that Matt is using his market power to prevent competition in violation of the Sherman act.

Can we either remove the subtitle that’s not in the article or s/affect/effect?

I actually wonder if “tip the development team” makes sense (assuming tipping is gratuity and not because an employer pays below-living wages). Weirdly it might even lead to quality improvement because low tip areas could be detected and debugged.

Wonder if the size of this breach will be used as evidence of consumer harm by their monopoly. If there were more competition in the market, there wouldn’t be one single treasure trove so enticing.

Vercel has great products (both their hosting product and Next.js). If we look back far enough, some of Next.js’s most killer features (e.j. ISR) had tight coupling with their hosting platform. In the last year, Vercel has really upped their game. The Vercel-specific features are becoming encapsulated with replaceable delegates and Vercel has started differentiating with additional services. This is great! Vercel is innovating with new infrastructure (e.g. KV) while also increasing the portability of Next.js applications. We (Firebase) are going to use these more portable APIs to offer similar experiences and Google, Vercel, and others will differentiate on their IaaS ecosystem. This benefits developers immensely because it eliminates lock-in fears because Next.js will have proof of portability in market and you no longer have to couple your infrastructure and framework decision making. It’s a bright future for web developers in general!

Yes, I’m the engineering lead of Firebase App Hosting. If you have anything you want to talk about, inlined.dev has all the places you can find me.

Any node app works if you have a build and start script. Being a “supported” framework is a lot more about forward looking commitments that we’ll understand your site’s configuration and translate it to our native output rather than asking you to do it “our way” (e.g. redirects that never have to hit your backend)

The build process is open source, as are any adapters we use to help align vanilla code to best practices. Some stuff is magic (e.g. the FIREBASE_CONFIG env being automatically injected), but I’d hardly call that a risk of lock-in.

Though I'm not familiar with the specifics, they announced "context caching"

Yes, against Hollywood. Before then you could only see a Fox movie at a Fox theater

Especially since Google had always had the AOSP as a reasonable way of demonstrating their commitment to the industry as a whole disjoint from the places where they thought the Google ecosystem provided extra value (which they admittedly require you to take wholesale)

Unless Apple has a most favored nation clause—another legal practice that should be outlawed

Taken in the context of Google as a whole, this seems like pretty good evidence that Google does not consider itself to benefit from monopoly power like the DOJ claims. If Google did have a monopolistic advantage, they could refuse to pay the link tax. Clearly they're worried about losing market share to other search engines.

[usual disclaimer: I work at Google but on nothing related to search or policy]

I feel like Cal Poly SLO prepped me for “real programming” relatively well. The software engineering major has a year long capstone program building software for a real company. I built a scriptable GPS emulator for Trimble. I was also required to do a work study to use software engineering to the benefit of someone other than software engineers (I worked on real estate).

Are you using a log service directly, or stdout? Stdout has no such issue. On Run (and therefore functions 2nd gen) you get a SIGINT before the container is shut down. Open Telemetry is pretty easy to configure to flush on SIGINT in the background.

What part of the constitution prohibits banning software?

Large amounts of money being sent through tumblers is definitely suspicious. Or spending more money than reported income.

I used to work at Microsoft on the windows team. There it was very common to have a “goto cleanup” for all early exits. It was clean and readable. Otoh, I once was assigned to investigate an assertion error in the bowels of IE layout code. It was hundreds of stack frames deep in a recursive function that was over a thousand lines long and had multiple gotos that went forwards or backwards. That was an absolute mess and would have been impossible to debug without an recording (“time travel”) debugger.

My email address is no@never.com. I’ve actually seen some forms reject it though

The iPad

If the latter requires you to do your own mini router to handle each verb separately, then yes. It greatly improves readability and reduces boilerplate to have the ability to have one handler per path x verb

I hope you’ll watch the firebase summit keynote on Tuesday

Thank you for the feedback. I can’t comment about future roadmaps, but we expect v2 to severely reduce cold start problems with concurrency support. WRT deploy times, I’m not a fan either, but this is the cost of standardizing on Docker. I don’t honestly see that decision being reversed soon. That’s why we’ve instead decided to invest in an emulation suite. How has that worked out for you? And I’m curious why the real-time database and Firestore don’t meet your needs. The real-time database requires manual sharding, but tools for that have dramatically improved (e.g. in v2 functions, a single function can listen to all databases in a region). Firestore is built on spanner. It prohibits queries that fall apart at scale, but it’s a planet scale database that you’ll never have to shard.