I gave this a go recently, nice work!
In a few hours I was able to get a really nice looking UI starting from an example.
I got a bit frustrated when it came to managing state though. I struggled to mutate and view the same state across all web users, instead of creating state per user that connects.
However this is still a great framework I’ll definitely revisit in the future!
Just to offset the negative comments on here, I think what you did is great! I don't think people appreciate the 1.5 years of individual effort you put into this and the demo looks like something I would find genuinely very useful. This clearly has lots of potential!
I would honestly prefer paying for it, perhaps with a cut-down free version (perhaps using cached data only?) without sign-up to try it out, so one day you can work on it comfortably and doesn't require commitment for me to try out.
However I'm sure you'll refine it in the years to come considering how well you've done so far. Keep up the good work!
Really amazing work, well done! Having something like this when growing up would've made electronics so much more accessible.
I can't think of anyone I know close to me that would really appreciate this gift, so I'm with another comment on here that gifting it online somehow would be something I'm interested in. I'd feel happy knowing I'm supporting a great product and helping the less fortunate of the younger generation get better access to fun educational tools.
Yeah I was thinking something like this too, hopefully someone makes this if it hasn't been already.
If the diagrams had some linkage to your code you'd be able to see what a failed unit test means in the overall context of the app, what code is used in which block, what protocol is used for connections between blocks, a summary of what each block does etc...
A monitoring tool as you say - and since you'll use it often you'll probably keep it up to date
As a primarily C++ dev who's been using nodejs on the side for about a couple years now - so forgive me if this is naive - but am I wrong in seeing Deno as a potential Electron replacement with standalone binary builds + webview?
If so, the introduction of interactive permission prompts is pretty cool.
I see a few comments from more experienced web developers that are quite negative about Deno that seem to generally be centred around the fact it offers very little compared to nodejs, and isn't worth the effort to learn.
Does it have potential as a safer, lightweight Electron alternative? Or are there better options than Deno in that regard?
> Does it have potential as a safer, lightweight Electron alternative? Or are there better options than Deno in that regard?
If they target this, the big chunk of code will still be the same ones on Electron, so i don't think it would get to be safer or lightweight as compared to Electron.
there's webgl, webgpu, and dom, but it's a headless dom (jsdom) not a webview.
I wouldn't be surprised to see packages developed for a webview but atm demo seems to target server side web platform compatibility... except rendering html!
I wouldn't be surprised to see some packages try to fill the gap, & deno has a much stronger basis for implementation than node (a rpc layer between rust & v8 defines the core character of the project, and an native addon that adds webview methods to the rpc would be natural in Deno, vs a hack in electron).
It's likely you will find some hiccups in latest deno release because it uses rust plug-ins and they are getting overhauled at the moment. Maybe a few more months before getting stabilized.
Found my number on there too even though I've deleted Facebook for at least 5 or 6 years now -_- Not sure when I gave them my number either, I hope it wasn't scraped from someone else's contact list...
At least it makes sense why I received a bunch of spam calls over the weekend.
Anyway it's probably good practice to recycle your number every few years, and not use it for 2FA to make switching numbers a lot easier. Who knows what services I'll be locked out of once I change, let's hope not too many.
I can’t imagine telling everyone I know that I’m changing my number every couple years, and I’m not even calling/messaging a lot of people nowadays. I have a family member who did something similar(not on purpose) and I still have 3 of her numbers and still get confused which is the working one.
I had a company phone about 6 or 7 years ago for a company I worked for at the time. When I was on my way out they unilaterally revoked my company-provided cellphone after convincing me I should get rid of my old private number for theirs.
I'll never do that again. It happened shortly after ditching social media and I just about all of my contact info and I haven't been in touch with some old friends because of that since then.
Even if you had the time to transfer your contacts, etc, something will inevitably get missed.
Hell, I've updated family and friends to an email address I've been using for closer to a decade and they still email the old one...
I know exactly what you mean, there's only so many times you can append "New" on the end of a contact name!
A good chunk of people will probably communicate mostly on platforms like WhatsApp/Telegram/Discord/whatever that don't need numbers at all or facilitate switching of numbers without your contacts having to do anything. I don't think that will constitute anywhere near the majority of people across the world though, switching numbers will definitely be a pain for most.
"Anyway it's probably good practice to recycle your number every few years, and not use it for 2FA to make switching numbers a lot easier."
Ironically Twilio of all places forced SMS 2FA on all accounts earlier this year.
As in, one day you could no longer log into your twilio account without giving them a phone number. You are locked out until you do.
Ironic in a few ways ...
First, twilio numbers are not mobile numbers - they are voip numbers - and cannot be used for most 2FA authentication services because they cannot receive messages from short codes. So it's ironic that twilio forces you to use a non-twilio number for their 2FA.
Second, many twilio use-cases (like mine) involve building a twilio infrastructure to replace my existing phones/numbers ... and now that is broken from the bottom up because I have to use a mobile phone with a fixed provider just to use twilio.
The bottom line is: none of this is for me or my safety and security. Twilio has a spam problem and that spam problem is very hard to solve. Forced pairings of physical phones and SIM cards is just a desperate way to throw sand in those gears to slow it down a little bit.
I have had a Twilio account for years, and have always used the proprietary MFA implementation from their Authy app. I don’t remember being forced to switch to SMS MFA.
I thought this was the norm. I've had the same number for 20 years now, though have moved through many different area codes since. But, I must be the odd one, because I get asked regularly why I have the area code I do, and the answer "because that's where I was living in 2001" doesn't seem satisfactory.
It's fascinating reading about giants of academia, that I've personally never thought to link together, interacting and disagreeing with one another in such a relatable way.
I wonder if anyone's written about a younger Dirac and any interactions he got into with his heros, and so on and so forth back as far as possible? I'm sure there's an amazing story to be told through following this "thread of knowledge" through time...
I got a bit frustrated when it came to managing state though. I struggled to mutate and view the same state across all web users, instead of creating state per user that connects. However this is still a great framework I’ll definitely revisit in the future!