mbleigh

6 ms·

1.
Welcome to the Age of the Slop Fork(mbleigh.dev)
8 points by mbleigh 7mo ago|0 comments
2.
by mbleigh 10mo ago
Yeah, it does lose something in the more realistic performances. Was still fun to play with though!
3.
by mbleigh 10mo ago
FWIW I actually agree that the original is funnier in its delivery!
4.
Broccoli Man, Remastered(mbleigh.dev)
169 points by mbleigh 10mo ago|94 comments
5.
by mbleigh 11mo ago
Fair, but the person who coins a term generally doesn't ultimately decide how it's going to be used, see vibe coding for a more recent example. REST API became colloquially defined as "HTTP API with hierarchical URL structure
6.
by mbleigh 11mo ago
Heh, the problem with having a half drafted post on your machine for a few weeks is the industry moves fast! I had the post pretty much done, went on vacation for a week, and Claude Skills came out in the interim. That being said Skills are
7.
by mbleigh 11mo ago
Totally agree, the web itself is absolutely HATEOAS, but there was a type of person in the 2000s era who insisted that APIs were not truly RESTful if they weren't also hypermedia APIs, but the only real benefit of those APIs was to ena
8.
Context engineering is sleeping on the humble hyperlink(mbleigh.dev)
177 points by mbleigh 11mo ago|68 comments
9.
by mbleigh 2y ago
TL;DR GraphQL isn't really the problem, untrusted clients executing arbitrarily complex queries is the problem. This is why authz is hard, why rate-limiting is necessary, why "query complexity" calculations are necessary... A
10.
Query-Defined Infrastructure with Firebase Data Connect(firebase.blog)
7 points by mbleigh 2y ago|0 comments
11.
by mbleigh 8y ago
FWIW providing access logs is something we're exploring (though it's still a ways out). I certainly hope that you don't feel the need to move to something else when your application scales / gets more complex -- our whol
12.
by mbleigh 8y ago
Founder of Divshot here, and engineering manager of the Firebase Hosting team. Thanks for the shoutout! :)
13.
Static Website Hosting: Who's Fastest?(savjee.be)
4 points by mbleigh 9y ago|0 comments
14.
by mbleigh 9y ago
Yeah, unfortunately this is pretty much an unsolvable problem. Roadmaps are subject to change and even more subject to be delayed, publishing them tends to disappoint more than reassure. If we gave a forward commitment the questions would j
15.
by mbleigh 9y ago
We announced the product, that's a loud public commitment. Once it reaches general availability, it will be covered by the Cloud deprecation policy requiring a minimum of one year notice for deprecation. I'm not sure what other gu
16.
by mbleigh 9y ago
The Firebase Realtime Database has been around for ~5 years (and is still fully supported after this launch). Cloud Datastore has been around in some form (started as App Engine Datastore) since 2008. Cloud Firestore was a massive multi-yea
17.
by mbleigh 9y ago
I'm surprised the FAQ doesn't answer the question that immediately came to mind: why should I risk my data with an untested startup when the only benefit is claimed performance/price? Or my second question: wait, doesn&#x27
18.
by mbleigh 9y ago
If you need to ask them these questions that's an employee, not a cofounder. Maybe it's an employee with a big chunk of equity, but in general you should have a pre-existing professional relationship. Otherwise, there aren't
19.
by mbleigh 9y ago
This author seems to be afflicted by a crippling short-sightedness. I stopped reading when I hit the sentence about autonomous cars being "just a new type of car".
20.
by mbleigh 9y ago
What effect does a transfer protocol have on the average user? If they knew, why would they care? Genuinely curious.
21.
by mbleigh 9y ago
TypeScript isn't higher level than JavaScript. It is JavaScript, just with a lightweight type system. It doesn't make things "easier" than JS, it makes the process of building large JS apps less error-prone.
22.
by mbleigh 9y ago
I (barely) tolerate the bay area to get to do the work I love. It's a permanent game of weighing pros and cons and doesn't feel sustainable long-term even working at one of the best-compensating companies on the planet. When 40% o
23.
by mbleigh 10y ago
Is it possible things will change? Of course. I was just trying to illustrate that, unlike Parse and Facebook, Firebase has a clear relationship with core Google businesses. We will never be able to fully dispell these worries, but I think
24.
by mbleigh 10y ago
Firebase engineer here. We recognize the anxiety that comes with a hosted solution. That being said, Firebase has seen enormous and growing investment from Google (see e.g. Fabric acquisition). Firebase feeds directly into two huge business
25.
by mbleigh 10y ago
v6.9.1
26.
by mbleigh 10y ago
Well, Cloud Functions for Firebase isn't the only thing we're working on... ;)
27.
by mbleigh 10y ago
You can definitely do this! There are two ways that readily come to mind: 1. Use the Realtime Database as a communication channel to trigger a Cloud Function that then sets up the thing you need. 2. Create an HTTPS function and call it dire
28.
by mbleigh 10y ago
Firebase engineer here. Additional languages will come, but we're starting with Node.js. We'd rather take the approach of doing one language really well than a bunch of languages with a poor developer experience.
29.
by mbleigh 10y ago
Firebase engineer here -- what don't you like about the Firebase Console? Any specific things that we could improve?
30.
by mbleigh 10y ago
A solution is under active development. We don't communicate timelines, but it's a high priority for the team.

More ›