has reached the end-of-life and is now read-only. Please see the EOL announcement for details

Idea: A tool for non-tech people to generate a static website that lets users save & load CMS content by using an external cloud storage service like Dropbox, Mega, etc. so you can host a full website for mostly-free

Does anyone know any good (or just standalone ) that have a really good physical feeling rather than a flat/stylish one? A while back, I saw this awesome chunky button and I'd love to know what else is out there.

It's annoying that `document.execCommand()` is deprecated ( even though it's the only way to easily interact with `contenteditable` in . I don't care that `contenteditable` is implemented inconsistently across browsers, it's convenient for implementing editors without needing a ton of .

Without it, the smallest JS-only WYSIWYG editor that I can find is ~50 KB ( instead of the ~3.5 KB ( one that uses `contenteditable` and `document.execCommand()`... It's not *that* bad a difference, but I'm looking for the smallest possible option that's widely compatible, and it looks like pell won't be an option for much longer. 😣

The place I work in Denver, Colorado is 2 senior web developers. We're looking for folks who are great with JavaScript and PHP, specifically working with VueJS and Laravel, respectively, though there's some flexibility to learn on the job if you're a fast learner and have used similar frameworks before (there was for me at least).

We've started returning to the office part time (I go 2 days a week), but the people there are super cool and fun. The company itself does building energy usage (benchmarking) consultation and has been branching out over the past few years to build software that helps manage energy use—that software is specifically what you'd be working on if you get this job.

It's currently a team of 5 developers (including myself) to work with, and the position itself will be for not only writing code but also also helping manage the team.

If you're interested, apply via Indeed here:

I've decided that for the sake of my career's future, every project I start from now on will be made with , whether it needs to or not.

Starting a new project to prove that I know how to use it. It'll be a life tracker where you can journal, track moods, and have todos and stuff. Seems like an attainable goal that's complex enough to get people to see that I know what I'm doing.

I'm using only "popular" tools for the project and it's antithetical to everything I've done for a personal project before because I always try to make my projects as small as possible. If I was building this normally, I anticipate it would be <100kb, but I'm certain the final result will be >800kb at the smallest... maybe I can at least make it accessible.

It's been about 1 year since I started working on @Readlebee, so I wrote a blog post about my experience so far:

TL;DR: the development process is very different than what I'm used to because I'm trying to do it "right," and that slow process has been discouraging, but I'm hopeful that I'll get something to show for my work relatively soon.

Excellent. Now when I ask for help and opinions, I can potentially get replies from both Mastodon *AND* Twitter! I'll be UNSTOPPABLE!!!

wishy-washy dev framework bullshit 

Oh no, React + Redux might actually be a really good choice for Readlebee 😂

React's per-Component states would be extremely helpful to have, and Choo doesn't have that built in—I'd have to build my own implementation, and I don't have the time! Maybe Preact...? That's pretty light, right? But then I'd have to add preact-compat to use Redux plus whatever other react add-ins, which would make it even larger... ugh, maybe I shouldn't care so much.


Only 15 minutes to answer!

I'm gonna finally redo my whole portfolio site from scratch! What should I use?

I just finished and uploaded my updated Audiobook Time-to-Page Converter!

It's roughly 40x larger than the original version because it's built using , , and , but it looks nice and I added some extra features, so I'm happy with it! Plus it's still a lot smaller than I expected it to be; I was expecting a full megabyte!

Overall, it was a pretty good experience! And the source is on my GitHub if you're interested:

Well... and are kinda starting to grow on me 😬 They're *exhausting* to work with, but the structure and flow is pretty interesting and almost fun!

Sheesh, why am I SO upset over ? Is it really just that I can't conceptualize a single reasonable use case for it? What makes me reject it so hard?

If I don't fall in love with it and React and all the other bullshit that modern uses, I'll never be hireable anywhere else!

I'm doing the course on freeCodeCamp right now, and holy fucking shit, I can't believe how stupid this is. Why would *any* self-respecting programmer want to add this much overhead to their work process? This is one of the stupidest ways I've ever heard of to accomplish what it's trying to do. Jesus christ!

I really hope something very compelling shows up by the time I finish this course or else I'm just going to be seriously concerned for web developers' mental states from now on.

Should I write 's front end in instead of what I'm currently using for professional skill-building purposes and maybe a greater range of developer familiarity, or should I keep using the tiny framework I'm currently using that I love called that's easy to learn and understand anyway and that everyone ought to be using instead.

I'm planning on streaming some development on Thursday at around 7 or 8 pm Mountain Time, so stay tuned if you're interested! As it gets closer, I'll post the exact time and the link!

Hey there Fediverse friends! When it comes to (or ) , what do you prefer?
ES6+ (aka EMCAScript) or ?

Also, which might make you more likely to contribute code if you're interested in the project?

I just saw this, which wrangles up some tests performed to see what freshly-installed do when you first load them:

Pretty interesting stuff!

Show older

‼️🔛‼️'s choices:


the mastodon instance at is retired

see the end-of-life plan for details: