The Evergreen Web section in Kitten’s¹ settings now has its own page too (and uses Kitten’s new Streaming HTML² workflow).
If you have the previous version of your site up somewhere, you can use the 404-to-307 technique³ to forward missing pages to your old site so as not to break the Web.
It can now return the result in order (at cost of performance of course) and it also got a new method: mergeIterables(), which interweaves values from multiple async iterables in parallel
I have this blog set up and ready for writing using a bare, classic web stack with no framework, no static site generator, just html/css files and some short scripts in JS and OCaml.
The only thing I feel is missing is an RSS feed. Presently I am feeling very inclined to just rolling my own RSS using the very same stack (a text editor and scripts) instead of switching to some SSG just to get an RSS feed. Something tells me that this is a sinful, heretic thought.
Ideas welcome on how to avoid such heresy. Encouragement to just do it also welcome.
#Javascript experts, I need advice. I'm trying to extend a class in order to override a method or two. It defines everything in its constructor, and I can't work out how to use anything in the original class from my new one.
Could anyone suggest to me how syntactically I should minimally replace onKeyDown and handleKeyDown with my own versions, while still being able to use functions and properties from the base class? I'd really appreciate the guidance!
I am looking to #Connect with people who are interested in:
Coding
Web Development
Front End
Back end
React/Nextjs
Javascript/Typescript
Tailwind CSS
UI/UX
Open Source
Software Development
=== applies much more reasonable behavior for operands of different types, mainly by not coercing them together like == does.
A lot of developers will tell you to learn the rules of coercion and use it when appropriate, however I disagree for one key reason. Consider this example:
if (foo == bar) {
doSomething();
}
Question: Did the developer mean to use ==? Is the coercion intended or a typo?
It's incredibly difficult to know with any amount of certainty as this depends on the types and semantics of foo and bar.
If I was writing this intentionally, I would feel compelled to write a several line comment about how coercion behavior applies here in a desirable way. And if you need to write that much explanation, it would be much less confusing to actually codify the desired behavior with === and explicit type checks so devs don't have to understand that coercion.
I thought I would take up the challenge of getting @enhance_dev#WASM working with #aspnetcore with the ability to SSR web components directly into the request pipeline.