So far the tax filing season is going "well" for me in #Taiwan. I downloaded their latest required plugin for smart card readers on #Linux from the official site at https://moica.nat.gov.tw/rac_plugin.html and it seems to be breaking excellently with a #Javascript error.
Day 40 of #100daysofcode#webdev was the start of my capstone project. Now, I am creating a website to play tic-tac-toe on. So far, so good. Day 41 will be more #javascript-heavy to implement the game's function.
Hi, as a #FunctionalProgramming beginner, I'd appreciate any guidance. Links to in-depth discussion, examples, and summaries would be great. I'm pretty fine with #JavaScript overall, and have used some FP features, but strict FP is new to me.
Greg Johnston, maker of the front-end framework Leptos in #Rust, has a great explainer on the performance costs/benefits of #WebAssembly and whether Rust applications can beat out #Javascript apps.
In short: yes, but… ready for it… "it depends."
TL;DR: most WASM apps will beat out native JS apps, potentially even things like Svelte, but one major hurdle for WASM is a lack of code splitting. Up-front load times is the current cost for native-like run time speed. https://www.youtube.com/watch?v=4KtotxNAwME
#JavaScript privste attributes don't work with a popular convention to duplicate objects for reactive streams, proxy objects. So if you want your library to be compatible, you need to abstain from using private fields. 🫡🪦
Once I get a stable job, I'm thinking of setting up a Mastodon/(Miss/Calc/Found)key server for me and my immediate family (which), but I'm debating on whether or not to go the #Mastodon route or go the #Misskey route; I know that Misskey may be easier to use because it only uses #javascript for its stack compared to Mastodon using JavaScript and #Ruby for its stack. I'm also debating what policies to implement to moderate my server; I will for sure adopt my current server's rules with a few edits, but I don't know what other rules I should enforce and how to enforce them.
question for other #nodejs#javascript devs out there. is there a way to get the predictability of reproducible versioning between dev and deployed without having to lock down your package.json to exact versions? concern is that locking down versions now introduces a quarterly upgrade cycle that sucks up dev time. i'm also not a fan of dependabot's yarn.lock only updates.
this whole convo started w/ #nextjs 13.3.1 release with a nasty bug.
It's where I experiment with all things web, like #html#css#javascript esp. #svelte and #svg most often in the context of #dataviz or similar forms of visual storytelling.
I’ve been watching out for languages that could encroach on JavaScript’s power domain (the browser) for awhile. Since Node, it’s been able to play on other language’s turf, but not the other way around.
The idea that #rust could compete with #javascript on its home turf is one that I’ve watched carefully. The blocker seemed to be WASM bindings; that is, JS was still fastest at working the DOM.
If anyone's got chops, thoughts on the best way to make a #javascript module available to require() from a PyPI installed #python package would be welcome on this ticket:
A very well written article, that argues why it is the best time to invest in Web Components rather than anyone else's flavor of the month Front End Framework.
Breaking change²: data is now evaluated in virtual machine contexts.
If you were persisting custom objects³ and referencing classes from global scope (globalThis) to have your objects keep their types when read, you must now explicitly register your list of custom classes using the new classes property of the options object when calling JSDB.open().
Day 39 of #100daysofcode#webdev is done, and it was again all about the four different kinds of loops in #javascript in action. The sheer amount of helper constants is kind of overwhelming for me, and I think I'll have to repeat some of the lectures before moving on. Day 40 up to day 40 are a milestone project, so I will find out quite quickly how well I understood all the control structure stuff...