mircerlancerous

Any framework that requires me to learn custom syntax, is a problem in my opinion. I agree with the author that the browser is already the framework, and a powerful one at that. I don't really struggle with views and dom thanks to my own libraries, so maybe those without appreciate thw guilded gardens of these frameworks. Problem is that if these frameworks fall out of favour or stray from their original quality, you're stuck with worthless knowledge and maybe code as well

Interesting; good to know.

I've been running this web server for over a year with no stability issues like that. The app itself shutting off was the biggest issue, but the alarm plugin reboots it whenever that happens. Perhaps you had a bad batch of phones but in my case, it's been very reliable.

Glad you like it! The phone serves everything. In this case Cloudflare will be helping with some caching, but it's not required.

Edit: actually looking at the logs, it looks like Cloudflare caching is off or isn't working; everything you see is served up by the phone.

Author here. What boiling water doesn't take care of all that ;)

Author here. I'll admit that I have made limited use of AI for helping in areas that I'm less familiar with (like FTP protocols), but I haven't paid a dime; all free plan. I'll use AI to help make the project possible, but it's not trustworthy enough to make things readable and maintainable.

If you want help getting this setup for yourself, let me know; happy to help.

Author here. Qik is the name I've given to the project. It's pretty clear on all the pages that it will always be free, and that there's no reference anywhere to any crypto services. Give specifics if you think otherwise; there's lots of noise these days, so I'm not offended you figured this was another one.

Author here. All good points from this point and its replies, which to me says best to me that not all products and experiences are equal, so proceed based on your comfort level.

Note that the app is capable of monitoring both battery charge percentage and temperature. If one was inclined a USB to serial adapter with some simple circuitry could be used to monitor and control the state of charge. Good idea for a follow-up project and article!

Hold the submitter to a higher standard by introducing penalties for errors, and/or incentives for clean PRs. In my opinion a PR should be flawless once submitted, as the dev should have tested thoroughly. QA should only catch errors in a small percentage of cases

If you want to buikd and distribute something B2B or just to friends or colleagues outside of the app stores, it's a nightmare on iOS. Sideloading isn't as simple anymore for Android, but it's way easier. It's for that reason and for more open hardware and software that I exclusively work on Android now. Too bad about iOS as generally I like Apple hardware, just not interested in the hassle with everything else.

Personally if I see a PR that's not readable, I send it back immediately without much of a read-through. AI or not, the code should be readable or it's not maintainable by people or AI

Yes, very familiar. I think it might be ok though, as it's similar to a web search where you maybe need to refine it a few times. Just assume that the first answer may not be fully correct or complete, until the AI has more context. It would be a nice change if it would ask the follow-up questions automatically.

You may want to offer a page credits option instead, as "50 pdfs" for the free tier is a little vague. Is that 50 1-page pdfs, or 50 100 page pdfs? We generate our pdfs one page at a time, and then stitch them together into one at the end; I'm unsure whether your solution would be practical for us. Self-hosting is maybe the other option

Totally agree that creating something to reproduce the issue is a big turn off when it comes to reporting bugs; what else can one do though? In your case though, I guess it was a pretty simple thing

Well-written and valuable for insight whether you have similar personal experience or not. As someone who does hardware and software as well, I relate to the challenges of making something you can hold; it's very easy to underestimate the challenge difference between the two. Your Murphy's law references are spot on; I feel comforted reading I'm not the only one this happens to! Misery does love company, and it's important to hang on that I think, so that you don't lose hope :)

I store my data in the service worker cache, so I guess I'm immune to this issue

Service workers solve the cache issue; web apps can run permanently offline after initial load. You may be a bit out of date on the state of the web.

Service workers allow you to control cache in web apps; you may be a bit out of date.

There are hardware APIs for some stuff that only works in native (cors, raw tcp), but 99% of apps don't need those.

I do but I feel it's long overdue for replacement. I've been working on a new protocol that includes timestamp filtering, real-time notifications, and optional things like 'likes' and 'comments'. I use it everyday and I load it with content from RSS feeds. Not ready for sharesies yet though

A self-hosting ecosystem with apps and services to do everything from file sharing, to email, and dynamic DNS. It's Javascript based and runs in node, but I've also got it running under Android and in a regular web browser (the web browser one needs requests forwarded to it). The whole goal is to make self-hosting really easy, cheap, but also capable. It's got a long way to go, but I've already posted a few articles on HN that are hosted on it.

I'm not sure I can accept the findings of this article. It seems to me that all the concerns and issues can be summed up to bad design. A mini framework should be designed to be easy to adapt and extend, and any layer on top should be just as easy to further adapt and extend. That to me is the crux of this, "avoid frameworks that are difficult to adapt and extend".

You don't need React or HTMX; just put onclick= on your element and make your call with vanilla javascript. Use these frameworks if you want, as they're both neat, but frankly I think people forget that there are other options

Depends on what you mean by "native". Like do you mean same look and feel, or just launch and performance?

I disagree overall. While good points are made, a client could simply pass state data when reconnecting SSE. Tell the server the last message that was received, and you're good to go. Long story short is that SSE isn't the problem, it's how you're using it that might suck.

Neat project, regardless of some of the opinions of practicality.

What you want to do is make sure your client device is an HID device, so that it's recognized as a keyboard. I think something like this will do: https://makerspot.com/cp2110-usb-hid-to-uart-serial-adapter/

For the server side, you'll either want a USB to serial adapter with a microcontroller in between, or one of the RP2040 Raspberry pis as it can be both those at once. https://www.waveshare.com/rp2040-zero.htm

Actually you can probably do it with two RP2040s (or maybe just one) as their USB ports I believe can be configured for different roles.

Good luck, and share your results!

+1 to this. I've found AI to be a good tool for getting things started, and for handling more tedious features that would have required reading a lot of documentation. I wouldn't trust AI to build a whole feature on its own, but with you at the helm, you can use it to build a feature one piece at a time. I use Perplexity with a free account.

I feel the same as you on this. There's always something not quite right with one editor or another. I did start down the custom path by finding a very bare bones editor, so that I want starting from scratch. I was able to make changes and get it to good enough, but what I found is that there are lots of simple things that aren't always so simple. Things like auto-indenting for example look simple but can be fiddly, especially if you've mixed tabs and spaces. I might come back to it but for now, the other editors are also good enough.

Completely agree. I don't work much in PHP anymore, but there's still nothing that's faster or easier to get something up and running. I use it for web services, and command line scripts when I just need something fast.

My son is 12, and we've just started in on learning coding. To make it fun, we're making a game together. He does all the art and game design, and I do all the coding. To help him learn coding, I make him sit with me while I do the easy parts, so that he learns concepts. I explain things like variables, loops, and functions, and then talk through the design with him. He 'helps' me solve things at a high level, and then I show him what the solution looks like. At his age I think simple exposure to concepts is important, as it will make things easier if he gets into it himself when he's older. As for AI, it is still just a tool to make devs more productive, you still need to understand coding to get the most out of it. With that in mind, the basics are just as important as ever.

Please correct me if I'm wrong, but I feel rendering html overtop of canvas solves this with vanilla just fine. Canvas is for rendering things you can't with html, and not replacement for the dom.