3,884 karma · joined March 14, 2013
building Superuser, come join :)
https://superuser.app
https://x.com/keithwhor
I can edit the above to;
> I do think specific words and long sentences have their place. They can be used to alter the flow of a sentence and make it feel more conversational instead of less.
But it's not the way I talk. I enjoy the way you can alter the cadence of sentence to impact the reader. For example: the phrase, "perhaps counterintuitively," is like a rolling hill the reader spends extra energy to climb but then engages them with the writer, "I'm interested, I like hearing about counterintuitive things" -- it's almost an invitation. You've set an expectation that something counterintuitive is ahead, so what's next?
Generally, I could use more of Paul's advice in my own writing. And that's the fun of writing, learning to write is a very organic process. But I'm sure everyone can find their own style somewhere in between simple, poetic, natural, or whatever makes you feel the happiest about your work.
I never had experience with J2EE personally which is why it’s missing. I was 12 in the year 2000 and had just started web development — because of that PHP retains a sense of primacy in my mind. Forgive the bias :).
FunctionScript has a basic type system that’s a superset of JSON but there should be an overarching semantic system to it all. Feel free to e-mail me, keith@ (company domain) and introduce yourself if you’d like to chat about it. :)
You’re a large tech company. Your front-end of engineers want to build with GraphQL. Your legacy API is 80% REST with some SOAP endpoints strewn about. Who gets saddled with the job of building to the OpenAPI spec and why? Where is it creating customer value? You introduce it and then what, what value did you actually unlock from your customer ecosystem? I’m not saying that it doesn’t create value — but which stakeholders can you explain that to and how long does it take to convince them?
On the other hand, if you start a new company, you’ll find that your API evolves organically. Locking yourself into a specification ahead of time is like writing all the unit and integration tests before a product ever gets in customer hands. Does anybody even want this? Are we even going to expose this API? What if we need to change it?
OpenAPI isn’t bad — quite the opposite, it’s fantastic. When we encounter an API that adheres to the OpenAPI spec it makes our lives a lot easier.
The problem is what I outlined above: for OpenAPI to permeate the market there has to be some sort incentive so powerful that it spontaneously aligns thousands of companies and millions of developers to accept it as the One True Specification. That’s just never going to happen.
So “standardization” can only come from something that creates an economic incentive so great that everybody agrees to it without hesitation. Which is a Herculean effort; it requires something like a product that’s never existed before, or an entirely new class of web developer. When you start thinking down that path you start seeing through our eyes at Autocode. I’m not saying we have the exact right answer today, but I’m saying this is how we think about the space.
Every single one of these products starts out with the same epiphany we had, which is some variation of, "there needs to be an API for APIs...". People keep putting a band-aid when what's really needed is an architectural refactor of how we deliver and connect APIs, full-stop. The problem is there's very little market incentive to standardize how API integration works because it requires the complex coordination of thousands of companies and millions of developers. The barrier to transformation is extremely high, so the catalyzing agent has to be spectacular. A product (or set of products) needs to come along that completely changes the game and creates a real incentive to standardize and adopt a common integration scheme and format.
The worst-case scenario for Autocode, as I see it, is becoming just another integration tool for some specific vertical. What we're striving to deliver is an open ecosystem for integrations that's accessible to non-developers who are going to derive the most immediate value from it as an introduction to development, but attractive to professionals as a development target as well. That's an extremely difficult balance to achieve but the rewards are just as large as the problem, technically the entire industry could be made more efficient at scale.
https://autocode.com/lib/halo/mcc/
As you can see from the code examples, you just talk to it via an API key and a standard calling convention. It's completely portable. Autocode makes it easier to manage your tokens, code, etc. but you could port this to any Node.js codebase or make an HTTP request from anywhere. We have universal Ruby and Python libraries, too, but they're a little outdated. (Small team, have had to stay focused on Node.js for now.)
Edit: I'll mention that technically anybody can add to our stdlib. We do a lot of the work ourselves right now, but it's fundamentally an open platform. Also see other comment re: FunctionScript specification and how we add APIs to the stdlib. :)
The reason we don't support GQL APIs natively is because we designed Autocode to follow the best practices of the top API companies we knew; Twilio and Stripe. Both companies designed their SDKs in a way that feels natural: a call to their API is achieved via a namespaced function call -- it's very Railslike. Everything available in our stdlib follows that convention as we felt it was the most intuitive approach to API / SDK design.
- Participants preferred whatever they saw first
- Otherwise, accelerating or rapidly accelerating progress bars were generally preferred
If you're designing progress bars with an unknown time to completion, my recommendation is to use an accelerating function for the first 95% over the predicted median time to completion. Then linear timing function for the next 4% and set the time to 3x the median time to completion. Automatically fill the bar when progress completes, no matter what.
e.g. if an action takes a median time of 4s to complete;
f(0 <= t < 4) = 0.95 * ((t / 4) ^ 2)
f(4 <= t <= 16) = 0.95 + (0.04 * ((t - 4) / 12))
f(t > 16) = 0.99
You can adjust this however you see fit but I find it gives a pleasant experience.HTTP is quite literally "hypertext over sockets" so "HTML over websockets" is functionally equivalent... with a layer of abstraction added on top. If you build web software by sending HTML over websockets you're just reinventing what already exists; it's probably why it's never taken off. I think most developers realize within ~weeks to months of working on a "websocket-everything" framework that they're doing more work, not less.
- What happens if the client’s internet connection temporarily drops? How do you handle client reconnections and retries?
- What if the remote server crashes through no fault of your own (AWS server rack catches fire)? How do you ensure a consistent reconnection that preserves application state?
These are just two questions that HTTP + Browsers solved decades ago.
Websockets are this cool technology that seems powerful and exciting until you realize the “boring old stateless World Wide Web” was built over decades of iteration using stateful sockets as the backbone, did most of the work for you in tandem with browsers, and is ultimately a lot cooler and more sophisticated than a lot of us give it credit for.
The problem is that stateful connections suck and create artificial complexity when you don’t need them. Instead of managing the state of your app you’re now managing the state of your app and a connection to a remote server. HTTP is a stateless protocol on top of a stateful socket connection. It wasn’t designed this way by accident.
I’m all for new engineers building SPAs creating exciting new libraries, but HTML-over-websocket has been rehashed at least three times over my professional career so far and it’s not even that long.
Don’t get me wrong — websockets have their use cases. Multiplayer online experiences pretty much require them. It’s just that HTTP isn’t fundamentally broken, and by engineering HTML over websockets you’ll almost universally find yourself building protocols to abstract the state away... re-engineering HTTP in the process.
It’s certainly a fun project which I have personally worked on. But I’m not sure it has legs outside of that. Open to being proven wrong, the authors of HTTP aren’t infallible.
Gorgeous game, lots of educational tidbits, highly recommended if you're looking for a little bit of escapism during the pandemic. :)
(Note: I'm a SaaS company founder, not a game developer, so forgive the rough edges.)
Edit: If you notice lagging, it's actually synchronous Voxel / terrain generation, not the rendering! Never did offload it to a separate thread like I had planned. Built this during the start of the pandemic in a weekend or two.
What you're saying is that; due to debt issuance in the US, it's hard for commodities and consumer goods to be priced efficiently. I interpret "confusing price signals" to mean that e.g. Apple can charge $1k for an iPhone and sell out to families who wouldn't typically be able to afford it, but the price of bread remains the same. Your medical bill comment -- you're basically saying that when one of these families hits a statistically predictable snag, they're instantly bankrupt because they've always been functionally broke, propped up by the consumer debt industry?
And so you're saying that most commodity goods face deflationary pressure as a means to stabilize the market? So if the price of commodity goods does increase significantly beyond the capacity of debt issuance, we're likely to see a depression?