oatmealsnap

I disagree. Even if you don't put too much weight into this test's results, if you stick with vanilla JS your agents (or human devs) are going to write `element.addEventListener` and `document.querySelectorAll` countless times, and each one is going to drift a bit of time.

Having some sort of reusable framework is important for maintainability, always has been. Sure, you can have an agent "write a small JS framework that covers common functionality", but then you need to know what should fit into that framework. Having a framework pre-defined saves a lot of decision making and helps avoid drift.

In my opinion, this has always been true and it hasn't changed with AI-coding.

There are skills available that might help you out. The “superpowers” set from Anthropic is really impressive.

The idea is, you want to build up the right context before starting development. I will either describe exactly what I want to build, or I ask the agent for guidance on different approaches. Sometimes I’ll even do this in a separate Claude (not Claude Code) conversation, which I feel works a bit faster. Once we have an approach, I will ask it to create an implementation plan in a markdown file, I clear context and then tell it to implement the plan.

Check out the “brainstorming” skill and the “git worktrees” skill. They will usually trigger the planning -> implementation workflow when the work is complex enough.

I use my old MacBook Air as a server. Really easy to set up out of the box.

That's always a concern, though. Node has breaking changes, too.

15% is most likely too much to ignore. Most web developers have had to support IE11, which is at like, 3-4% tops.

hey, just like web development.

I mean, there's a time and a place for speed reading. Part of being good at speed reading is identifying the areas you need to slow down for and pay attention to.

Another aspect of writing code is to think about future speed readers. Can your code be skimmed and understood on a cursory level?

That's not how I see jQuery hate.

jQuery promotes bad development patterns, AND brings a cost for end users. Developers will do themselves and futures devs a favor by not choosing to use it. Is it really gatekeeping to expect people to be aware of commonly used 10 year old features?

I assume developers who share YMNNJQ are just sick of inheriting messy projects built with jQuery. I know I am.

I thought this was a parody post.

Could it be used as a Linux desktop environment? I.e. Alternative to Gnome?

I would love to be able to contribute improvements to the desktop environments I use, but I don’t have the time to learn languages that aren’t applicable to my daily work.

Yea, far more web developers know PHP than Ruby or Python.

Python devs don't necessarily know web development, and Ruby is pretty old-school (I don't mean that in a bad way, it's just not what they teach these days and not as applicable outside of web development).

I know several people look at the 3090 for ML use, due to its extra RAM. Hobbyists, not companies.

Do you mean "enterprise ML"? Like, if I ran an ML company I wouldn't be looking at these cards?

Yea, I get 60fps @1440p on an 8 year old AMD GPU, no issues. I haven't checked the actual frame rate, but I've not noticed any dropped frames.

Same experience. I tried, but Linux just isn’t ready to be used as a general OS right now.

I’ve dug through message boards and bug reports, and a lot of the features that MacOS has will never be implemented. I’m taking about features released 13+ years ago on OS X 10.4.

Code for the developer that comes after you, not for yourself.

If you’re going to implement a coding style, make it easy to follow. Provide a linter that works with multiple editors, and that can automatically fix common problems or design choices.

If the project is intended to be short-lived or you know for a fact your won’t update it after two years, then who cares. Try something new or get it done quick and dirty.

Pick the right tools and methods for the job, and make sure those methods decrease friction with your team (communicate and get feedback often).

Ok, I'll just rewrite my clients' entire website using a trendy, brand new JS framework that is built on top of an ever-changing trendy JS library, requiring the entire site to be compiled from scratch when my client wants to update a title.

Different tools for different projects. Gatsby and Gridsome, or any other static site generator is not comparable to a simple script like this.

Audible does. I believe it even syncs it with your Kindle books, if you purchased both versions.

I was surprised when I saw the Apple Books app didn't have that feature. Seems like a no-brainer to include.

Wow, thank you for sharing! I'm guessing those are all D3 5.x?

You’ll find this to be really helpful.

https://every-layout.dev/

For practice, try dropping React and simply build the layout you want. When you’re happy, rebuild it with React.

That might be true, but the radio buttons aren’t coded up correctly.

Pretty sure that exists in Firefox

Nobody makes money off flat-earth and anti-vax conspiracies, either. Of course, anyone can write a book about their experiences on X fad.

There must be open source editors available that have feature parity with 12yo software.

Two tips:

I can't download that file without logging in to a OneDrive account.

I'm human, and I have no idea what that is for.

I've never worked with React, but I have worked on giant AngularJS (1.x) apps and medium-sized Vue apps. I've only seen performance issues on pages with long repeated lists that create a lot of $watchers. This is fairly straight-forward to solve, and I know that Vue and Angular are both a lot smarter about tracking changes than AngularJS was.

Is React more difficult to keep responsive as an app grows? What sort of UI paradigms lead to poor performance? Just the phrase "using immutable data structures (that support reference equality checking) in combination with judicious use of PureComponent/shouldComponentUpdate/React.memo" makes it seem like you need lots of in-depth React knowledge and additional packages to write a performance React app.

Yea, it was even causing my keyboard to lag. Keystroke queued up, but the key press state (enlarged visible letter above your finger) was really delayed.

Why is it difficult? It's just a command line tool with a config file.

I'm not familiar with this tool, but with Babel, you wouldn't use it to bundle your code. That's what Webpack/Rollup/Parcel is for.

If you don't care about targeting older browsers, you can use ES Modules today without a bundler. Even dynamic imports work without transpiling or polyfilling.

Why?

200W still seems really high. A +10yo MacBook Pro used an 85W charger, and it rarely if ever reached that max. I find it hard to believe that even an old gaming laptop would require over twice that.

Isn't it up to [competing music service] to implement this? Podcasting apps work with Shortcuts, so I don't see why [competing music service] wouldn't work.