71–80 of 226 posts
Earlier quoted context omitted.
Cloudflare reports 50% quarter growth year over year, it sounds to me you're in a minuscule minority.
Yes, let's simplify the Internet, being decentralised is such a crutch! We should all just connect directly to Cloudflare.
Those function don't suffer from cold start time? When somebody hit my webserver for the first time, how long are they gonna wait for the page to be loaded? Assuming a noop in the functions part.
https://developers.cloudflare.com/workers/learning/how-worke...
What is really annoying is that Cloudflare pages will strip the file extension off of your html pages, and perform permanent redirects to those new URLs. Now if you're intending on moving to a new hosting service that doesn't do that (cgi-bin), all Google search results to your site will 404. Github pages and likely others also supports this format, so moving between those two services doesn't exhibit this problem. M…
Earlier quoted context omitted.
Having .html file extensions is very old school, and its removal is one of the popular/default redirects on all http servers that support it. Site generators also hide it through various methods (e.g. having a folder with the path name with just an index.html where a dynamic redirect isn't possible).
Yes. New school's defining feature is needless layering of complexity to hide the simple truth of the file system from users.
Earlier quoted context omitted.
Having .html file extensions is very old school, and its removal is one of the popular/default redirects on all http servers that support it. Site generators also hide it through various methods (e.g. having a folder with the path name with just an index.html where a dynamic redirect isn't possible).
Yes. New school's defining feature is needless layering of complexity to hide the simple truth of the file system from users.
What is really annoying is that Cloudflare pages will strip the file extension off of your html pages, and perform permanent redirects to those new URLs. Now if you're intending on moving to a new hosting service that doesn't do that (cgi-bin), all Google search results to your site will 404. Github pages and likely others also supports this format, so moving between those two services doesn't exhibit this problem. M…
Having .html file extensions is very old school, and its removal is one of the popular/default redirects on all http servers that support it. Site generators also hide it through various methods (e.g. having a folder with the path name with just an index.html where a dynamic redirect isn't possible).
I'd love to see a more detailed post about that. I don't know any TS devs using that kind of workflow.
Why not just make it CGI (or FastCGI) compatible so you can test it locally or run it in other environments? At least for things that are actually generating responses rather than acting as middleware. Oh, right, vendor lock-in.
The engine is open source: https://github.com/cloudflare/workerd We did not create our own engine to create "lock-in". On the contrary, it would be a huge win for us if we could simply run FastCGI or Node or whatever applications unmodified. We'd be able to onboard a lot more customers more quickly that way! Our product is our physical network (with hundreds of locations around the world), not our specific developmen…
I'm interested in Durable Objects but I don't know how to work within the 50-subrequest limit on the Free or Bundled plans.
It sounds like I can only read from 50 Durable Objects or KV queries in a single request. If my usage pattern is e.g., sharing docs with many users, how would I let more than 50 users access a doc?
Whether I consider fanning out on writes or fanning in on reads I'd need more than 50 subrequests. How should I approach this?
Earlier quoted context omitted.
Static hosting combined with server-side dynamic content modification using postgres was the interesting part for me. Static hosting has historically been seen as exactly that, static and immutable. Things like Cloudflare functions/workers can turn static hosting into dynamic content delivery while maintaining (most of) the benefits of static hosting. Granted, this can be done whether the underlying content is hosted…
I’m still struggling to understand how this is any different than an oldschool cms or blog with a cache in front.
Plus CDN if that matters.
Earlier quoted context omitted.
Yes. New school's defining feature is needless layering of complexity to hide the simple truth of the file system from users.
Is there a reason why someone visiting your website should know or care about file extensions?