Yeah it's odd we needed a whole article for this. "You can't out exercise a bad diet" has always been true outside of the most extreme cases (competitive athletes).
Fair enough, I guess this just seems like a bold assumption to make since an explicit handler function is a cornerstone of lambda, rather than being able to run module level code and having the end self detected.
It may just be such a basic tenant of the platform that no one thought to. You stop getting billed after lambda returns a response so why would you expect computation to continue? This guy expected free lunch.
For brochure / static content sites this is definitely the beginnings of a web crawler but it can be a lot trickier for web apps.
For example, clicking a link which loads some data, then clicking edit (which isn't even an anchor), typing in & clicking stuff, then clicking the save button (don't click the cancel button!) would not be an interaction that would get picked up with your suggestion. Detecting loops becomes much more ambiguous and backtracking to get all the permutations of interactions becomes a whole other problem to solve.
If you are using Cludfront with an S3 origin you can turn on static website hosting and specify a 404 fallback page[0] - which would then just be your index file. It will render your client code and let you show a 404 if it is indeed one.
The problem is that essentially every time a user goes to the site it will be a 404 status code since they are probably not typing in example.com/index but this has pragmatically not been an issue for a wholly authenticated, private, B2B SaaS app. The marketing website is a separate subdomain.
For a public site this is probably worse than returning 200s that should be 404s occasionally, though.
It just seems odd in this context given they are willfully compiling these screenshots together, displaying them prominently, and saying they pay attention to details. What details are they trying to highlight here, if not the UI details?
In general the UI doesn't even look good. It's just a bunch of unflattering grey.
Am I the only one who gets an uncanny feeling visiting this site? If someone told me this was software satire I would believe them.
This cyberpunk-ish theme with juvenile sprite sprinkled over it (e.g. the little AI guy floating under the video and the figures under "What people are saying").
At the beginning of the video I get these '90s infomercial; "The world moves fast / information super highway" vibes. The background music seems ironic considering the visual content.
I guess it is just trying to be retro but the "I want to be post iOS 5 Apple" top bar throws me off. Sorry this is not constructive but I just must know if I'm the only one feeling this.
In any case, I don't mind Slack but I'd give this a try if they allowed more than 500 messages in the free tier. At least Slack gives you the 90 day history.
"Learn to Code like a Developer" is a funny tag line to me. Isn't the point to become a developer? Or are you saying: "you're going to learn with modern tools, just like how a may use tools to facilitate coding?"
Maybe highlight the fact that you have an AI bot helping you through it. I would not have known it unless I read your HN comment.
A concrete example would be a users shopping cart, as they build it. You don’t need the niceties of a fully ACID compliant DB, you need write performance, and extremely high availability.
That was at least a chief use case spotlighted in the original Dynamo paper by Amazon that what the precursor to AWS’ DynamoDB paper.
Not to say that couldn’t be done with Postgres but of course they were dealing with insane scale on Amazon Day.
I duplicated a repo to test this out on and signed up, only to find that all I could try out was Authentication. That's probably one of the features most dependent on which library or identity provider you are using and they only have one library for now.
I think certain fads are a little dreadful in terms of unoriginality - those humaaans illustrations, for example. But I think most of the web really should look similar. I think of brochure websites like resumes: you're trying to depict key points without distractions and obstacles. Just like that one person's "unique" resume is actually the last one you want to read, so is that unnecessarily "original" website.
Yeah I'm always surprised by the downright hate. I use the console for 95% of things and it's alright.
My gripe is that the thing just gives off this BLOATED impression. Safari routinely reloads it because it was "using significant energy." Every time I load a page I just wait until it renders, goes blank, re-renders, goes blank, places everything that was on the left over to the right, and then finally things settle down and I click a button. That all takes about 1.5s though, so not awful.
I don't think the knight should be allowed to move in a full circle. It should be disjointed - four arches. Allowing a knight to move two squares orthogonally kind of makes it a completely different piece.
>> “ A mission critical user check needs to run (eg: does this user have enough money in their account to complete the transaction?)”
That info wouldn’t be in the session db row either.
>> “ A database write needs to occur to persist information (if this information is related to the user, it’s likely that the full user object must also be retrieved from the database”
This type of info doesn’t get updated frequently. Email, phone, name, etc, are pretty static. If they are just talking about a join using a userId, well that’s not gonna be any different whether you know the ID from a JWT or normal cookie.
>> “ The full user object must be pulled out of the cache / database so that the website can properly generate its dynamic page content”
But that’s an upside of keeping more than a cookie with an ID. You can just stash the stuff that doesn’t change much client side (keeping in mind the XSS risks). We certainly don’t pull the user’s email and name every page load even though it’s displayed on every page.
>> “ Almost every web framework loads the user on every incoming request. This includes frameworks like Django, Rails, Express.js”
That’s a framework issue and should be customizable. Not really a JWT vs cookie w/ ID topic
There’s plenty of reasons to choose an ID cookie vs a JWT but the many that the author gives are not among them.
From what I gather, it seems like this would be a good choice if a portion of clients are on low end devices and it is more of a MPA/SPA hybrid - not a full blown web app. A lot of E-commerce and informational sites do fall into the MPA/SPA hybrid bucket.
If you really are making a web app (think dropbox, cloud based enterprise software) I think you'd reach a point where there is so much interactivity that you are essentially shipping Preact, custom component JS, and just a little bit of static HTML. The latter bucket is the only one which saves the user network and parsing time (and I doubt much of it.) I'd still go with a properly chunked SPA for true web apps.