photog.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for your photos and banter. Photog first is our motto Please refer to the site rules before posting.

Administered by:

Server stats:

244
active users

#webpack

0 posts0 participants0 posts today
Hi, I'm Evan (he/any).

TLDR: I'm a privileged white hetero-cis-male politically #left #TriratnaBuddhist #SoftwareEngineer (#IHelpPeopleGetJobs) currently in #Seattle but planning to move to #AotearoaNZ or #Australia as so as we can manage it with my wife & 3 kids

I'm politically #left (at least in United States terms). I'm a #voting nerd in that I have a favorite voting-related textbook (Collective Decisions and Voting by Nicolaus Tideman).

I think we could mostly solve #gerrymandering by making larger districts with ~5 representatives instead of just 1 and then using #SingleTransferableVote. That would strike a nice balance between local & proportional representation. For single-person positions, like presidents/governors/mayors, STV becomes #RankedChoiceVoting (aka #InstantRunoffVoting aka #AlternativeVote) which eliminates the spoiler effect and leads to more civil campaigns.

Plus, #RankedChoiceVoting eliminates the need for primaries and runoffs, which can lead to significant cost reductions.

I'm training for ordination with the #TriratnaBuddhist Order (#dhamma, #dharma, #Buddhism) and have been for many years. It's a long process, especially with other things going on. I've done some kind of #meditation (mostly #anapanasati) every day for over 3 years and more sporadically since 2006.

That said, I do take issue with some of the things the founder (Sangharakshita) did, and I'm concerned with a recent rise in sort of guru worship around. I can have gratitude for his explanation of the dharma, try to sort out the idiosyncratic bits, and still view him as a deeply flawed human being.

I write #software for http://indeed.com (job search site) (previously employed by Amazon). I've written a lot of #database-backed #webservices in #Java, but in the last few years, I've been working on #microfrontend platforms in #JavaScript & #TypeScript, primarily supporting #React. I have more knowledge about #Webpack #ModuleFederation than anyone should be cursed with. I'd love to try #SolidJS, #RustLang seems really cool, and I'm excited about the future of #WebAssembly.

My wife & I have fantasized about moving to #AotearoaNZ or #Australia since well before the pandemic, and now we're actively trying make it happen. Since we're both in high-demand professions (she's a nurse), I think it should go reasonably smoothly 🤞. Feel free to get in touch with job opportunities that offer visa sponsorship, suggestions for #kiwiana or Australian culture that will help us adapt, reasons that your city is the best, etc. I always blow on the pie when I wear my jandals to the dairy. If we ship things over, I can only hope that the front doesn't fall off the boat. I hear that only rarely happens.

My daughter Juniper was born at the beginning of 2020, so her experience of life and my experience of parenthood are both tightly linked to the pandemic. On the upside, I get to work remotely, which means I get more time with her. She's a lot of fun (and of course a lot of work).

Then, we had our twins Heath & Magnolia (Noli) in September 2023, and our lives got even more hectic and full of love.

Juniper goes to a Waldorf school, and I wish I could go, too, but I think the adult version of Waldorf school might just be therapy.
indeed.comEmploi | IndeedÊtes-vous à la prochaine étape de votre carrière ? Sur Indeed, accédez à des millions d'offres demploi. Nous pouvons vous aider avec nos outils de recherche d'emploi, CV et des avis.

Even though I'm a backend developer I've got to keep abreast of some frontend stuff so that I can lend my general developer brain to designing or advising or fixing things wherever it happens, and it looks like I've now got to get up to speed on #Preact and #TailWind and #WebPack for the next phase of work. That'll keep me busy for a bit.

Replied in thread

I'm learning just a tad-bit about #AMD ( #asynchronous #module #dependencies ) and #RequireJS. I've always been too retarded to do anything with #Webpack, because it needs to be running server-side as well as clientside in the browser (I think). Dependencies bundled together in real time, at the server side, plus whatever minifier and obfuscation they decide to add.

With RequireJS, it just needs to find static JS files in the URL folder structure it expects. So you can use really any webserver.

<rant>
Yesterday I got really sad about the state of IT and how very rarely we go back and actually fix things and instead we just keep piling more sort-of fixes onto each other.

I was trying to help my partner to add an (background)image to her website.

She managed to find a manual for #tailwind to create a custom class and after a few fixes we got it working, sort of. #Webpack was being, as usual, less than helpful and spew few incomprehensible errors about loader type missing. I know this, I get how to fix this, but the config botch to make it work is ... less than optimal.

Then I noticed that the original design actually used image tag directly to show a placeholder svg. Cool, let's use that. #EmberJS has a cool library ember-responsive-image that will do 90% of the job. Well, in the version the project is using, the image needs to be imported through (already configured) dark magic of webpack imports. Cool, let's do that. Oh no this part of the app is lacking controllers, let's define those. Now I have to explain why this whole whoop of new files and references exists. To show an effing image on an effing webpage.

So we just went old school of defining HTML IMG tag and referencing the non responsive, non optimised image directly from assets. Flip this, Apple landing page literally downloads 100MB to show a scrollbar invoked animation. How bad is it for a private website to show an non optimised image?
</rant>

Now the practical part: More than 20 years ago when I started playing with #HTML and Apache I was researching if it's possible to stream images. So that it's not the developer at the build time to decide the dimensions and quality being displayed, but the webpage at show time saying: "I will need to fill in 2000x1000 pixels for this one image, please keep em coming".

And no, images scaled on the server over query params are not what I'm looking for. That's just a botch that brings more problems than solutions.

I'm talking about an image format where first kB when brutally chopped off would be render-able as a very low res representation of said image. Then next 10kB would give slightly sharper image, then the next 100kB...

And the browser would just keep streaming next part until it would decide it has enough to fill in given space perfectly.
This is the solution to the problem that should've been built in the first place. We could have avoided all the `picture` and `srcset` and build time optimisation and N-times cache invalidation dance. I'm looking for a solution that removes responsibility from the user instead of giving them more work.

Now please tell me that I'm just old and this technology already exists.

Replied in thread

I hate that I'm so easily defeated, and derailed by unimportant shit. I can't tell you how often I find myself stuck in "can't install the PWA". It doesn't matter, it's an optimization, I should just move on and get easier wins. But this is something I've solved in other frameworks, this should be easy, and the fact that it's not just fills me with dread. I kinds of error messages I'm seeing, about server/client doesn't bode well. I'm reminded that I'm deep in #webpack territory again. #nextJS

Is there a way to determine which files a #webpack main.js can dynamically load? For example: I have a main.js which dynamically loads another js file called api.{some random chars}.js

However I can't figure out how the main.js determines the required random chars required to load the correct api.js

Should #NPM libraries handle #bundling themselves?

I'm working in a library for internal use. It will be acting as a utility wrapper for a larger #nodejs library and will be used in two main use cases #CreateReactApp and custom #Webpack projects. This is my first time building a utility library from scratch and was thinking of using Webpack to handle the bundling, tree shaking, and minification, and using #babel for transpiling.

Is this necessary or should this even be done?