Just wanted to say congrats on the project. This is truly a masterpiece from the utility of it, the novelty, to execution with the vscode / meridian app, and sass. Brilliant execution!
I feel like it shouldn't be the classes responsibility to provide a method to return a nullable / falsey value. We should have a convenient one-line syntax around try / catch. Something like pipe operators and or pattern matching.
I've gotten a couple gel manicures recently, it's addicting once you start because it lasts a long time. I'm taking a break from it because it makes your nails brittle. They make special gloves you can wear that just expose your nails, ideally I was thinking the same technology in 3d projection mapping could be used to only expose the nailbed to uv ligt with hand tracking. It would increase the the cost of one of these uv curing devices by smartifying it but would prevent cancer...
Is there any DIY / 3D Printed community-made projects around designing household appliances? I'm mainly thinking about vacuums but even blenders and other things. Im not talking about everything being hand-made but designs can be made with popular motors, blades, and things of that nature. I like the idea of an off-the-shelf vacuum using the most efficient or readily available motors, and bags.
I've been using the native Uint8Array that Deno provides and it's been great overall. From time to time I may need to covert away from a Buffer type and it's a little bit of a headache, but I think the ecosystem is supporting Uint8Array, at least on the server very well.
I agree with this article, however I think that HTMX needs a strong server framework to support HTMX. I've thought about this alot and a couple months back created this deno / typescript framework https://github.com/reggi/htmx-components, would love for people to take a look at it and provide guidance and direction for a releasable version.
Location: New York City
Remote: Yes
Willing to relocate: No
Technologies: react, deno, node.js, nodejs, typescript, javascript, shopify
Résumé/CV: https://resume.reggi.com/
Email: [email protected]
Location: New York City
Remote: Yes
Willing to relocate: No
Technologies: Node.js, React.js, Next.js, TypeScript, JavaScript
Résumé/CV: https://resume.reggi.com/
Email: [email protected]
10 years expierence building full stack web apps. ex twitter, mongodb, hello alfred, anheuser busch, american express
Hey! That would be really cool and interesting. You'd still need all the creators to agree on a pricing structure based on the transparency mentioned in the article, you'd still need to pay engineers and cover server costs.
It's a deep dive in understanding and empathizing with another human being, and reflecting and finding the things one is grateful for in their own life.
I'm very interested in a way to containerize (runing them within a vm) these tools that way nothing needs to be installed, and could go easily from machine to machine, without polluting the filesystem.
Thanks for this! This is really helpful. To expand further, I can't tell you how many times I've written something as simple as a promised version of fs exists, and if you do copy and paste something like that into your project you have to bring it's deps (tracking them down in package.json) in and tests (for full coverage into your new project. Alternatively you make it a one-off npm module. It just seems like both those options are cumbersome and inefficient for one function. I'm very much against the MVC setup (I'm working with mainly API's), and as well as OOP in general, and write a ton of very small functions, some that expand on tools like lodash, and that I use a lot. This is where it gets harder and harder to maintain them.